Skip to content
This repository has been archived by the owner on May 19, 2020. It is now read-only.

Update node/npm to new version #467

Merged
merged 4 commits into from
Jul 13, 2016
Merged

Update node/npm to new version #467

merged 4 commits into from
Jul 13, 2016

Conversation

msecret
Copy link
Contributor

@msecret msecret commented Jul 12, 2016

Updates node to version 5.12 and npm to version whatever. Main point
was to update npm to version greater then 3 because of all the features
it adds at that point.

It would be nice to merge this before any package.json updates.

Ref #331

Updates node to version 5.12 and npm to version whatever. Main point
was to update npm to version greater then 3 because of all the features
it adds at that point.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.958% when pulling d83620f on ms-upgrade_npm into ad3e187 on master.

@jeremiak
Copy link
Contributor

I'm concerned about moving to a 5.x branch because the odd numbered branches don't ever enter the NodeJS long term support schedule. Is the goal to get npm anything above 3.0? If so, I can try this with node 6.x and still use npm@3.8?

Marco Segreto added 3 commits July 12, 2016 17:06
Odd number versions of node do not have LTS, so we don't want to
move to version 5.
@jeremiak
Copy link
Contributor

This is great, I'm really impressed with how little had to change to go up two full versions of node! Plus, the way that npm3 handles dependency resolution seems to make a lot more sense and will hopefully lead to even faster install times since dependencies can be shared.

@jeremiak jeremiak merged commit ad5a94a into master Jul 13, 2016
@jeremiak jeremiak deleted the ms-upgrade_npm branch July 13, 2016 01:48
@jeremiak jeremiak mentioned this pull request Jul 18, 2016
9 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants