News for hackers. Stuff that matters.
Re:Node v6.6.0 by tlrobinson on Thursday September 15, 2016 @06:59PM (#12510576)
I recommend nvm on your dev machines.

    $ nvm install 6.6.0
    Downloading https://nodejs.org/dist/v6.6.0/node-v6.6.0-darwin-x64.tar.xz...
    ######################################################################## 100.0%
    Now using node v6.6.0 (npm v3.10.3)
    $ node -v
    v6.6.0
Re:Node v6.6.0 by sotojuan on Thursday September 15, 2016 @07:16PM (#12510654)
I second something like `nvm`. Even homebrew takes a long time to update their Node versions.

That said, I use `n` because for some reason `nvm` makes my shell take more than a second to startup (I've tried tons of fixes and none work).

https://github.com/tj/n

Re:Node v6.6.0 by diggan on Thursday September 15, 2016 @07:23PM (#12510693)
I have a little trick that makes nvm not impact your overall startup time.

First, put the version you commonly use in your path

  export PATH="${PATH}:/home/victor/.nvm/versions/node/v6.5.0/bin"
Then, instead of sourching nvm when your shell starts, do it when you call an alias instead.

  export NVM_DIR="/home/victor/.nvm"
  alias n=". $NVM_DIR/nvm.sh" 
Now, you have a node+npm version by default, and you can do a quick flow if you want to change

  $ n
  $ nvm install 6.6.0
  Now using node v6.5.0
Re:Node v6.6.0 by jessaustin on Friday September 16, 2016 @08:16AM (#12513469)
I thought the point of a package manager was not having to mess with stuff like that? "n" is simply better.
Re:Node v6.6.0 by diggan on Friday September 16, 2016 @04:09PM (#12516970)
Yeah, sure, but sometimes you have to go a little bit extra to have it the best...
Re:Node v6.6.0 by jbergstroem on Thursday September 15, 2016 @10:29PM (#12511489)
I do something similar to @diggan, but expand with globbing because I'm probably lazy:

  NODE_PATH=$(dirname ~/.nvm/versions/node/v6*/bin/node)
  export PATH="\
  ${NODE_PATH}:\
  ...

  export NVM_DIR="/Users/jbergstroem/.nvm"
  [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

Also, the delay that a lot of you may be experiencing has to do with npm, not nvm.
Re:Node v6.6.0 by overcast on Thursday September 15, 2016 @08:45PM (#12511145)
'n' has always worked perfectly for me. Takes all of twenty seconds to get up to date, and switching between versions is stupid simple.
Re:Node v6.6.0 by dandanisaur on Friday September 16, 2016 @01:03AM (#12511957)
I learned this subtle trick via nvm. If you use "nvm install 6" it will automatically download the latest version.
Re:Node v6.6.0 by shriek on Friday September 16, 2016 @12:45AM (#12511892)
and

  nvm reinstall-packages v6.5.0
to reinstall all your global packages from v6.5.0 or other versions.