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 trialIain Simmons
Treehouse Moderator 32,305 PointsNODE_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).
2 Answers
Martin Imfeld
5,403 PointsWould 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
Treehouse Moderator 32,305 PointsIt'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
Courses Plus Student 306 Pointsokey actually i've done this with just using Git bash in the directory of the project
Antonio Jaramillo
15,604 PointsAntonio Jaramillo
15,604 PointsThanks!