casvirginia.blogg.se - Install nvm on windows 10

After I restarted the terminal window, the nvm command was available to me. When I was done with that, I downloaded nvm-setup.zip from the NVM for Windows releases page and ran the installer from that archive.

Deleting the npm and npm-cache folders from the %appdata% folder.

Uninstalling Node.js from the Windows Programs & Features window.

Clearing the npm cache by calling npm cache clean -force.

I followed a great guide I found on Stack Overflow. Since I already had Node.js installed on my machine, it seemed like a good idea to do a full uninstall first. When I realized that I would also need to downgrade my Node.js installation, I decided to bite the bullet and install NVM for Windows. At first, it seemed like downgrading npm would suffice. In Visual Studio, go to Tools -> Options -> search for 'external web tools' in the searchbar.Īs shown in the image add the path to the folder where Node.js is installed to the top of the list.I have been working on older Ionic Angular projects lately that can not be built with the latest version of Node.js. net developer like me and use Visual Studio daily, there can sometimes be an issue with Visual Studio not using the Node version specified by NVM. To download the latest version just use: nvm install latest.Īnd if you want to see a list of all the commands available just enter NVM in cmd to list them all: This command lets you install different Node versions. Shows a list of available Node versions to download Now that we have NVM installed we can start using it in our terminal of choice. It's easy!įor installing on Linux and MacOS I would refer to the readme found on GitHub. How to install and use NVM on Windowsĭownload the latest version of NVM (nvm-setup.zip) from Github. All you need to do is install NVM and the versions of Node you need.

NVM (Node Version Manager) is a tool for installing and managing different Node versions.

That's a problem we can solve rather easily with NVM. If you're like me, and switch a lot between different projects, you've most likely run across problems with Node.js versions when building the frontend.