Nvm has been a lifesaver for me, especially when troubleshooting issues in projects where the user may have more than one Node.js version. You can set the default Node.js version by using alias: If you're done with a version and want it gone, you can do that too: If you want to check out what versions of Node.js are installed on your machine, you can use the ls option: That's where you can use nvm to download, install, and use different versions of Node.js:Īt any given time you can switch to another with use: If you work with a lot of different Node.js utilities, you know that sometimes you need to quickly switch to other versions of Node.js without hosing your entire machine. There are only two easy steps for installation and configuration. You can read the installation steps on the nvm GitHub page. An easy fix for this though is to just consolidate all of the customizations to the terminal load process into the. Little did I know that I was only off by one letter: n vm is the ideal solution. A kind user on Stack Exchange explains that on OS X, every time terminal is run it considers it a login terminal which uses the.
The shell commands within that post work great but there were reports in the comments that it could mess with node module paths and such - a far from ideal situation.
A while back I wrote a blog post called Upgrade Node.js with NPM.
0 kommentar(er)
