Repository navigation
0.12: why upgrade to npm 3? #72
Description
this breaks a bunch of things in my builds that use to work before, and there's no way to revert because you haven't versioned this change.
I'm seeing npm ERR! code EXDEV and npm WARN EBUNDLEOVERRIDE Replacing... messages that break my installation. when googling the first error, it seems the fix is to upgrade to node 4? why is this in a 0.12 Dockerfile then?
please either revert this change, or version it so we can choose npm v2 or npm v3. those of us on node 0.12 don't want breaking changes, please leave this to node 5.
Activity
[-]why upgrade to npm 3?[/-][+]0.12: why upgrade to npm 3?[/+]chorrell commentedon Dec 3, 2015
Historically the Node.js 0.10 and 0.12 docker images always updated npm to the latest version available. That seemed to make sense at the time when the latest version was still v2. We had a recent discussion about whether on not we should keep doing that give the new LTS release status for 0.10 and 0.12. At the time we felt that having the latest npm would be desirable, but I don't think any of us realized this would break npm installations.
@Starefossen We need to revisit #64
0.12.9 comes with npm v2.14.9 and It seems like we need to leave that way. We should do the same for 0.10.
Merge pull request #73 from chorrell/no-npm-update
chorrell commentedon Dec 3, 2015
Hi @vincentcr
The next 0.12 release will no longer include an updated npm (see #73).
Apologies for this, the last thing we wanted to do was break things.
This change should land with the next release of 0.12, which should happen Friday or early next week.
vincentcr commentedon Dec 3, 2015
thank you!