Hacker News Reader

Comment by cornedor | Hacker News Reader

`nvm install v4.0.0` and you're ready to go.

To preserve your npm packages, try:

  nvm install node --reinstall-packages-from=node

Oh that's super helpful I didn't rtfm enough, thanks for the tip.

If you don't mind fetching package locations over HTTP

https://github.com/creationix/nvm/issues/614

nvm maintainer here: the only thing that's done over HTTP is the initial redirect on http://nvm.sh, which will soon be HTTPS. This URL is only used if you type it in (because it's easy to remember).

Everything else is done over Github's super-secure HTTPS - so there's really nothing to be paranoid about.

Ah, thanks for the update

nvm install 4.0 works, do we really need the "v"?

Since it's the first and only release so far in 4.x.y, I got away with `nvm install 4`. ;)

Using `stable` is also another way.

  > nvm install stable
  v4.0.0 is already installed.
  Now using node v4.0.0 (npm v2.14.2)

nvm maintainer here: this is true - but please use `node`, since the concept of "stable" and "unstable" has died with the advent of node v4.0 using semver.

All node versions are now stable, and version numbers now communicate breakage, not stability. As it should be.

nvm maintainer here: you do not need the `v`, it will always be automatically added if you've provided a version number that doesn't already match to an existing alias.

Reply on news.ycombinator.com