nvm-windows

What does it mean for a Windows Node.js version manager to be written in Go? The project's own description calls it ironic, and the README now points at a successor named Runtime.

The description on GitHub is worth reading twice: a Node.js version management utility for Windows, ironically written in Go. The README takes care to distinguish this project from the original nvm, which is for Mac and Linux only. nvm-windows is not a clone, it uses a different philosophy. The project is MIT licensed and has collected over 47,000 stars, which suggests the Windows gap it fills is real.

The most notable thing in the README right now is the announcement of Runtime, described as the successor to NVM for Windows. The latest version is presented as a transition version while the team completes Runtime. There is also a known bug that can affect some users when installing old end of life versions of Node.js, and the last stable version supports most end of life versions. The README notes that some companies need specific features from both versions, which is not possible with the current public releases.

The README is careful to say the tool has always been a node version manager rather than an io.js manager, with Node 4 and later supported. Running nvm install or nvm use usually requires administrative rights because the tool creates symlinks. Common commands include nvm install latest and nvm install lts, and the stated reason to switch versions is testing modules against different Node versions.

The install notes carry a few warnings. The README recommends uninstalling any prior Node installation before installing the tool to avoid pitfalls. It also says NVM for Windows can take over management of an existing installation depending on user permissions, and it warns about closed environments such as corporate Active Directory setups. For the Runtime successor, the project asks for feedback through a form and posts updates on a company LinkedIn page.

• Source 1 · Project repository
• Source 2 · README