An in-range update of webpack is breaking the build 🚨

Question

The devDependency webpack was updated from 4.19.0 to 4.19.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 - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/heiseonline/embetty/builds/430060352?utm_source=github_status&utm_medium=notification)). Release Notes for v4.19.1

Bugfixes

• Internal requested filename for import() with target: "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 .mjs
• browser field as object is used when using target: "electron-renderer"
• Comments near export default are preserved
• Passing an array as externals value, now works correctly as documented

Commits

The new version differs by 15 commits.

• b7121c1 4.19.1
• ab28497 Merge pull request #8043 from RubenVerborgh/externals-object-array
• 9bda629 remove bad unit test
• f0271d9 fix ExternalModule and test case
• 3aef0e5 Allow array as value in externals object.
• 7b91fa6 Merge pull request #8042 from webpack/bugfix/comments-export-default
• e08f71c keep/restore comments in export default
• 2f78aae Merge pull request #8038 from sharang-d/patch-5
• bb4c2d1 Correctly set the 'browser' value for electron-renderer
• 5ade574 Merge pull request #7947 from philipwalton/mjs-sourcemap-support
• 5258471 Merge pull request #8035 from kwonoj/fix-path
• 2df7b0c fix(nodemaintemplate): resolve async chunk path platform agnostic
• 17fafd3 Fix lint errors
• a2cc031 Add tests for default source map extensions
• 12762ff Add sourcemap support for .mjs output files

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

该提问来源于开源项目：heiseonline/embetty

Answer 1

After pinning to 4.19.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.