NODE_ENV is not recognised as an internal or external command

Question

I am developing in node.js and wanted to take into account both production and development environment. I found out that setting NODE_ENV while running the node.js server does the job. However when I try to set it in package.json script it gives me the error:

NODE_ENV is not recognised as an internal or external command

Below is my package.json

{
  "name": "NODEAPT",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "NODE_ENV=development node ./bin/server",
    "qa2": "NODE_ENV=qa2  node ./bin/server",
    "prod": "NODE_ENV=production node ./bin/server"
  },
  "dependencies": {
    "body-parser": "~1.15.1",
    "cookie-parser": "~1.4.3",
    "debug": "~2.2.0",
    "express": "~4.13.4",
    "fs": "0.0.1-security",
    "jade": "~1.11.0",
    "morgan": "~1.7.0",
    "oracledb": "^1.11.0",
    "path": "^0.12.7",
    "serve-favicon": "~2.3.0"
  }
}

I run my node server as: npm run qa2 for example.

I don't know what I am doing wrong. Any help is appreciated

yes os matters. for windows it is `SET NODE_ENV=development node ./bin/server` — J Santosh, Oct 14 '16 at 07:07
use GULP if you have multiple environments and some other global variables which vary for each environment — J Santosh, Oct 14 '16 at 07:08
Possible duplicate of ["NODE\_ENV" is not recognized as an internal or external command, operable command or batch file](https://stackoverflow.com/questions/11928013/node-env-is-not-recognized-as-an-internal-or-external-command-operable-comman/40967643#40967643) — laggingreflex, Jul 02 '19 at 07:07

Jagrati · Answer 1 · 2017-03-13T05:39:45.703

62

Since you are using windows operating system., the command varies from the unix system command that you are using.

In windows you have to modify you script as.

"scripts": {
    "start": " SET NODE_ENV=development &  node ./bin/server",
    "qa2": "SET NODE_ENV=qa2 & node ./bin/server",
    "prod": "SET NODE_ENV=production & node ./bin/server"
  },

Use SET and then an & after that.

However using cross-env npm package for cross platform stability is recommeded.

Install it like npm install -S cross-env

"scripts": {
    "start": " cross-env NODE_ENV=development &  node ./bin/server",
    "qa2": "cross-env NODE_ENV=qa2 & node ./bin/server",
    "prod": "cross-env NODE_ENV=production & node ./bin/server"
  },

edited Mar 13 '17 at 05:39

answered Oct 14 '16 at 03:59

Jagrati

11,474
9
35
56

2

Use it as a dev dependency instead of a normal dependency. So, "npm install -D cross-env". – batbrain9392 Jan 30 '20 at 10:29
the "npm install -S cross-env" worked for me in windows. thanks a lot – Bruno Sep 18 '20 at 10:43

score 15 · Answer 2 · answered Oct 14 '16 at 07:05

15

I can suggest cross platform sollution. It's done with the help of the cross-env npm package. Your script section would look like this:

"scripts": {
    "globals" : "npm i -g cross-env",
    "start": "cross-env NODE_ENV=development &  node ./bin/server",
    "qa2": "cross-env NODE_ENV=qa2 & node ./bin/server",
    "prod": "cross-env NODE_ENV=production & node ./bin/server"
  }

So you run once:

npm run globals // to install global dependencies

Then you're free to use your scripts both on linux and windows(mac?).

answered Oct 14 '16 at 07:05

Lazyexpert

3,106
1
19
33

Thanks for the answer, but I think I will go with the other answer. – Shubham Khatri Oct 14 '16 at 11:11
Using cross-env is HIGHLY recommended, because you never know who is going to try to run your code. Other developers, servers, virtual boxes, Macs, Linux machines, etc. – Joshua Jan 06 '17 at 22:02

score 4 · Answer 3 · answered Sep 24 '20 at 06:17

4

Sometimes this can be fixed by using win-node-env if your running on windows, For using it just run the below command.

npm install -g win-node-env

answered Sep 24 '20 at 06:17

Prasad Gayan

1,424
17
26

score 0 · Answer 4 · answered Aug 30 '21 at 12:04

If you run into this problem in 2021, install cross-env as a dev dependency by running npm i -D cross-env.

Then, modify your command in the package.json file thus:

"scripts": {
    "start": "cross-env NODE_ENV=development node ./bin/server",
    "qa2": "cross-env NODE_ENV=qa2  node ./bin/server",
    "prod": "cross-env NODE_ENV=production node ./bin/server"
  },

NODE_ENV is not recognised as an internal or external command

4 Answers4

Linked