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
When I precss Ctrl+C during the initial bundling I expected the process to abort.
Actual Behavior
When running webpack-dev-server through CLI, I have to wait for the initial webpack bundle to be built before I can close the process. This is not necessary for webpack-cli, so is this restriction required for webpack-dev-server?
For Bugs; How can we reproduce the behavior?
Run webpack-dev-server CLI and immediately press Ctrl+C.
For Features; What is the motivation and/or use-case for the feature?
Initial bundling can take a long time, so if you realize you made a mistake in the configuration or you're iterating through different configuration combinations, you always have to wait until the initial bundle is finished.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When I precss Ctrl+C during the initial bundling I expected the process to abort.
Actual Behavior
When running webpack-dev-server through CLI, I have to wait for the initial webpack bundle to be built before I can close the process. This is not necessary for webpack-cli, so is this restriction required for webpack-dev-server?
For Bugs; How can we reproduce the behavior?
Run webpack-dev-server CLI and immediately press Ctrl+C.
For Features; What is the motivation and/or use-case for the feature?
Initial bundling can take a long time, so if you realize you made a mistake in the configuration or you're iterating through different configuration combinations, you always have to wait until the initial bundle is finished.
The text was updated successfully, but these errors were encountered: