Run a command to specify what version of node to use.There are three ways to swap node versions: Now that you’ve got nvm set up, you can jump between any versions of node that you’ve installed. That middle ‘ node’ is what tells you whatever the latest version version is will be the default. Now when you use nvm ls you’ll see something like default -> node (-> v12.19.0) just after all the node versions you’ve got installed. You’re probably going to want to set the default version of node as the most up to date version. nvm ls will list the versions of node you have installed, with an arrow pointing at the version currently in use (normally the last one you installed).Repeat for each different version you need.You can specify the minor and patch versions too if needed, e.g. nvm install 10 to install the latest version of node 10 (replace 10 with whatever version you need).nvm install node to install the most recent version.You can install as many versions of node that you like. Install the versions of node that you need Type nvm and it’ll give you a list of commands and options if you’ve installed it successfully.Close and reopen your terminal, or open a new terminal window.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. 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. Thankfully, there are a few ways to downgrade or change the version of node. Of course, I should be upgrading packages to fix vulnerabilities, etc., but in the real world that’s not always immediately possible. A few of my projects still run Gulp version 3, which isn’t compatible with node 12 and above. I recently (accidentally!) upgraded to version 12 of node on my Mac unsurprisingly it broke things.
0 kommentar(er)
