This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
This release has some bug fixes, but it's mostly about bringing support for MUCH smaller package metadata. How much smaller? Well, for npm itself it reduces 416K of gzip compressed JSON to 24K.
As a user, all you have to do is update to get to use the new API. If you're interested in the details we've documented the changes in detail.
CORGUMENTS
Package metadata: now smaller. This means a smaller cache and less to download.
86dad0d74 Add support for filtered package metadata. (@iarna)
Previously we needed to extract every package's tarball to look for an npm-shrinkwrap.json before we could begin working through what its dependencies were. This was one of the things stopping npm's network accesses from happening more concurrently. The new filtered package metadata provides a new key, _hasShrinkwrap. When that's set to false then we know we don't have to look for one.
4f5060eb3#15969 Add support for skipping npm-shrinkwrap.json extraction when the registry can affirm that one doesn't exist. (@iarna)
INTERRUPTING SCRIPTS
878aceb25#16129 Better handle Ctrl-C while running scripts. npm will now no longer exit until the script it is running has exited. If you press Ctrl-C a second time it kill the script rather than just forwarding the Ctrl-C. (@jaridmargolin)
DEPENDENCY UPDATES:
def75eebfhosted-git-info@2.4.1: Preserve case of the user name part of shortcut specifiers, previously they were lowercased. (@iarna)
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
npm just published its new version 4.5.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
v4.5.0 (2017-03-24)
Welcome a wrinkle on npm's registry API!
Codename: Corgi
This release has some bug fixes, but it's mostly about bringing support for MUCH smaller package metadata. How much smaller? Well, for npm itself it reduces 416K of gzip compressed JSON to 24K.
As a user, all you have to do is update to get to use the new API. If you're interested in the details we've documented the changes in detail.
CORGUMENTS
Package metadata: now smaller. This means a smaller cache and less to download.
86dad0d74Add support for filtered package metadata. (@iarna)41789cffanpm-registry-client@8.1.0(@iarna)NO SHRINKWRAP, NO PROBLEM
Previously we needed to extract every package's tarball to look for an
npm-shrinkwrap.jsonbefore we could begin working through what its dependencies were. This was one of the things stopping npm's network accesses from happening more concurrently. The new filtered package metadata provides a new key,_hasShrinkwrap. When that's set tofalsethen we know we don't have to look for one.4f5060eb3#15969 Add support for skippingnpm-shrinkwrap.jsonextraction when the registry can affirm that one doesn't exist. (@iarna)INTERRUPTING SCRIPTS
878aceb25#16129 Better handle Ctrl-C while running scripts.npmwill now no longer exit until the script it is running has exited. If you press Ctrl-C a second time it kill the script rather than just forwarding the Ctrl-C. (@jaridmargolin)DEPENDENCY UPDATES:
def75eebfhosted-git-info@2.4.1: Preserve case of the user name part of shortcut specifiers, previously they were lowercased. (@iarna)eb3789fd1node-gyp@3.6.0: Add support for VS2017 and Chakracore improvements. (@refack) (@kunalspathak)245e25315readable-stream@2.2.6(@mcollina)30357ebc5which@1.2.14(@isaacs)The new version differs by 882 commits .
5d17fc94.5.03f88cb8update AUTHORScac64b7doc: Fix release dates in changelogc97980bdoc: update Changelog for 4.5.0bd624bfnpm: Replace http: URL in npm-shrinkwrap with https:878aceblifecycle: On SIGINT, ensure process stays alive until child exits86dad0dextract: support minified packuments95d4fc8fetch-package-metadata: Support the _hasShrinkwrap registry metadata6400d3ascript: fix lint error30357ebcode>which@1.2.14</code245e253code>readable-stream@2.2.6</codeeb3789fcode>node-gyp@3.6.0</codedef75eecode>hosted-git-info@2.4.1</code41789cfcode>npm-registry-client@8.1.0</code63468a64.4.4There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.