-
-
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
Error overlay gets stuck on first failed compilation #824
Comments
Please ensure you are on the latest version of webpack dev server. Something like this was fixed in the latest version. |
I’m using 2.4.1, which should be the latest. Is this the commit that should fix the issue? |
Yes. Can you reproduce it using this example (clone the repo, |
I’ll try. Do you think it could be related to using node 7.6 intead of 6 to run |
I can’t reproduce the problem with the simple setup in the repository, but it keeps happening in my own project.
Could |
@ludovicofischer do you also have the issue when using |
I tested |
Pruning due to age, inactivity. |
Do you want to request a feature or report a bug?
A bug.
What is the current behavior?
When a change to a file to solve a compilation error introduces a different compilation error, the error overlay keeps showing the first error, even if the console output correctly reports the new error.
If the current behavior is a bug, please provide the steps to reproduce.
From the
webpack.config.js
entry point, import an ES6 module containing a syntax error. The error overlay displays the error. Change the imported module to contain a different syntax error. Now the error overlay keeps displaying the old error.What is the expected behavior?
The error overlay should display the new error.
Please mention your webpack and Operating System version.
webpack 2.2.1, Fedora 25.
The text was updated successfully, but these errors were encountered: