Skip to content

deps: upgrade npm to 5.6.0 - #17535

Closed
zkat wants to merge 1 commit into
nodejs:v9.x-stagingfrom
npm:npm-5.6.0
Closed

zkat wants to merge 1 commit into
nodejs:v9.x-stagingfrom
npm:npm-5.6.0

Conversation

@zkat

@zkat zkat commented Dec 7, 2017

Copy link
Copy Markdown
Contributor
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)
  • deps
Description 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 @next for 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@9 out 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@66d18280c npm/npm#19104 Add new --node-options config to pass through a custom NODE_OPTIONS for lifecycle scripts. (@bmeck)
  • npm/npm@c930e98ad npm-lifecycle@2.0.0: npm's node-gyp is now included as part of an external library, npm-lifecycle, so any future PRs by Node folks to bump or adjust node-gyp versions should be made against https://github.com/npm/lifecycle instead. (@zkochan)
  • bc263c3fd #19054 Fully cross-platform package-lock.json. Installing a failing optional dependency on one platform no longer removes it from the dependency tree, meaning that package-lock.json should now be generated consistently across platforms! πŸŽ‰ (@iarna)
  • A whole slew of bugfixes, including some for platforms like Docker and Windows which should fix further issues.
Changelogs

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

npm Issues and PRs related to the npm client dependency or the npm registry.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants