Skip to content

An in-range update of @nuxt/friendly-errors-webpack-plugin is breaking the build 🚨 #148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
greenkeeper bot opened this issue May 20, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented May 20, 2019

The dependency @nuxt/friendly-errors-webpack-plugin was updated from 2.4.0 to 2.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@nuxt/friendly-errors-webpack-plugin is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: build-job: Your tests failed on CircleCI (Details).

Commits

The new version differs by 23 commits.

  • 6052e5a chore(release): 2.5.0
  • 636c57c Merge remote-tracking branch 'upstream/master'
  • e02907b v2.0.0-beta.0
  • 726e3e1 chore: drop support for node < 8
  • 3ac9b8f chore: update eslint
  • a851028 chore: drop support for node < 6
  • d0393ed Merge pull request #86 from pieh/bump-chalk
  • f39834d Merge pull request #87 from 0xflotus/master
  • 0c7fe31 Merge pull request #1 from 0xflotus/patch-1
  • 41e8b3f Update README.md
  • 4c5bf97 add strip-ansi to cover for removed stripColor function in chalk
  • 3dba5db deps: bump chalk version
  • a4a0c62 Merge pull request #83 from coreyleelarson/master
  • fc65a23 Separates MultiStats vs non-MultiStats compile time logic for readability purposes and to avoid recursion.
  • 956ecc1 Merge pull request #82 from weaverryan/fix-starts-with-undefined

There are 23 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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 20, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants