deps: upgrade to npm 2.14.12

[zkat]

Hiii!

This PR includes two releases:

• https://github.com/npm/npm/releases/tag/v2.14.11
• https://github.com/npm/npm/releases/tag/v2.14.12

The main thing to note is a hopefully welcome update to our licensing to clarify scope of both the open source side and the registry TOS. There's a further clarification coming later this week, so we're not done with that bit yet -- so keep an eye out for v2.14.13.

This PR supersedes #4003, but have a look-see over there for some discussion. That PR should be closeable, though. #4033 was closed because I made it against the wrong branch. Sorry about that. :)

r: @jasnell
r: @Fishrock123
r: @chrisdickinson
r: @thealphanerd

[MylesBorins]

I was unable to apply the patch with git am but it cleanly cherry-picked onto v4.x-staging

[Fishrock123]

make test-npm gives two errors.

1st as expected:

test/tap/prune.js ................................... 16/17 npm install not ok Should not get data on stderr: WARN engine [email protected]: wanted:{"node":"*"} (current:{"node":"4.2.3-pre","npm":"2.14.12"}) at: file: test/tap/prune.js line: 57 column: 7 stack: | test/tap/prune.js:57:7 f (node_modules/once/once.js:17:25) ChildProcess.<anonymous> (test/common-tap.js:56:5) maybeClose (internal/child_process.js:818:16) Socket.<anonymous> (internal/child_process.js:319:11) Pipe._onclose (net.js:469:12) 

2nd also happens with v3.5.0 (I think?), not sure what's up here:

test/tap/circular-dep.js .............................. 8/9 installing a package that depends on the current package not ok no error output at: file: test/tap/circular-dep.js line: 48 column: 9 stack: | test/tap/circular-dep.js:48:9 f (node_modules/once/once.js:17:25) ChildProcess.<anonymous> (test/common-tap.js:56:5) maybeClose (internal/child_process.js:818:16) Socket.<anonymous> (internal/child_process.js:319:11) Pipe._onclose (net.js:469:12) 

[MylesBorins]

I was seeing both of those myself fwiw

[zkat]

@thealphanerd@Fishrock123 This is the thing where you have to set node to be a release, not a prerelease. See #4003 (comment)

[Fishrock123]

@zkat ah ok I didn't realize both were from that. :)

LGTM

@thealphanerd Would you prefer to land it?

[zkat]

@Fishrock123 sec. After #3959 (comment), I have updated the LICENSE file for node accordingly, so please re-review.

@jasnell See new commit! Is this alright now?

[jasnell]

@zkat ... I haven't had a chance to review the entire PR so I can't give an LGTM but the new commit is exactly what I needed! Thanks!

[MylesBorins]

I have confirmed using diff that the resulting LICENSE is identical to that found on https://github.com/npm/npm/blob/master/LICENSE

LGTM

[jasnell]

LGTM. This shouldn't land until the corresponding PR for master also lands tho.

[jasnell]

derp.. nevermind.. sigh. I keep forgetting that master and v5.x are on npm3. sigh.

[Fishrock123]

Tests passed, for the record. cc @jasnell

Edit: with node_version.h modified to look like a release

[jasnell]

@zkat, this PR is not landing cleanly on v4.x-staging for me for some reason. Can you take a moment to do a quick rebase and update then I'll get it landed.

[Fishrock123]

@jasnellgit am -3

[jasnell]

@zkat nevermind :-) @Fishrock123 .. thanks :-)

Landed in fff8132 and 4f8d557