You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue with suspend and resume flow of Watching. The second and subsequent aggregated changes that occur after suspend are dismissed by webpack.
If the current behavior is a bug, please provide the steps to reproduce.
No, those are actually different bugs (they hit different codepaths). Fixing one won't fix the other. That's why I've opened two issues. Also, they have quite different steps to reproduce.
Bug report
What is the current behavior?
This is an issue with
suspend
andresume
flow ofWatching
. The second and subsequent aggregated changes that occur aftersuspend
are dismissed by webpack.If the current behavior is a bug, please provide the steps to reproduce.
suspend
.aggregated
watchpack event fires)resume
.What is the expected behavior?
The compilation contains changes from both
file1
andfile2
Actual result: only changes from
file1
are applied. Changes tofile2
are skipped by webpack.I've opened a PR with a failing test that demonstrates the problem (and suggested fix): #12897
Other relevant information:
webpack version: latest (but also exists in v4 latest)
Node.js version: 12
Operating System: Windows
Additional tools: no
The text was updated successfully, but these errors were encountered: