An in-range update of webpack is breaking the build π¨
Closed this issue Β· 3 comments
The devDependency webpack was updated from 4.18.0 to 4.18.1.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β ci/circleci: build: Your tests failed on CircleCI (Details).
Commits
The new version differs by 7 commits.
c51a1ba4.18.1c79c1deMerge pull request #8018 from webpack/ci/azure-windows37046a7Add windows to azure814b85bMerge pull request #8012 from webpack/ci/azure474a9acAdd simple azure pipeline7b3a297Merge pull request #8015 from webpack/deps/upgrade-tapable35015ddUpgrade tapable version
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
After pinning to 4.18.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependencywebpack was updated from4.18.1to4.19.0.
Your tests are still failing with this version. Compare changes
Release Notes for v4.19.0
Bugfixes
- Create a hash of the whole runtime code for the chunk/contenthash of entry chunks
- Before hash was (incorrectly) calculated from (some) inputs
Commits
The new version differs by 5 commits.
6bf83234.19.0aecdeb3Merge pull request #8029 from webpack/bugfix/hash-bootstrap13b2cddhash content of bootstrap codec2cfa7eMerge pull request #8022 from antleblanc/readme-styling-typo96ffd27docs(readme.styling): write correctly sass
See the full diff
- The
devDependencywebpack was updated from4.19.0to4.19.1.
Your tests are passing again with this update. Explicitly upgrade to this version π
Release Notes for v4.19.1
Bugfixes
- Internal requested filename for
import()withtarget: "electron-main"uses correct path separator on windows
(This fixes a problem with filemappings in vscode) devtool: "source-map"and variants generate SourceMaps when output file is.mjsbrowserfield as object is used when usingtarget: "electron-renderer"- Comments near
export defaultare preserved - Passing an array as
externalsvalue, now works correctly as documented
Commits
The new version differs by 15 commits.
b7121c14.19.1ab28497Merge pull request #8043 from RubenVerborgh/externals-object-array9bda629remove bad unit testf0271d9fix ExternalModule and test case3aef0e5Allow array as value in externals object.7b91fa6Merge pull request #8042 from webpack/bugfix/comments-export-defaulte08f71ckeep/restore comments in export default2f78aaeMerge pull request #8038 from sharang-d/patch-5bb4c2d1Correctly set the 'browser' value for electron-renderer5ade574Merge pull request #7947 from philipwalton/mjs-sourcemap-support5258471Merge pull request #8035 from kwonoj/fix-path2df7b0cfix(nodemaintemplate): resolve async chunk path platform agnostic17fafd3Fix lint errorsa2cc031Add tests for default source map extensions12762ffAdd sourcemap support for .mjs output files
See the full diff