NODE ENV is not recognized as an internal or external command operable command or batch file

Question

I m trying to setup an environment for a Node js app  but I m getting this error every time       NODE ENV  is not recognized as an internal or external command    operable command or batch file     What does this mean and how can I solve this problem   I m using Windows and also tried set NODE ENV development but had no luck

User · Answer

process env NODE ENV is adding a white space do this  process env NODE ENV trim       production

User · Answer

For windows you can do it like   scripts          start prod     SET NODE ENV production  amp  nodemon app js        start dev     SET NODE ENV development  amp  nodemon app js

User · Answer

For those who uses Git Bash and having issues with npm run  lt script gt    Just set npm to use Git Bash to run scripts  npm config set script-shell  C   Program Files  git  bin  bash exe   change the path according to your installation   And then npm will run scripts with Git Bash  so such usages like NODE ENV  will work properly

User · Answer

It sounds like your error comes from an attempt to run something like this  which works in Linux   NODE ENV development node foo js   the equivalent in Windows would be  SET NODE ENV development node foo js   running in the same command shell   You mentioned set NODE ENV did not work  but wasn t clear how when you executed it

User · Answer

If anyone else came here like me trying to find a solution for the error    env  is not recognized as an internal or external command   The reason I got this is that I was migrating an angular solution from a mac development machine over to a windows 10 desktop   This is how I resolved it    run npm install --save-dev cross-env go into my package json file and change all the script references from env  lt whatever gt  to cross-env  lt whatever gt    Then my commands like  npm run start some random environment var now run fine on Windows 10

User · Answer

for windows use  amp  in between command also  Like      scripts          start    SET NODE ENV development  amp  nodemon app app js

User · Answer

I wrote a module for this  win-node-env    It creates a NODE ENV cmd that sets the NODE ENV environment variable and spawns a child process with the rest of the command and its args   Just install it  globally   and run your npm script commands  it should automatically make them work   npm install -g win-node-env

User · Answer

For windows  open git bash and try  NODE ENV production node app js

User · Answer

Do this it will definitely work  quot scripts quot          quot start quot    quot SET NODE ENV production  amp  amp  node server quot

User · Answer

I had the same problem and on windows platform and i just ran the below command npm install -g win-node-env  and everything works normally

User · Answer

npm install --save-dev  quot cross-env quot  module  modify the code as cross-env NODE ENV development node foo js  Then you can run the like npm run build

User · Answer

set NODE ENV production  amp  nodemon app app js   will cause NODE ENV to contain a space at the end   process env NODE ENV     production     false process env NODE ENV     production      true   As mentioned in a comment here  use this instead   NODE ENV production amp  amp  nodemon app app js

User · Answer

npm install -S cross-env   Worked for me

User · Answer

Use win-node-env  For using it just run below command on your cmd or power shell or git bash   npm install -g win-node-env   After it everything is like Linux

User · Answer

Most of the answers up there didn t help me    What helped me was NODE ENV production amp  amp  nodemon app app js  Take note of the space  Good luck

User · Answer

Changing your scripts to accommodate Windows is a royal pain  Trying to figure out the appropriate Windows translations and maintaining 2 sets of scripts is no way to live your life   It s much easier to configure npm to use bash on Windows and your scripts will run as is   Simply run npm config set script-shell  C   Program Files  Git  bin  bash exe   Make sure the path to the bash executable is correct for your machine  You ll likely need to start a new instance of the terminal for the change to take effect   The screenshot below illustrates the benefit    npm ERR  when trying to run script initially  Script modified for Windows use runs but doesn t show the return message  After updating npm config to use bash  the script runs and returns the appropriate message

[windows] "NODE_ENV" is not recognized as an internal or external command, operable command or batch file

Examples related to windows

Examples related to node.js