Why not set process.env.NODE_END?

In my webpack.config.js I have the following code(and other too, but the point is only that):

//Mode configuration

const isDev = process.env.NODE_END === "development";
console.log(process.env.NODE_END);


In package.the following json script to run:
"scripts": {
 "dev": "set NODE_ENV=development && webpack-dev-server --color --open --mode development",
 "build": "cross-env NODE_ENV=production webpack --mode production"
 },


But in the console I get underfined. Although set NODE_ENV to development.

Tried to do it through cross-env. Same problem.

What could be the problem?
April 7th 20 at 10:49
2 answers
April 7th 20 at 10:51
Solution
process.env.NODE_END
NODE_ENV
See the difference?
April 7th 20 at 10:53
Solution
process.env.NODE_END
cross-env NODE_ENV=production

Find more questions by tags JavaScriptnpmWebpack