Why set NODE_ENV twice? about react-transform-boilerplate

[chentsulin]

NODE_ENV=production only set process.env.NODE_ENV to production in node environment. In frontend code which run on browsers, it should be replaced with webpack DefinePlugin, Otherwise, you will get a

Uncaught ReferenceError: process is not defined(…)

[theneva]

Oh. Upon further investigation, setting NODE_ENV=production in the package.json script has to do with selecting .babelrc environment.

However, removing the plugin code setting NODE_ENV from webpack.config.prod.js does not seem to affect anything as long as NODE_ENV=production is set by the NPM script. That is, unless you for some reason would invoke webpack without going through the script.

Can I safely remove the plugin code setting NODE_ENV in webpack.config.prod.js in my own project without worrying about side effects?

[theneva]

Okay, I get it now. Thanks! We have no environment-specific code in the front-end app, so I'll leave it out and hope it doesn't bite me.