NODE_ENV is inherited from atom process...always 'production'

[jrop]

First of all, thanks for the awesome plugin!

When I run gulp tasks I will run production builds based on the NODE_ENV environment variable. It would be nice if this was configurable, because the default inherited from the atom process is always "production". When I am developing in atom, I usually want to run development builds.

[maniR1990]

Awesome Plugin!! :) Sometimes, when i switch between both QA and development environment. if there is way to give the what type of environment during gulp build then it would be more helpful.

[mamaretti]

Hi! it's really great, thx a lot. But i have the same issue. it seams it runs every task with --production flag. For testing i placed "console.log(elixir.config.production);" in my gulpfile.js. When running "gulp default" in my terminal it returns "false" which is ok. But wenn i run the "default"-Task via gulp-control it always returns "true" which is not ok for me. would be great if you have a solution or some tipps. THX