nvm vs n!

Working with multiple NodeJS projects gave me a reason to look for a version manager for NodeJS. Having worked with Ruby, first thought came to mind would be a tool similar to rvm (https://rvm.io/).

Sure enough, there was nvm (https://github.com/creationix/nvm). After a couple of days, found it annoying to see some aliases that were sticky like the ancient iojs. Though easy to use, it required the IDE’s to provide full ~/.nvm path.

Now, comes along my savior npm package “n” (https://github.com/tj/n). n provides similar functionality of nvm but n will move node files to the same user path. Thus saves the annoyance of linked path by nvm.

path to node will always be at the same place

I used yarn to install n globally along with specifying user directory for developer tooling. Installing and switching versions is just as easy.

Adding n using yarn globally
installing version 4.4.3 (so short and cool right? 👍🏽 )
Switching is easy