Repository navigation
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
depsDescription of Changes
Here it is! It's been a long time coming, what with conference season, vacations, and everyone getting sick, but I think folks have been expecting this one for a bit. This is another fairly sizeable release, as far as impact goes, and did include some refactoring, but it's been sitting in
@nextfor a week and has gotten some use from folks, so we think it's ready to bump in Node!The most important thing with this release is, probably, that npm now works with
node@9out of the box. Previously, y'all had floated a patch over 5.5.1, but this change integrates it directly. πOther changes of note to node folks:
npm/npm@66d18280cnpm/npm#19104 Add new--node-optionsconfig to pass through a customNODE_OPTIONSfor lifecycle scripts. (@bmeck)npm/npm@c930e98adnpm-lifecycle@2.0.0: npm'snode-gypis now included as part of an external library,npm-lifecycle, so any future PRs by Node folks to bump or adjustnode-gypversions should be made against https://github.com/npm/lifecycle instead. (@zkochan)bc263c3fd#19054 Fully cross-platformpackage-lock.json. Installing a failing optional dependency on one platform no longer removes it from the dependency tree, meaning thatpackage-lock.jsonshould now be generated consistently across platforms! π (@iarna)Changelogs
v5.6.0