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.
Env variables don't seem to load from a .env file on the new cli
See original GitHub issueVersion
3.0.0-alpha.5
Reproduction link
https://github.com/alexjoverm/vue-cli-env-reproduce
Steps to reproduce
Clone, run npm install and npm run serve on the repo provided.
What is expected?
According to the code of the Service, some env variables should be loaded taken from a path, which are parsed on the loadEnv util.
By adding some logs, it seems that indeed the path it takes when running npm run serve is ${rootDirectory}/.env.development and ${rootDirectory}/.env.development.local. They’re indeed loaded.
So, by the console.log(process.env) line in the main.js file, those variables should be printed in the console.
What is actually happening?
They’re not listed in the console.
Note: if this is not supposed how is it possible to add env variables?
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Only variables that starts with
VUE_APP_are loaded on the client: https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-service/lib/util/resolveClientEnv.js#L1Why? It makes my API keys very longs.