Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Automatically set NODE_ENV to production when build

See original GitHub issue

What problem does this feature solve?

Currently, I have to add cross-env into build script every time. (cross-env NODE_ENV=production vue-cli-service build).
If I don’t add it, build script will not minify files and extract CSS. (My laptop set NODE_ENV to development.)

What does the proposed API look like?

It should be great if vue-cli automatically define NODE_ENV to production when use vue-cli-service build with production mode. (It’s default)

Issue Analytics

State:
Created 5 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

5reactions

LinusBorgcommented, Jul 22, 2018

I assume you still have NODE_ENV defined globally on your system?

You can’t overwrite an environment variable set on your system with one in an .env file. As Evan alreay explained, and as the documentation explains (I think) - if you have set an environment variable, vue-cli will never overwrite that.

That’s why cross-env works. it changes the environment variable on your system before vue-cli-service runs.

It’s specifically designed like that so people can overwrite stuff with environment variables, which is quite often required in CI/CD environments.

2reactions

Akryumcommented, Jul 22, 2018

Relevant documentation