-
-
Notifications
You must be signed in to change notification settings - Fork 622
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
bail = true should not kill watch mode on ModuleNotFound error #1794
Comments
Why are you using |
@sokra I have a config file that specifies bail true by default. I was not sure what to expect. Maybe that the first typescript compilation error will abort the current bundling if Why am I even allowed to use bail true when watching? Why doesn't webpack ignore the option if its not supposed to be used? Perhaps generate an error? |
https://webpack.js.org/configuration/other-options/#bail
|
At the very least webpack should generate a warning when you try to set bail and watch to true at the same time. edit: This can easily happen through config files and forgetting to add --bail=false in watch mode. |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
/cc @webpack/cli-team should be easy to implement |
Yes, I will do it. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
When
bail = true
, a ModuleNotFound error during a change of the files will cause the entire watch process to either abort or get stuck. Subsequent rebuilds will not happen even if the file changes.If the current behavior is a bug, please provide the steps to reproduce.
import './non-existant-module'
to any filenode version: 8.9.4
Webpack 3.11 made one step towards fixing this with webpack/webpack#5797
However even though the process does not die, rebuilds stop happening.
The text was updated successfully, but these errors were encountered: