23rd September 2019
I recently (accidentally!) upgraded to version 12 of node on my laptop; unsurprisingly it broke things. A few of my projects still run Gulp version 3, which isn’t compatible with node 12 and above.
Of course, I should be upgrading packages to fix vulnerabilities, etc., but in the real world that’s not always immediately possible. Thankfully, there are a few ways to downgrade or change the version of node.
The typical way to install node is (was?) with Homebrew, you can change the version but it’s fiddly and easy to forget you’ve done it, meaning you’ll be using an old version of node for all of your projects.
nvm (Node Version Manager) is a better way, as it allows you to easily switch the version of node you’re using for each project that might need a different one.
- curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash
- Close and reopen your terminal. Or open a new terminal window
nvmand it should give you a list of commands and options
Install the versions of node that you need
You can install as many versions of node that you like.
nvm install nodeto install the most recent version
nvm install 10to install the latest version of node 10 (replace
10with whatever version you need). You can specify the minor and patch versions too if needed, e.g.
nvm install 10.1.2
- Repeat for each different version you need
nvm lswill list the versions of node you have installed, with an arrow pointing at the version currently in use (normally the last one you installed)
Switch node version for a project
Now that you’ve got nvm set up, you can jump between any versions of node that you’ve installed.
There are three ways to swap node versions:
- Run a command to specify what version of node to use
- Run a command to switch to a pre-defined version of node
- Automatically switch to a pre-defined version of node when you move in/out of a directory
Run a command with the node version you need
On the face of it, this is the simplest way to do it. Just run a command to use the right version of node for a project, for example
nvm use 12 to use the highest version of node 12 that you have installed.
The problem with this method is that you need to know which version to use before you run the command. There may be an .nvmrc file in the project root which you could reference the required version for your command.
Run a command to switch to a pre-defined version
So if a project has an .nvmrc file there’s a way to switch to the version specified in there without looking in the file and typing the version in your command. Just run
When you’re finished work, just
cd out of the project folder and run
npm use again to switch back to the system default version. Note: if this doesn’t work out of the box, add an .nvmrc file with the value of default:
echo "default" > ~/.nvmrc.
The problem with this method is that you have to remember to switch back to the global version of node once you’re finished work on your project.
Auto-switch to pre-defined version
So we’ve got an .nvmrc file in the project and possibly one in your user root directory (
~/). Wouldn’t it be nice if it just changed automatically, rather than your having to run
npm use every time you jump in/out of a project folder? So it would work something like this:
cdinto your project directory
- nvm will hook up to the version of node specified in the .nvmrc file
- When finished work, navigate out of project folder
- nvm will hook up to the globally installed version of node
That would mean you:
- Never have to check for the node version number in an .nvmrc file
- Won’t run into issues because a project needs an older version of node than the one running globally
- Don’t have to worry about forgetting to switch back to the global version when you’re finished work on that project
Well, all you have to do is add a script to your Bash or Zsh config file (depending on which shell you use – those two are pretty popular). The script checks for an .nvmrc file; if there is one, it switches to the specified version of node automatically. When you move out of the folder again, it reverts back to the global version.
If using Bash
- Add this script to the bottom of your ~/.bashrc file
If using Zsh
- Add this script to the bottom of your ~/.zshrc file. Re-run the Zsh config
Posted 23rd September 2019 in Development
If you enjoyed this post and want to know when the next one is published, head to Twitter and hit ‘Follow’.@tempertemper
Or read more articles