Option to ignore test development pages from production build.

[omareg94]

Describe the feature you'd like to request

I have many development test pages collected along with normal pages under /pages.
When I want to have a production build, I move/delete those development test pages in order not to be included in the production build.
What I request is an option to list pages files/folders to exclude from production build.

Describe the solution you'd like

Example for anticipated options within next.config.js:

module.exports = ({
    buildIgnore: {
        folders: ['test', /locationA/test', '/locationB/test'],
        pageExtensions: ['page.dev.tsx', 'page.dev.ts', 'page.dev.jsx', 'page.dev.js'],
            // files with these extensions are ignored from production build, but not ignored from dev.
    }
})

Describe alternatives you've considered

Alternative 1: Ignoring files/folders via .gitignore file on the git repo, however, I still need to include my test pages within my repository without them being included within the production build.

Alternative 2: defining pageExtensions option to include dev pages while in development mode, and remove them while in production mode (this is manual work that's needed to be done on each production build):

module.exports = (
    pageExtensions: ['page.tsx', 'page.ts', 'page.jsx', 'page.js', 'page.dev.tsx', 'page.dev.ts', 'page.dev.jsx', 'page.dev.js'],
        // enable this line when building a test/dev build.
    // pageExtensions: ['page.tsx', 'page.ts', 'page.jsx', 'page.js'],
        // enable this line when building to production
})

[thibautsabot]

Hello!

The second alternatives looks fine to me!
You could use a ternary to have one configuration for all:
pageExtensions: process.env.NODE_ENV === "production" ? ['page.tsx', 'page.ts', 'page.jsx', 'page.js'] : ['page.tsx', 'page.ts', 'page.jsx', 'page.js', 'page.dev.tsx', 'page.dev.ts', 'page.dev.jsx', 'page.dev.js']

[omareg94]

Yes you are right I forgot that next.config.js is Javascript file, not .json, where we can leverage JavaScript automation :")

[peterwake]

For anyone else hitting this page, @thibautsabot was very helpful, but didn't work for me (using TypeScript). What did work (in the TypeScript config file next.config.ts) is the following:

import type { NextConfig } from "next";
import type { webpack } from "next/dist/compiled/webpack/webpack"
type Configuration = webpack.Configuration;

const nextConfig: NextConfig = {
  pageExtensions: process.env.NODE_ENV === "development"
    ? ["dev.tsx", "dev.ts", "tsx", "ts"]
    : ["tsx", "ts"],
  webpack(config: Configuration) {
      // webpack config modifications, if any (I had some svg file handling in here)
      return config;
    },
};

export default nextConfig;