Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

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

Posted by Iain Simmons
Iain Simmons
Treehouse Moderator 32,305 Points

NODE_ENV=production in Windows

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

set NODE_ENV=production

...then:

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

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

Antonio Jaramillo
Antonio Jaramillo
15,604 Points

Thanks!

2 Answers

Martin Imfeld
Martin Imfeld
5,403 Points
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
Iain Simmons
Iain Simmons
Treehouse Moderator 32,305 Points

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.

abdo wsdsla
PLUS
abdo wsdsla
Courses Plus Student 306 Points
abdo wsdsla
abdo wsdsla
Courses Plus Student 306 Points

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