-
-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
filesystem cache corruption on SIGINT #2918
Comments
/cc @webpack/cli-team should be easy, we should add listener before running webpack and run |
I will fix it. |
It should be added here, right? process.on("SIGINT", () => {
compiler.close();
}); |
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. |
Don't lock |
Issue was closed because of inactivity. If you think this is still a valid issue, please file a new issue with additional information. |
Sorry for long fix 😞 |
If webpack-cli is terminated by SIGINT while writing to the filesystem cache (e.g. in watch mode during an incremental rebuild of a project with large external source maps), the filesystem cache will be corrupted and must be erased before webpack will build again.
webpack-cli should hook
SIGINT
and await a clean exit from compiler.close.Note that the child processes spawned by e.g.
fork-ts-checker-webpack-plugin
orthread-loader
will hear SIGINT from the parent process, so they'll need to be isolated by spawning the compiler into a detached child process.The text was updated successfully, but these errors were encountered: