-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
0.14.8: vuepress build just failed #1255
Comments
Hi again, I also switched on latest Node (v11.9.0) and 8 Regards, |
I confirm the same error. |
As a workarround, I temporarily changed dependency on webpack from ""^4.8.1" to ""4.8.1" and build run properly |
Hello @sjbat,
Can you be more specific?
Well, that is way I'm always freezing exact dependencies version in all my projects.. |
In my project package.json I added strict webpack dependency on specific version "4.8.1"
|
Same problem here with a clean installation from today. As a workaround, I was able to patch the global installation of vuepress with the change suggested by @sjbat (thanks!) by changing After this patch I am able build my vuepress site without any problems. |
I have investigated little bit and found, that last worked webpack dependency in that case is |
A bug in terser 3.16 which was released hours ago. For npm users run: For yarn users: add the following field to package.json and then rerun yarn: "resolutions": {
"terser": "3.14.1"
} Refs: |
UPDATE: It builds now! Still the same thing here :(
I'm using yarn and here is my package.json
|
@ulivz 👍 A general question, when do you think the current vuepress will goes to Beta Release? |
@ulivz: Please leave the comment when this problem was solved, so we can remove workaround code. Thanks! |
We can close this issue for now, and all the users met this error should re-install your deps:
|
Bug report
Version
0.14.8
Steps to reproduce
I'm following getting started steps from official home page guide
also I have tried use npm way:
What is actually happening?
vuepress build
command is failingOther relevant information
The text was updated successfully, but these errors were encountered: