-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
deps: upgrade npm to 2.7.1 #1142
Conversation
Every npm version bump requires a few patches to be floated on node-gyp for io.js compatibility. These patches are found in 03d1992, 5de334c, and da730c7. This commit squashes them into a single commit. PR-URL: nodejs#990 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
(I pinged @rvagg on twitter, maybe we can get a npm-specific CI test to make reviewing these more reliable multiplatform?) |
My bad, looks like there is a CI task for it now! https://jenkins-iojs.nodesource.com/job/iojs+npm+any-pr+multi/2/ Edit: looks like the node symlink may not be working on some CI platforms? |
@Fishrock123 to expand on the earlier conversation: the test-npm Jenkins job initially exists to give @othiym23 a place to refine his test suite to make it work for us, don't expect it to actually work yet hence the This PR gets an LGTM from me. |
PR-URL: #1142 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Rod Vagg <rod@vagg.org>
npm@2.7.1
is a pretty hefty release. I've included the four most significant changes below, and there are many others in the full release notes.6823807
#7121
npm install --save
for Gitdependencies saves the URL passed in, instead of the temporary directory used
to clone the remote repo. Fixes using Git dependencies when shrinkwwapping.
In the process, rewrote the Git dependency caching code. Again. No more
single-letter variable names, and a much clearer workflow.
(@othiym23)
abdd040
read-package-json@1.3.2
: Provide more helpful error messages when JSONparse errors are encountered by using a more forgiving JSON parser than
JSON.parse. (@smikes)
c56cfcd
#7525
npm dedupe
handles scopedpackages. (@KidkArolis)
4ef1412
#7075 If you try to tag a release
as a valid semver range,
npm publish
andnpm tag
will error early insteadof proceeding. (@smikes)
I've also applied the floating patch to
node-gyp
to make it work properly with io.js