You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running vuepress build docs and inspecting the index.html file in /docs/.vuepress/dist/, the <title> tag will show Hi | Dev. Inspecting it further:
Running vuepress build docs should set the NODE_ENV environment variable to 'production'.
What is actually happening?
The NODE_ENV environment variable isn't being set to 'production'.
Other relevant information
Running NODE_ENV=production vuepress build docs works. The project I was working on was previously running VuePress 0.14.x, so I'm not really sure around what version this started to become an issue.
Output of npx vuepress info in my VuePress project:
The text was updated successfully, but these errors were encountered:
Bug report
The
NODE_ENV
environment variable is no longer being set to'production'
when runningvuepress build docs
.Steps to reproduce
In a VuePress 1.2.0 project:
After running
vuepress build docs
and inspecting theindex.html
file in/docs/.vuepress/dist/
, the<title>
tag will showHi | Dev
. Inspecting it further:This is what gets output to the console:

It seems like this repo itself tries to do the same thing I do (set the Algolia docsearch key only in production mode) here: https://github.com/vuejs/vuepress/blob/master/packages/docs/docs/.vuepress/config.js#L34
But it seems like Algolia is also disabled on the live site at this time.
What is expected?
Running
vuepress build docs
should set theNODE_ENV
environment variable to'production'
.What is actually happening?
The
NODE_ENV
environment variable isn't being set to'production'
.Other relevant information
Running
NODE_ENV=production vuepress build docs
works. The project I was working on was previously running VuePress 0.14.x, so I'm not really sure around what version this started to become an issue.npx vuepress info
in my VuePress project:The text was updated successfully, but these errors were encountered: