Upgrade npm to 2.14.14

[wsargent]

Merging in the webjars upgrade locally. Will need to branch / tag for 1.1.2 (or 1.2? Minor or major upgrade?)

Following on from webjars/npm#4. Tested with sbt-js-engine using sbt scripted with no errors:

> scripted
[warn] Credentials file /Users/wsargent/.bintray/.credentials does not exist
[info] Updating {file:/Users/wsargent/work/sbt-js-engine/}sbt-js-engine...
[info] Resolving org.scala-sbt.ivy#ivy;2.3.0-sbt-fccfbd44c9f64523b61398a0155784d[info] Resolving org.scala-sbt#sbt-launch;0.13.8 ...
[info] Done updating.
[info] :: delivering :: com.typesafe.sbt#sbt-js-engine;1.1.4-SNAPSHOT :: 1.1.4-SNAPSHOT :: integration :: Tue Jan 05 15:11:25 PST 2016
[info]  delivering ivy file to /Users/wsargent/work/sbt-js-engine/target/scala-2.10/sbt-0.13/ivy-1.1.4-SNAPSHOT.xml
[info] Packaging /Users/wsargent/work/sbt-js-engine/target/scala-2.10/sbt-0.13/sbt-js-engine-1.1.4-SNAPSHOT.jar ...
[info] Done packaging.
[info]  published sbt-js-engine to /Users/wsargent/.ivy2/local/com.typesafe.sbt/sbt-js-engine/scala_2.10/sbt_0.13/1.1.4-SNAPSHOT/jars/sbt-js-engine.jar
[info]  published sbt-js-engine to /Users/wsargent/.ivy2/local/com.typesafe.sbt/sbt-js-engine/scala_2.10/sbt_0.13/1.1.4-SNAPSHOT/srcs/sbt-js-engine-sources.jar
[info]  published sbt-js-engine to /Users/wsargent/.ivy2/local/com.typesafe.sbt/sbt-js-engine/scala_2.10/sbt_0.13/1.1.4-SNAPSHOT/docs/sbt-js-engine-javadoc.jar
[info]  published ivy to /Users/wsargent/.ivy2/local/com.typesafe.sbt/sbt-js-engine/scala_2.10/sbt_0.13/1.1.4-SNAPSHOT/ivys/ivy.xml
Running sbt-js-engine / jstask
Running sbt-js-engine / npm
Running sbt-js-engine / npmsubmodule
[success] Total time: 60 s, completed Jan 5, 2016 3:12:24 PM

[huntc]

Did the test pass locally for you? Fails on CI.

[wsargent]

@huntc i was running the sbt-js-module scripted tests, not the local tests -- I confused the webjars-npm with the typesafe-npm.

0 info it worked if it ends with ok
1 verbose cli [ './node',
1 verbose cli   '/Users/wsargent/work/npm/target/webjars/npm/lib/npm.js',
1 verbose cli   'update',
1 verbose cli   '--verbose' ]
2 info using npm@undefined
3 info using node@v0.10.32
4 verbose node symlink /usr/local/bin/node
5 silly mapToRegistry name amdefine
6 silly mapToRegistry using default registry
7 silly mapToRegistry registry https://registry.npmjs.org/
8 silly mapToRegistry uri https://registry.npmjs.org/amdefine
9 verbose request uri https://registry.npmjs.org/amdefine
10 verbose request no auth needed
11 info attempt registry request try #1 at 4:14:39 PM PST
12 verbose request id e5eac2081fd28759
13 verbose etag "6U9GHH4I8CAX7G1R4EWYEO1Z9"
14 http request GET https://registry.npmjs.org/amdefine
15 http 304 https://registry.npmjs.org/amdefine
16 verbose headers { date: 'Wed, 06 Jan 2016 00:14:41 GMT',
16 verbose headers   via: '1.1 varnish',
16 verbose headers   'cache-control': 'max-age=300',
16 verbose headers   etag: '"6U9GHH4I8CAX7G1R4EWYEO1Z9"',
16 verbose headers   age: '179',
16 verbose headers   connection: 'keep-alive',
16 verbose headers   'x-served-by': 'cache-sjc3131-SJC',
16 verbose headers   'x-cache': 'HIT',
16 verbose headers   'x-cache-hits': '14',
16 verbose headers   'x-timer': 'S1452039281.013962,VS0,VE0',
16 verbose headers   vary: 'Accept' }
17 silly get cb [ 304,
17 silly get   { date: 'Wed, 06 Jan 2016 00:14:41 GMT',
17 silly get     via: '1.1 varnish',
17 silly get     'cache-control': 'max-age=300',
17 silly get     etag: '"6U9GHH4I8CAX7G1R4EWYEO1Z9"',
17 silly get     age: '179',
17 silly get     connection: 'keep-alive',
17 silly get     'x-served-by': 'cache-sjc3131-SJC',
17 silly get     'x-cache': 'HIT',
17 silly get     'x-cache-hits': '14',
17 silly get     'x-timer': 'S1452039281.013962,VS0,VE0',
17 silly get     vary: 'Accept' } ]
18 verbose etag https://registry.npmjs.org/amdefine from cache
19 verbose get saving amdefine to /Users/wsargent/.npm/registry.npmjs.org/amdefine/.cache.json
20 info outdated updating [ [ '/Users/wsargent/work/npm',
20 info outdated     'amdefine',
20 info outdated     undefined,
20 info outdated     '0.1.0',
20 info outdated     '1.0.0',
20 info outdated     '0.1.0' ] ]
21 verbose install where, what [ '/Users/wsargent/work/npm', [ 'amdefine@0.1.0' ] ]
22 verbose install initial load of /Users/wsargent/work/npm/package.json
23 verbose readDependencies loading dependencies from /Users/wsargent/work/npm/package.json
24 silly cache add args [ 'amdefine@0.1.0', null ]
25 verbose cache add spec amdefine@0.1.0
26 silly cache add parsed spec { raw: 'amdefine@0.1.0',
26 silly cache add   scope: null,
26 silly cache add   name: 'amdefine',
26 silly cache add   rawSpec: '0.1.0',
26 silly cache add   spec: '0.1.0',
26 silly cache add   type: 'version' }
27 silly addNamed amdefine@0.1.0
28 verbose addNamed "0.1.0" is a plain semver version for amdefine
29 silly mapToRegistry name amdefine
30 silly mapToRegistry using default registry
31 silly mapToRegistry registry https://registry.npmjs.org/
32 silly mapToRegistry uri https://registry.npmjs.org/amdefine
33 verbose addNameVersion registry:https://registry.npmjs.org/amdefine not in flight; fetching
34 verbose get https://registry.npmjs.org/amdefine not expired, no request
35 silly mapToRegistry name amdefine
36 silly mapToRegistry using default registry
37 silly mapToRegistry registry https://registry.npmjs.org/
38 silly mapToRegistry uri https://registry.npmjs.org/amdefine
39 verbose addRemoteTarball https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz not in flight; adding
40 verbose addRemoteTarball [ 'https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz',
40 verbose addRemoteTarball   '3ca9735cf1dde0edf7a4bf6641709c8024f9b227' ]
41 info retry fetch attempt 1 at 4:14:42 PM PST
42 info attempt registry request try #1 at 4:14:42 PM PST
43 http fetch GET https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
44 http fetch 200 https://registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz
45 silly fetchAndShaCheck shasum 3ca9735cf1dde0edf7a4bf6641709c8024f9b227
46 verbose addTmpTarball /var/folders/n2/bn0zj_x90qn7q850fsd_rpx00000gn/T/npm-1539-caef3e33/registry.npmjs.org/amdefine/-/amdefine-0.1.0.tgz not in flight; adding
47 verbose addTmpTarball already have metadata; skipping unpack for amdefine@0.1.0
48 silly cache afterAdd amdefine@0.1.0
49 verbose afterAdd /Users/wsargent/.npm/amdefine/0.1.0/package/package.json not in flight; writing
50 verbose cwd /Users/wsargent/work/npm/.
51 error Darwin 10.11.2
52 error argv "./node" "/Users/wsargent/work/npm/target/webjars/npm/lib/npm.js" "update" "--verbose"
53 error node v0.10.32
54 error npm  vundefined
55 error path /Users/wsargent/.npm/amdefine/0.1.0/package/package.json.2577261896
56 error code EIO
57 error errno 5
58 error EIO:/Users/wsargent/.npm/amdefine/0.1.0/package/package.json.2577261896
59 error If you need help, you may report this error at:
59 error     <https://github.com/npm/npm/issues>
60 verbose exit [ 5, true ]

I think the "undefined" value for npm is where it breaks down. That looks like it's happening from the JS engine, which is configured for Trireme, but I don't know the Node version:

https://github.com/typesafehub/js-engine/blob/master/build.sbt#L11

Am currently wondering if Node is out of date is respect to NPM -- from release notes it looks like Node 4.2.4 is compatible with NPM 2.14.12.

Looks like Trireme only supports 0.10.x currently:

Trireme supports two versions of Node.js:

0.10.32. This is the default, fully-supported version.
0.12.7. This version is still a work in progress.
Support for Node.js 4.0 depends on more complete ES6 code in Rhino. The Rhino community is making progress on this but it will be quite some time before we are ready to support 4.0.

https://github.com/apigee/trireme#what-version-of-nodejs-does-trireme-support

[wsargent]

@huntc See above -- I don't know enough about the project to be able to fix this (or know if it's fixable without other projects being involved)

[huntc]

Nice investigations.

Unfortunately Trireme is the lowest common denominator here. We can only support what that will support.

[benmccann]

@wsargent I'm pulling in a newer version of Trireme transitively in #6. You may want to try merging that change and rebasing this PR to see if it makes any difference for you. Though the docs haven't been updated to suggest that any newer version of NPM is supported, so I'm not super hopeful

[benmccann]

@wsargent @huntc I can't reproduce the error here. I just sent a PR to upgrade to an even newer version and it worked fine: #10

[wsargent]

Closing in favor of #10