The NPM_CONFIG_PRODUCTION flag sets the NOVE_ENV variable to production in npm scripts
Written by Stefan Judis
- Published at
- Updated at
- Reading time
- 1min
This post is part of my Today I learned series in which I share all my web development learnings.
Today I learned that when you set NPM_CONFIG_PRODUCTION=true and use npm scripts, NODE_ENV will be production, too.
Thanks @bahmutov for sharing why this could lead to confusion!
Was this TIL post helpful?
Yes? Cool! You might want to check out Web Weekly for more quick learnings. The last edition went out 18 days ago.
Yes? Cool! You might want to check out Web Weekly for more quick learnings. The last edition went out 18 days ago.
Related Topics
Related Articles
- How to use headless Chrome in serverless functions with a 50MB limit
- The problem of breaking changes and version numbers
- Top-level promise handling in Node.js ES modules
- How to create a module-based Node.js executable
- Global fetch landed in Node 18
About the author
Frontend nerd with over ten years of experience, "Today I Learned" blogger, conference speaker, Tiny helpers maintainer, and DevRel at Checkly.