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

Continuous re-bundling, VALID state never reached #705

Closed
mischkl opened this issue Nov 22, 2016 · 3 comments
Closed

Continuous re-bundling, VALID state never reached #705

mischkl opened this issue Nov 22, 2016 · 3 comments

Comments

@mischkl
Copy link

mischkl commented Nov 22, 2016

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

@mischkl mischkl changed the title Contiuous re-bundling, VALID state never reached Continuous re-bundling, VALID state never reached Nov 22, 2016
@SpaceK33z
Copy link
Member

SpaceK33z commented Nov 22, 2016

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 webpack --watch.

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 --watch-poll or watchOptions: { poll: true }

@mischkl
Copy link
Author

mischkl commented Nov 22, 2016

@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...

@SpaceK33z
Copy link
Member

Okay, I'm going to close this because we can't do anything about this in dev-server unfortunately.

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