Treehouse

Upgrade Node.js via NPM

By on  

I was recently installing a utility via NPM when I learned that my version of Node.js itself was out of date.  No worries -- simply upgrade my Node.js install and move forward.  Of course I could just hit nodejs.org and get the new image, but figured there had to be an easier way.  It turns out there is -- you can upgrade your local Node.js with NPM:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

The n package represents a Node helper, and running the last command upgrades node to the latest stable version.  Instead of using "stable", you could specify a desired version:

sudo n 0.8.21

Once your install is complete, you can confirm you version with another command:

node -v

It's quite nice that you can upgrade Node.js right from npm;  it's like Inception...or something.

ydkjs-4.png

Recent Features

  • Send Text Messages with PHP

    Kids these days, I tell ya.  All they care about is the technology.  The video games.  The bottled water.  Oh, and the texting, always the texting.  Back in my day, all we had was...OK, I had all of these things too.  But I still don't get...

  • 5 HTML5 APIs You Didn’t Know Existed

    When you say or read "HTML5", you half expect exotic dancers and unicorns to walk into the room to the tune of "I'm Sexy and I Know It."  Can you blame us though?  We watched the fundamental APIs stagnate for so long that a basic feature...

Incredible Demos

  • Modal-Style Text Selection with Fokus

    Every once in a while I find a tiny JavaScript library that does something very specific, very well.  My latest find, Fokus, is a utility that listens for text selection within the page, and when such an event occurs, shows a beautiful modal dialog in...

  • MooTools Typewriter Effect Plugin

    Last week, I read an article in which the author created a typewriter effect using the jQuery JavaScript framework. I was impressed with the idea and execution of the code so I decided to port the effect to MooTools. After about an hour of coding,...

Discussion

  1. Chris Hamant

    Just to be pedantic – ‘n’ isn’t something that the guys behind npm and nodejs core team created nor necessarily support.

    ‘n’ the package ‘https://github.com/visionmedia/n’ is created and maintained by the prolific TJ Holowaychuk. It’s one of many competing version managers for nodejs – https://github.com/creationix/nvm being another.

    While I do sometimes need to manage different versions of node (those tools are convenient for sure) I personally rely upon a decent package manager on my OS. ‘Homebrew’ (or MacPorts/Fink if a masochist) on OSX. ‘Chocolatey’ on Windows. (Linux users probably have it in their distro’s package manger)

    Installing via the provided packages will ensure that npm itself is up to date too (which not all other solutions do).

    • alexserver

      alright, so you recommend to brew update node ?
      nice to hear.

  2. Neat, but I prefer to build from source and install to ~/.local so I don’t have to sudo.

  3. Mehdi

    emmmm… nvm?

  4. Santi

    Anyway of doing this on windows?

  5. John

    Didn’t work for me.. :(

  6. Paul

    Thanks, this worked great for me.

    Regardless of whether ‘n’ is developed by the npm guys, I haven’t done anything special and I found it was already installed on my centos 6 system (which was set up from scratch and only has node and npm installed)

  7. Rob

    Thanks David, you are a wealth of information!

  8. MattDMo

    It’s nice to know about n, but one of its major failings (at least for me, on Linux, without ‘sudo’ privileges) is that there’s no way to define a local install path, or even one that’s not /usr/local. Back to building the source for me…

  9. David Beckwith

    It worked nicely for me. Thank you!

  10. Thanks worked for me.

  11. Works fine thx!

  12. ilker

    Did anybody get this working on Windows 7 ?
    When trying to run n (anything with n , like “n -h” or “n stable” fails saying
    ‘sh’ is not recognized as an internal or external command.

    Because in AppData\Roaming\nmp\n.cmd file there is a line trying to use sh as
    sh “%dp0\node_modules\n\bin\n” %*

    and since it does not know what sh is it does NOT work on windows 7.
    Looked at the package.json file of n , did not see any dependencies.

    What is missing ? How to get the n to work on Windows 7 ?

  13. worked for me.. cheers

  14. Tony

    I’ve been using n for sometime now and like it, seems like everyone uses nvm but I like the stuff TJ makes, he’s brilliant

  15. Borislav

    It worked like a charm! Thank you!

  16. Worked like a charm – cheers mate

  17. Vamshi

    this worked cool.. thanks

  18. Yeah, trying to figure out on windows 7 too, if anybody found a way :)
    Same behavior as iliker.

  19. It worked for me… but it killed npm. That is to say, node was update but npm command stopped working. I had to reinstall node the old way to get npm working again.

  20. Worked for me, thanks Mr Walsh!

  21. Muchas gracias! funciona perfecto!

  22. Daniel Mejia

    Gracias david. I found out about cache clean.

  23. Very useful and fast. Many thanks!

  24. mac

    I’m new in node development and just starting to learn from it.. I had an issue with npm add user and I decided to update node using the following command but after updating.. whenever I run node or npm I always got “Floating point exception” on my terminal. Please help.

    I’m using SUSE Linux sp1.

  25. Ian

    Thanks for the info. On Windows 7 installing n worked for me but then it tells me the version it tries to install is a invalid version. Since it is the very version I get from nodejs as a installer, I’m going to just say this does not work on Windows but it’s no big deal since it’s so easy to download the installer from the website.

    Will probably use this on my Linux machines if I remember so thanks :-)

  26. Carl-Erik

    Does not work on Windows 7.

    $ n stable

    install : v0.10.26

    Error: invalid version 0.10.26

    • At least it’s a version issue and not necessarily a node/n issue.

  27. Lucidz

    No version works with n in windows. They all give invalid version.

  28. marcelklehr

    Hey guys.

    Just to clear things up: N doesn’t support windows. It works Unixy operating systems, but not on windows.

    If you need a node version manager for windows, try https://github.com/marcelklehr/nodist

    cheers!

  29. Carlos Vazquez

    Thanks for the instructions, it was the only way I could have possibly pulled this out (I’ve read way too many articles)

  30. Loren Amelang

    WARNING!
    DON’T DO THIS if you are not on an x86 machine!

    I’m on ARM (BBB) and this procedure stupidly installed the x86 binary over my existing ARM version. I’m now three hours into repairing the damage.

    I knew there was trouble when I saw the response to the first command:
    ubuntu@ubuntu-armhf:~/Ldrv$ sudo npm cache clean -f
    npm WARN using –force I sure hope you know what you are doing.

    But there was no opportunity to back out by the time the message was up. Maybe if I’d stopped right there I wouldn’t be re-installing from scratch now?

    (Yes, I could apt-get a version quickly, but the repo version is too old to do https!)

    Please, David, put a big “Warning – x86 ONLY” message at the top of your page!

    Loren

  31. Absolux

    hi, it works fine for me. thank you.

    i has a troubleshotting with the npm. it doesnt recognize the registry http://registry.npmjs.org/. so before typing
    ! sudo npm install -g n
    you should type :
    $ npm config set registry http://registry.npmjs.org/

    PS: Curl must be installed also.

    thank you again.

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!