Skip to content
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

An in-range update of source-map-support is breaking the build 🚨 #227

Open
greenkeeper bot opened this issue Oct 28, 2019 · 3 comments
Open

An in-range update of source-map-support is breaking the build 🚨 #227

greenkeeper bot opened this issue Oct 28, 2019 · 3 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 28, 2019

The dependency source-map-support was updated from 0.5.14 to 0.5.15.

🚨 View failing branch.

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

source-map-support 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 🚢 0.5.15
  • 🐛 Adapt to node's removal of the module header
Commits

The new version differs by 5 commits.

  • e2fcc4c 0.5.15
  • 3315173 Update built files
  • a64d497 Merge pull request #255 from tapjs/node-header-length-change
  • b2e96dd test: SyntaxError may quote unexpected token
  • 27606c1 fix: Adapt to node's removal of the module header

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 Oct 28, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by commits ahead by 0, behind by 5.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 28, 2019

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Oct 30, 2019

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Release Notes for 🚢 0.5.16
  • 🐛 Fix "cannot read property 'name' of undefined" error
Commits

The new version differs by 5 commits.

  • 61ebf23 0.5.16
  • 1c708c1 Update built files
  • a29a7e4 Merge pull request #261 from 6utt3rfly/fix/260-name-of-undefined
  • 27ca2df Simplify null/undefined check
  • e5aff39 Fix #260 - name of undefined (line 379)

See the full diff

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