Clarify interaction between --node-env and mode

[aoberoi]

The interpretation of the current description is ambiguous, as it pertains to how a configuration function can or cannot benefit from the use of --node-env as a way to set mode. One might interpret it as if that happens before the configuration function is invoked, and therefore should be available to use for logic like switching in the function. That would be wrong. This update makes it clear that the assignment of a default mode based on --node-env happens after the configuration function is executed.

Related: webpack/webpack-cli#4009

Fixes webpack/webpack-cli#3992

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aoberoi / name: Ankur Oberoi (d00cbec)

[vercel]

@aoberoi is attempting to deploy a commit to the Webpack Docs Team on Vercel.

A member of the Team first needs to authorize it.

[alexander-akait]

Can you clarify

so it will not be set in the function arguments (env and argv).

Because

const path = require("path");

module.exports = function test(env, argv) {
  console.log(argv);

  return {
    entry: "./src/index.js",
    devtool: false,
    cache: {
      type: "filesystem",
    },
    output: {
      path: path.resolve(__dirname, "./dist"),
      filename: "main.js",
    },
  };
};

Run

webpack --node-env production

Output:

{
  nodeEnv: 'production',
  env: { WEBPACK_BUNDLE: true, WEBPACK_BUILD: true }
}

[alexander-akait]

Or let's do it better:

so the mode option will not be set in the function arguments (env and argv). You need to use the argv.nodeEnv option