An Angular project’s CLI version is in the package.json file, but what about the Node version? That is a piece of information that must be documented, and as we all know well, documentation is almost always left behind.Įach Angular version is compatible with a range of Node versions. Not only is this a time-wasting process, it is susceptible to errors from missing information. I must admit that the first time this switch was needed, I naively downgraded both Node and Angular CLI… Only to then upgrade them again when I went back to working on my current project. So I eventually came to a point where I needed to actively work on my current project but be able to quickly switch back to any of the other projects. Not only that, but all of these projects had at least one Node based component and a big part of them also used Angular as their Frontend framework.

Head over to Github and download nvm-setup.zip from the list of available options and follow through a regular installation process, nothing new.įurther information on installing NVM on windows can be found here.In my line of work as a Web Engineer, I have leaped through a decent amount of projects in a not so big amount of time.

Now before you install NVM, be sure to uninstall any existing installation of Node from your system to avoid complications during installation. Just as the name implies, nvm manages our Node version. Node Version Manager (NVM) is a tool that allows developers to easily switch between multiple node versions without having to manually uninstall and install a new version anytime the need arises. Hence, the motivation for writing this article. I recently had a similar challenge where my system is running Node v 16.14.2 which is the latest version at the time, and the project I want to work on required Node v 16.8.0. In this post, I will share how you can switch between multiple versions of Node and manage your projects easily using Node Version Manager(NVM) on windows.Īs developers, we work on many projects that run on different versions of packages. What happens when you need to work on a project that requires a previous version of Node? Do you have to uninstall the current version and install the version you need? what happens after you finish working on the project? And quite often, these tools and packages get updated. We build projects based on a specific version of tools, dependencies, and packages.

Nvm change node version