A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
My build runs: npm run build
On the first run, it fails. A file in dependency has a typescript error, causing the build to fail.
When I try to rerun it, it succeeds.
When I turn off the cache, it fails every time.
Failed builds should not create a cache that can be used for future builds. When cache is enabled, the build with errors should fail every time instead of only on the first attempt.
Bug report
What is the current behavior?
My build runs:
npm run buildOn the first run, it fails. A file in dependency has a typescript error, causing the build to fail. When I try to rerun it, it succeeds. When I turn off the cache, it fails every time.Example package to reproduce: https://github.com/dnillovna/webpack-cache-fail.git
What is the expected behavior?
Failed builds should not create a cache that can be used for future builds. When cache is enabled, the build with errors should fail every time instead of only on the first attempt.
Other relevant information:
webpack version:
Node.js version:
Operating System:
Additional tools: None
I got the information using
npm run version-info, which executeswebpack --version.I found a similar issue for the other webpack cache plugin: https://github.com/mzgoddard/hard-source-webpack-plugin/issues/507