-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
version 2.10.0 throw error #1259
Comments
+1 |
Same issue, Never realised it is related the version upgrade |
@ganesharulanantham Me too, it took me lots of time to figure out |
Same error here, was working before update. |
Same issue. Config has not changed. Please fix |
Same. |
Same error here, was working before update. Use vue-cli to build a new project but...... |
Same here! Still haven't been able to resolve the issue |
having the same issue |
Same issue for me as well |
Same error!, I am using v2.9.7 instead v2.10. |
This is an issue on Ubuntu 16.04 as well. |
"Same here" comments are not helpful. Please just +1 the issue. If you want to be notified of updates, click the "Subscribe" button to the right. |
Hit this issue too. Moving back to 2.4.5 is a temporary fix; all higher versions that I've tried have been affected. |
Is anyone here using |
@readeujet I am; tried that with no dice. |
@readeujet that doesn't work for me either. |
Same issue running yarn on Windows 10. Tried deleting node_modules and running |
installing node modules from yarn is the issue, did |
in my case, installing from yarn worked, but from npm throws error. |
Both yarn and npm can not worked for me , downgrading to 2.9.7 |
I have got the same issue ++1 |
I got the same problem.I'm using version 2.9.2.node version 8.9.4 on ubuntu 16.tried both npm and yarn I still have the same issue |
I have got the same issue |
Same problem. I'm using v2.9.1, node v9.3.0, windows 10. Tried both npm and yarn. worked: |
Edit: @guohui8 Solution worked for me (npm install webpack-dev-server@2.9.7 --save-dev). At least until they fixed it. How did you roll back to that version? PS: Same Issue on Arch-Linux |
Someone found a solution to the problem? |
I have solved this problem by this command: |
Same here. The changes done on this new version are the following: v2.9.7...v2.10.0 |
specifically commit 00e8500 introduce the bug and even more specifically changing yargs dep from 6.6.0 to 10.0.3 |
To everyone on this issue who replied "me too" - this is not said to be rude, and I say this with ❤️ - We've locked this issue to prevent further flooding in of those kinds of comments. That said, we're working on resolving the problem today. |
yargs has been rolled back to v6.6.0 in webpack-dev-server@2.10.1. Issue is resolved. We'll look into the breakages of that dependency update and issue a patch once an upgrade path is found. |
Also just added a test to make sure that this dependency doesn't get updated again. It's bit us a few times in the past. Tests will now fail (preventing publish) if that is updated again. Perhaps at some point in the future we'll move away from yargs to something more minimal. |
Confirming that this is a yargs issue. For us it happened when moving from "~10.0.3" to "~10.1.1" on webpack 3.10. |
mark |
Operating System: Windows i'm having the same problem of Thank you so much . |
PS C:\Users\Xxx\Desktop\9-forkify> npm run dev
webpack 2.7.0 Config options: Basic options: Module options: Output options: Advanced options: Resolving options: Optimizing options: Stats options: Options: Unknown argument: mode npm ERR! A complete log of this run can be found in: Still need help on this, above solutions didn’t help |
@coolapollo you're necro-bumping on a closed issue with many participants. It happens. It's fine, but try not to do it 😉 . |
|
Code
Expected Behavior
good running
Actual Behavior
It will throw the error when update to version 2.10.0. Before 2.9.3 no this error.
For Bugs; How can we reproduce the behavior?
If you have the same error
Downgrade to 2.9.7 temporarily.
npm install --save-dev webpack-dev-server@2.9.7
The text was updated successfully, but these errors were encountered: