
Once completed, open your command line and type nvm -v. Follow through and complete the installation wizard.Ĥ. Go to find the latest release and download the nvm-setup.zipģ. Uninstall the existing version of Node.js from your machineĢ. Since this is the version I used, I’ve provided some high-level notes on the installation process below.
#How to downgrade node js windows install
The steps to install this version of the utility are available on GitHub here. Conversely, i f you develop in a Windows environment (like me) then you’ll want to install NVM-Windows. The steps to install the utility are available on GitHub here. The original NVM utility was built specifically for Unix and MacOS. With this command line tool installed you can switch between the versions of Node.js being used on your computer with a single command.

NVM (not to be confused with NPM) stands for Node Version Manager and was created to elegantly handle this exact situation. Luckily after a quick search I found a tool that is both maintained and highly regarded by the front-end development community. Are we really going to need to uninstall and reinstall different version s of Node.js every time we switch between environments? Are we going to have to do the same thing for the Angular-CLI? How much time are we going to lose? I found myself in this situation recently and was frustrated with the time lost within the first day. However, because of Application 1’s strict dependency on Node versions we have a troublesome situation. In normal circumstances we could install the latest version of Node.js and that would be enough to allow us to develop against both applications. Application 2 is a greenfield project and uses Angular 9 which will work with the latest version of Node.js.
#How to downgrade node js windows code
Application 1 is production code that uses Angular 6 and has a custom build process that strictly depends on version 8.9 of Node.js. Let’s imagine you’re working on two Angular applications.

If you are working with applications whose front-end development processes depend on different versions of Node.js, your workflow can quickly grind to a halt.

As web developers, it is not uncommon for us to switch back and forth across different code bases throughout our day.
