Passing NODE_ENV into the npm script for Windows 10

I am using webpack in a Typescript project. I am following a tutorial where I have created 3 webpack files:

1. webpack.common.js
2. webpack.production.js
3. webpack.development.js

Within the tutorial’s package.json the "scripts" seconds have the following:

"build": "webpack --config webpack.$NODE_ENV.js"

I have been looking into the following SE Query to set the NODE_ENV for Windows 10.

Where within PowerShell I perform:

$env:NODE_ENV="development"

However once I execute npm run build the script still takes $NODE_ENV as a string and does not substitute the values.

I might shift to cross-env later if this doesn’t work for me but I would like to give environments variables a try in the PowerShell.

What should be the equivalent commands for:

NODE_ENV=development npm run build
NODE_ENV=production npm run build

in windows and how should I change the scripts in my package.json viz. $NODE_ENV to accept the variables?

Using cross-env

It is possible to achieve something similar using cross-env by doing the following:

1. npm i --save-dev cross-env

2. Within "scripts" add:

    "build-dev": "cross-env NODE_ENV=development webpack --config webpack.%NODE_ENV%.js"
    "build-prod": "cross-env NODE_ENV=production webpack --config webpack.%NODE_ENV%.js"
   

   And this should trigger the respective scripts.

however, this still does not provide flexibility for user to run a generic npm script command whilst setting the env. variable on the fly

PowerShell Limitations

There are examples where queries suggest doing something of the likes of:

  set NODE_ENV=production&& npm run build

but this fails in PowerShell with the following error:

At line:1 char:24
+ set NODE_ENV=production&& npm run build-dev
+                        ~~
The token '&&' is not a valid statement separator in this version.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidEndOfLine

And & is reserved for future-use.

Answer

I was able to Solve this issue based on comment from @ambienBeing. However here are some Caveats:

• The && DOES NOT work in the PowerShell but WORKS in cmd

• Instead of $NODE_ENV I needed to adapted %NODE_ENV% in the "scripts" part

  "build": "echo %NODE_ENV% && webpack --config webpack.%NODE_ENV%.js"
  

Upon executing the following:

 set NODE_ENV=production&&npm run build

the script gets executed correctly.

In order to be sure, I added console.log("production") as well as console.log("development") in the respective webpack.x.js files

and I could see the respective string printed in the console twice: 1 x from echo and 1 x from the file

Tests

• This works perfectly well with VS Code when one changes the default shell to cmd instead of PowerShell