nvm

NVM for Windows is a Node.js version manager built specifically for Windows, presented as the version manager recommended by Microsoft and Google documentation for Windows developers. It is a separate project from the original nvm, which targets Mac and Linux only, and follows a different design philosophy rather than being a clone. The README highlights that version 2 is a full rewrite aimed at modern workflows, with notable changes from v1 documented on the project's documentation site. The project provides a website, documentation, and an announcements discussion category as its main resources. Key capabilities described in the README: - Compatibility: no mandatory administrator privileges; a shim mode that avoids symlinks and is written in Zig; and a link mode using junctions with symlink fallback for zero-latency switching. - Automation: per-directory version switching (pinning), automatic installation of missing versions, and automatic installation of default global modules. - Speed: parallel simultaneous installations, smaller downloads via 7z, native extraction, and caching. - Native integrations: Windows Apps, logging through Windows Event Viewer, Windows Registry, and the Desktop Notification Center. - Customization: user-defined aliases, user-defined default global modules, and configuration for local (air-gapped) downloads. The README also mentions planned commercial Certified Builds for controlled environments, listed for September 2026, with features such as code signing for installers and executables, MSI/MST and Microsoft Intune installers, advanced auditable structured logging with a dedicated event source and SIEM integration, policy enforcement including Active Directory/Entra integration, restriction of Node.js versions or ranges, control over nvm-windows and Node/npm/npx settings, advanced proxy support (IWA, WPAD/PAC), a private Node.js download mirror, and trust artifacts such as SBOM, SLSA provenance and VEX reports. Some of these are marked as add-on packages. The README closes with thanks to issue reporters, contributors and others who helped improve the project, pointing to a separate contributor list file.