When I run my Vue app, the console shows:
You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See mo
Using .env
file is a common way to set environmental variables used in a lot of stacks. It makes sense to use it in Vue, not to try to reinvent the wheel.
Here's a little test, which will show what conditions and options you have.
Build your project this this command:
vue-cli-service build
.env file:
#.env
NODE_ENV=development
DDD=development
VUE_APP_NODE_ENV=development
Vue component:
mounted() {
console.log(process.env.NODE_ENV); // OUTPUT: production
console.log(process.env.DDD); // OUTPUT: undefined
console.log(process.env.VUE_APP_NODE_ENV); // OUTPUT: development
},
NODE_ENV is set by vue-cli-service
. You can have multiple .env
files and use vue-cli-service build --mode staging
to run different configurations.
There are environment variables used during build and client-side env variables used in the component code. So you cannot use something like DDD
in your client-side code, because Vue will ignore it.
You can create your own env variable prefixed with VUE_APP_ and use them in your client-side code for any checks. Docs ref.
VUE_APP_NODE_ENV
will work fine in our test.
NOTE
Parsing your url is not the best choice. If you use somethings like this window.location.href.indexOf("localhost")
, it will not work for 127.0.0.1
. There were a few times I had to run the project on a FQDN, and this check will not work for it eaither.
For my particular case where I use pug and just wanted to conditionally add some elements to a component I set the options.data
prop of pug-plain-loader
in my webpack.config.js
such that the loader looks like the following:
{
resourceQuery: /^\?vue/,
use: [
{
loader: 'pug-plain-loader',
options: {
// Use whatever you'd use to detect mode in the webpack config
data: { mode: process.env['PRODUCTION'] ? 'production' : 'development' },
},
},
],
},
}
Here's the full webpack.config.js
I'm using: https://github.com/SuperuserLabs/thankful/blob/5913d9d0bb02e6d2f3b88c541477dc557caa4148/webpack.config.js#L76-L88
After which I could do:
if mode === 'development'
| Only shown in development mode
For the general case, this was harder than I first anticipated. Although someone good at Webpack could probably do this pretty easily.
This is how Vue checks wether it is in development mode:
if (process.env.NODE_ENV !== 'production' &&
process.env.NODE_ENV !== 'test' &&
typeof console !== 'undefined'
)
Source: GitHub
Note: I removed the check config.productionTip !== false
from the code, because it is used only to turn off the "production tip" even if Vue is running in in development mode.
Gene Parcellano's answer works great as long as you are using Webpack, but this might be a bit more robust.
Edit:
It would be easy to combine both answers like that:
if (
window.webpackHotUpdate || (
process.env.NODE_ENV !== "production" &&
process.env.NODE_ENV !== "test" &&
typeof console !== "undefined"
)
)
I usually use:
if(window.location.href.indexOf("localhost") >= 0) {
// Development mode
}
Or:
if(window.location.href.indexOf("localhost") < 0) {
// Production mode
}
By just searching for part of the development URL like localhost
you don't need to be so specific with the rest of the address. This works anywhere in your project, unlike process.env.NODE_ENV
which won't work in the index.html
file for example.
If you started with vue-cli (default webpack) then this should work:
connection: process.env.NODE_ENV === 'development'
? 'ws://localhost:5000'
: 'wss://myawsomeproject.org'
Absolutely the most simple solution is to check for the window.location from you Vue component. That would look something like this:
if (window.location.href === 'YOUR DEVELOPMENT URL') {
//preset form values here
}