And it works with multiple types of shells: Sh, Bash, Zsh, Dash, Ksh, (not Fish though).Īs long as you’re fairly comfortable with the command line, you can use NVM.Default to automatically use whichever version of Node.js is specified if a.Set up aliases to switch between different downloaded versions of Node with ease,.Download any one of those remote LTS versions of Node locally with a simple command,.Access every long term support (LTS) version of Node.js from v0.1.14 to the latest version today, which happens to be v.11.10.1, as I write this,.While it doesn’t sound complicated, what NVM can do is awesome.

Simple bash script to manage multiple active node.js versions. Node Version Manager is exactly what its name says: This was my lot in life, until a co-worker clued me in to an awesome tool called Node Version Manager (NVM).

It’s not easy, it’s something I forget to do frequently (until I have an unexplained issue during development), and frankly, it’s just not the easiest thing to do on a Mac. I’m sure I’m also not alone when I tell you that the AngularJS application will ONLY run on Node.js version 9 (it crashes and causes weird bugs if it’s not), and our React application needs Node version 10 or above to take advantage of all the ES6 and beyond features.Īnd you know what? Switching between Node environments for local development is kind of a pain. The end goal is that the React application will one day host the entire application on its own. The two work together to serve up a single user experience, while we slowly migrate over the existing screens and functionality from the old, AngularJS application into the new, React application. I’m sure I’m not alone when I tell you that my current development team owns two different UI applications: one built in AngularJS (the old one) and one built in React (the new one). NVM - a simple bash script to manage multiple active Node.js versions Multiple Node Environments are a Pain to Develop In Locally

Nvm linux