[ ] I confirm that this is a issue rather than a question.
Bug report
Version
"vuepress": "^1.0.0-alpha.24" tp "vuepress": "^1.0.0-alpha.25" or "vuepress": "^1.0.0-alpha.26"
this problem occurred when I updated, server days ago, I updated to 1.0.0-alpha.25, the bug shows, and this day I updated to 1.0.0-alpha.26, it shows too.
Steps to reproduce
Maybe it is my environment problem.
What is expected?
no
What is actually happening?
yes
Other relevant information
Your OS:
win10 x23_64
Node.js version:
8.11.4
Browser version:
chrome 70.0
Is this a global or local install?
local, vue and vuecli is global.
Which package manager did you use for the install?
yarn, sometimes npm
Description:
I met the bug when I update to the new version of vuepress, I run:
yarn add vuepress@next -D,
and the bug occurred.
As the picture, and I fixed it last time by removing the node_nodules directory and run yarn install, it fixed, but this time, it doesn't work, could you please help find the reason?
Bug report
Version
"vuepress": "^1.0.0-alpha.24" tp "vuepress": "^1.0.0-alpha.25" or "vuepress": "^1.0.0-alpha.26"
this problem occurred when I updated, server days ago, I updated to 1.0.0-alpha.25, the bug shows, and this day I updated to 1.0.0-alpha.26, it shows too.
Steps to reproduce
Maybe it is my environment problem.
What is expected?
no
What is actually happening?
yes
Other relevant information
I met the bug when I update to the new version of vuepress, I run:
yarn add vuepress@next -D
, and the bug occurred.As the picture, and I fixed it last time by removing the
node_nodules
directory and runyarn install
, it fixed, but this time, it doesn't work, could you please help find the reason?Steps to Reproduce:
Other Information:
Yarn version: 1.9.4
Node version: 8.11.4
Platform: win32 x64