-
-
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
Continuous re-bundling, VALID state never reached #705
Comments
Note that webpack-dev-server doesn't control any of the watching, so the issue can't be fixed here. You could verify this with Do you have any special characters in your path? There are a couple of known issues with this (see webpack/webpack#2258). It could also be the same issue as webpack/webpack#2320. Or it could be webpack/watchpack#25. I also have this issue sometimes, but very rarely. As a workaround you could use |
@SpaceK33z there are no special characters as in webpack/webpack#2258 and the output doesn't look like in webpack/webpack#2320. I guess it could be webpack/watchpack#25, although the files in question were not newly created... |
Okay, I'm going to close this because we can't do anything about this in dev-server unfortunately. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Oftentimes when a file is changed, webpack re-bundles, says the bundle is VALID then INVALID, rebundles again, again says VALID then INVALID, and over and over. The only way to interrupt the process is to press Ctrl-C and try again.
If the current behavior is a bug, please provide the steps to reproduce.
This issue occurs when using the following configuration:
https://gist.github.com/mischkl/cf7ab4b10df9763aa698a5b885f700cd
What is the expected behavior?
After max a couple of re-bundles the status changes to VALID
Please mention your webpack and Operating System version.
Webpack: 2.1.0-beta.26
OS: Windows 7 Enterprise x64
The text was updated successfully, but these errors were encountered: