8000 An in-range update of source-map-support is breaking the build 🚨 · Issue #105 · zeekay/bebop · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Open
greenkeeper bot opened this issue Jul 31, 2019 · 4 comments
8000 Open

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

greenkeeper bot opened this issue Jul 31, 2019 · 4 comments
Labels
greenkeeper

Comments

@greenkeeper
Copy link
Contributor
greenkeeper bot commented Jul 31, 2019

The dependency source-map-support was updated from 0.5.12 to 0.5.13.

🚨 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 could not complete due to an error (Details).
Commits

The new version differs by 4 commits.

  • 4a9c45d 0.5.13
  • c4453fd Update built files
  • bfc73f9 Merge pull request #249 from evanw/LinusU-patch-1
  • 4852362 Tweak regex in retrieveSourceMapURL

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 Jul 31, 2019

After pinning to 0.5.12 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 28, 2019

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

  • 8cb9300 0.5.14
  • 4715e2d Update built files
  • 8a92ccf Merge pull request #253 from JLHwung/fix-function-name-logic
  • 3f4006b fix: function name should be obtained from next frams’s position

See the full diff

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Oct 28, 2019

Your tests are still failing with this version. Compare changes

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

@greenkeeper
Copy link
Contributor Author
greenkeeper bot commented Oct 30, 2019

Your tests are still failing with this version. Compare changes

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
Assignees
No one assigned
Labels
greenkeeper
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants
0