emailjs/emailjs-tcp-socket

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

greenkeeper opened this issue Β· 1 comments

The devDependency webpack was updated from 4.33.0 to 4.34.0.

🚨 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).

Release Notes for v4.34.0

Features

  • Error message when parsing fails shows used loaders now

Bugfixes

  • importing the namespace object from non-ESM (CJS) modules no longer leads to an warning
  • Error message in HMR logging works for Firefox too now
  • Parser understands block scoping now
Commits

The new version differs by 30 commits.

  • 34c8667 4.34.0
  • 0652114 Merge pull request #9268 from webpack/bugfix/let-scopes
  • e6f9db8 Merge pull request #9261 from webpack/bugfix/ff-errors
  • e04b1a5 handle block scopes correctly
  • 55f18f9 Merge pull request #9260 from webpack/fix-9044
  • a1d4567 fix error message and stack in Firefox
  • 8d5ad83 simplify code
  • df5e118 fix(mjs): remove unused namespace build errors
  • acf2c2d Merge pull request #8615 from felixfbecker/patch-1
  • 44fff70 Merge pull request #9256 from webpack/dependabot/npm_and_yarn/@types/node-10.14.9
  • 74178d4 Update snapshot
  • 7fb14ec Add name property to error thrown on chunk load failure
  • 85b0917 chore(deps-dev): bump @types/node from 10.14.8 to 10.14.9
  • 30882ca Link to JS Foundation Code Of Conduct
  • ff85fae Merge pull request #9241 from webpack/dependabot/npm_and_yarn/prettier-1.18.2

There are 30 commits in total.

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.33.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.