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

[greenkeeper[bot]]

The devDependency webpack was updated from 4.41.2 to 4.41.3.

🚨 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/chrisguttandin/extendable-media-recorder-wav-encoder/builds/625621351?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v4.41.3

Security

• force upgrade terser-webpack-plugin dependency for security fix (not affecting webpack)

Funding

• add npm funding field to package.json

Commits

The new version differs by 5 commits.

• df9f3eb 4.41.3
• fe71d68 Merge pull request #10010 from webpack/funding
• b396d96 Merge pull request #10123 from pustovalov/webpack-4-serialize
• 29b2bdd Update terser-webpack-plugin to ^1.4.3
• bedb566 chore: funding field

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:

[greenkeeper[bot]]

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