5 ms·

dang it i just installed 6.5 this morning

by dmh2000 10y ago

tlrobinson 10y ago
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
- sotojuan 10y ago
  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 https://github.com/tj/n
  - diggan 10y ago
    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
    - jessaustin 10y ago
      I thought the point of a package manager was not having to mess with stuff like that? "n" is simply better.
      - diggan 10y ago
        Yeah, sure, but sometimes you have to go a little bit extra to have it the best...
  - overcast 10y ago
    'n' has always worked perfectly for me. Takes all of twenty seconds to get up to date, and switching between versions is stupid simple.
  - jbergstroem 10y ago
    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.
- shriek 10y ago
  and nvm reinstall-packages v6.5.0 to reinstall all your global packages from v6.5.0 or other versions.
- dandanisaur 10y ago
  I learned this subtle trick via nvm. If you use "nvm install 6" it will automatically download the latest version.

dang it i just installed 6.5 this morning

by dmh2000 10y ago

dang it i just installed 6.5 this morning

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

sotojuan 10y ago
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 https://github.com/tj/n
- diggan 10y ago
  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
  - jessaustin 10y ago
    I thought the point of a package manager was not having to mess with stuff like that? "n" is simply better.
    - diggan 10y ago
      Yeah, sure, but sometimes you have to go a little bit extra to have it the best...
- overcast 10y ago
  'n' has always worked perfectly for me. Takes all of twenty seconds to get up to date, and switching between versions is stupid simple.
- jbergstroem 10y ago
  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.
shriek 10y ago
and nvm reinstall-packages v6.5.0 to reinstall all your global packages from v6.5.0 or other versions.
dandanisaur 10y ago
I learned this subtle trick via nvm. If you use "nvm install 6" it will automatically download the latest version.