![]() ![]() Unzip the folder's contents and run nvm-setup.exe. "Similar, not identical" as the project itself discloses. Note that this is not the same as the UNIX-based NVM project, although it is functionally equivalent. Go to the NVM for windows project page and download the latest available version's nvm-setup.zip from the releases page. In case you already have node installed this should not be a major problem as NVM will overwrite any node-related environment variables and symlinks, but I'd recommend you to uninstall it anyway as this process will render the current installation completely useless. Now, instead of installing node.js from the official website, we should install the Node Version Manager and download node versions from there. ![]() Installing this terminal is highly recommended if you plan to develop on Windows, using node.js or else. This is a hardware-accelerated tabbed terminal from which you can run Powershell, CMD or WSL interfaces, and a touchstone (and, some would say, pretty belated) step to approach Windows development experience to other major OS's. ![]() ![]() If not, open the Microsoft Store and download it free of charge. If you are using Windows 11, good news: you already have the Windows Terminal installed. Then this guide is for you, let's set up a Windows machine for node.js version with multiple version management, while also addressing common pitfalls. You are also aware that there are multiple node.js versions in active development and it is fairly common to find projects in the wild that only run in a handful of them. So you want to develop using the Javascript run-everywhere platform in the same computer in which you game, edit videos, code C# desktop apps or whatever. ![]()
0 Comments
Leave a Reply. |