Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A bug occurred when I updated #1064

Closed
1 task
chenweigao opened this issue Dec 3, 2018 · 3 comments
Closed
1 task

A bug occurred when I updated #1064

chenweigao opened this issue Dec 3, 2018 · 3 comments

Comments

@chenweigao
Copy link

chenweigao commented Dec 3, 2018

  • 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:

image

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?

Steps to Reproduce:

Other Information:

Yarn version:
1.9.4

Node version:
8.11.4

Platform:
win32 x64

@chenweigao chenweigao changed the title A bugA bug occurred when I updated A bug occurred when I updated Dec 3, 2018
@chenweigao
Copy link
Author

sry for the repo is the last version, because the version could not be compiled with my code.
My repo

@ulivz ulivz closed this as completed in 39e9673 Dec 3, 2018
@ulivz
Copy link
Member

ulivz commented Dec 3, 2018

Thanks for the report, fixed and released at 1.0.0-alpha.27.

@chenweigao
Copy link
Author

@ulivz thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants