-
Notifications
You must be signed in to change notification settings - Fork 220
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
fix(package): downgrade source-map
v0.7.0...0.5.6
#309
Conversation
source-map
v0.7.0...0.5.6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hackeryarn Thx
@@ -31,7 +31,7 @@ | |||
"async": "^2.0.0", | |||
"loader-utils": "^1.0.0", | |||
"lodash": "^4.0.0", | |||
"source-map": "^0.7.0", | |||
"source-map": "^0.5.6", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe ^0.6.0
is ok here, according to the CHANGELOG
support for node < v8.0.0
was drop in v0.7.0
https://github.com/mozilla/source-map/blob/master/CHANGELOG.md
Breaking change: Drop support for Node < 8. If you want to support older versions of node, please use v0.6 or below.
But the CHANGELOG
sadly misses notes about the 0.6.0
release 😞, so maybe 0.5.6
is 'safer'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I figured since the project was previously on ^0.5.6
, it was safer to just revert this version bump. But I would be happy to upgrade ^0.6.0
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, let's better leave it :)
Released in |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
Install breaks on node < 8
What is the new behavior?
Install is possible on node < 8
Does this PR introduce a breaking change?
Other information:
Resolves #308