In comparison to the previous time, it was a breeze, making this a fun experience! Install Software with wingetĪfter the initial installation (and updates), the first step is to make sure that winget is installed, and that it's updated to the latest version. This time, a lot in the Windows eco-system has changed. The last time that I configured my machine is a couple of years ago, and I remember that there were lots of sighs involved. Getting a new "toy" is always exciting but it's a double feeling because a new development environment involves manual work (remember what software to download, browse to the download page, step-through the install wizard), which is time-consuming. In just a few hours I was up and running, let's take a look at my setup as a full-stack. 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.In the first week of 2022, I had the joy to receive a new machine from my new employer dotNET lab. 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.
0 kommentar(er)
