Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

JavaScript npm Basics (retiring) Installing Packages with npm Managing Dependencies in the package.json File

NODE_ENV=production in Windows

For anyone wondering how to set the Node environment to production in Windows, first:

set NODE_ENV=production


npm install --python=C:\Python27\python

(or whatever your path to the Python 2.7 executable is).


2 Answers

Martin Imfeld
Martin Imfeld
5,403 Points

Would not the --production flag be an easier to remember option? Or is this not equivalent to setting the NODE_ENV?

npm install --production

It's the equivalent for the install command, but if your script or any modules run differently in the 'production' environment, they will get that information from the global variable and so it would still be development.

Also, if you were doing this on a public, production server, then you'd want to set the variable globally, rather than having to remember to add that option every time.

okey actually i've done this with just using Git bash in the directory of the project