You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version is covered by your current version range and after updating it in your project the build failed.
As source-map-support is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details
After pinning to 0.4.15 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 0.4.16 of source-map-support just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As source-map-support is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Commits
The new version differs by 9 commits.
6c3f308
0.4.16
2c8176b
Update compiled file
9addc16
Merge pull request #138 from Yogu/fix-out-of-range-columns
6020c02
Merge pull request #187 from evanw/update-travis
d74b70d
Fix tests on Node.js >=8.4
7cfd425
Add all supported releases to Travis
df2d24f
Merge pull request #185 from tisba/patch-1
77b7f52
updates link in README to V8 Stack Trace API
58a1169
Defensive coding to prevent out-of-range column
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: