NVS Node.js Version Manager

Manage Node.js versions using NVS (Node Version Switcher). Use when switching Node.js versions, installing new versions, managing version aliases, or when th...

Security Scan

The skill's files, instructions, and scripts are consistent with a Node.js version manager (NVS); it clones the official NVS repo and provides expected install/use commands.

Purpose & Capability

The skill's name and description match the provided SKILL.md, examples, and scripts. All required actions (installing, switching, listing Node versions) are directly related to NVS. Required artifacts (git clone of jasongin/nvs, NVS_HOME usage) are appropriate for this purpose.

Instruction Scope

Runtime instructions are limited to checking for nvs, cloning the official GitHub repo, sourcing nvs.sh, and running nvs commands. The scripts read only expected local files/variables (e.g., NVS_HOME, .node-version) and do not attempt to read unrelated system files or transmit data to unexpected endpoints.

Install Mechanism

There is no platform install spec; the included install script uses git clone from the official jasongin/nvs GitHub repository and sources the project's install script. This is a standard, low-risk approach (no obscure URLs or third-party binaries).

Credentials

The skill requests no credentials or config paths. It references NVS_HOME/NVS_NODE_HOME, which are appropriate and expected for an NVS installer. No unrelated secrets or environment variables are requested.

Persistence & Privilege

The install script will place NVS under the user's home (~/.nvs) and the upstream NVS install process typically adds shell sourcing so nvs is available in future shells (i.e., it introduces persistent shell integration and changes to PATH). This is expected for a version manager but is a persistent change the user should be aware of.

Assessment

This skill appears coherent and safe for its stated purpose. Before running: (1) review the install_nvs.sh and check_nvs_status.sh scripts locally to confirm you’re comfortable with cloning from https://github.com/jasongin/nvs; (2) expect the NVS install to modify your shell environment (PATH/profile) so that nvs is available in future sessions; (3) run the scripts in an environment you control (or sandbox) if you want to avoid persistent changes; (4) on Windows prefer the suggested winget/choco methods rather than running the Unix shell install script. If you need greater assurance, inspect the upstream jasongin/nvs repository directly before proceeding.

NVS (Node Version Switcher) is a cross-platform tool for managing multiple Node.js versions. It allows you to easily install, switch between, and manage different Node.js versions and their associated npm packages.

Quick Start

Check if NVS is installed

nvs --version

If NVS is not installed, install it first

Windows (PowerShell or Command Prompt)

# Using winget (Windows 11+)
winget install jasongin.nvs

# Or using chocolatey
choco install nvs

# Manual installation
$env:NVS_HOME="$env:LOCALAPPDATA\nvs"
git clone https://github.com/jasongin/nvs "$env:NVS_HOME"
. "$env:NVS_HOME\nvs.ps1" install

Mac/Linux

export NVS_HOME="$HOME/.nvs"
git clone https://github.com/jasongin/nvs "$NVS_HOME"
. "$NVS_HOME/nvs.sh" install

Basic Commands

Install Node.js versions

# Install latest version
nvs add latest

# Install latest LTS version
nvs add lts

# Install specific version
nvs add 18.20.0

# Install with specific architecture
nvs add 18.20.0/x64

Switch between versions

# Use a version in current shell session
nvs use 18.20.0

# Use LTS version
nvs use lts

# Set default version (permanent)
nvs link 18.20.0

# Remove default link
nvs unlink 18.20.0

List versions

# List locally installed versions
nvs ls

# List available remote versions
nvs ls-remote

# Filter remote versions
nvs ls-remote 18
nvs ls-remote lts

Remove versions

nvs rm 16.20.0

Advanced Features

Automatic version switching

Enable automatic switching based on .node-version or .nvmrc files:

# Enable auto-switching
nvs auto on

# Disable auto-switching
nvs auto off

# Manual trigger for current directory
nvs auto

Version aliases

# Create an alias
nvs alias myproject 18.20.0

# List all aliases
nvs alias

# Remove an alias
nvs alias myproject

Run commands with specific versions

# Run a script with specific Node version
nvs run 18.20.0 app.js

# Execute a command with specific version
nvs exec 18.20.0 npm test

Migrate global packages

# Migrate global npm packages from one version to another
nvs migrate 16.20.0 18.20.0

Remote configuration

# List configured remotes
nvs remote

# Add custom remote (e.g., nightly builds)
nvs remote add nightly https://nodejs.org/download/nightly/

# Use custom remote
nvs add nightly/18

Common Workflows

Project Setup Workflow

1. Check if project has .node-version or .nvmrc file
2. If NVS not installed, install it
3. Install required Node.js version
4. Enable auto-switching if needed
5. Verify the correct version is active

Version Upgrade Workflow

1. Check current version: nvs ls
2. Install new version: nvs add latest
3. Test with new version: nvs use latest
4. Migrate global packages if needed: nvs migrate <old> <new>
5. Set as default if satisfied: nvs link latest

Troubleshooting

• If nvs command not found, ensure NVS is properly installed and shell is restarted
• Check NVS_HOME environment variable points to correct directory
• Use nvs which <version> to verify version paths
• For permission issues on Mac/Linux, check NVS installation directory permissions

Environment Variables

• NVS_HOME: Directory where NVS stores Node.js versions (default: ~/.nvs on Mac/Linux, %LOCALAPPDATA%\nvs on Windows)
• NVS_NODE_HOME: Alternative location for Node.js installations

Integration with VS Code

NVS integrates with Visual Studio Code for debugging with specific Node.js versions. Configure in .vscode/launch.json:

{
  "runtimeArgs": ["18.20.0"],
  "windows": { "runtimeExecutable": "nvs.cmd" },
  "osx": { "runtimeExecutable": "nvs" },
  "linux": { "runtimeExecutable": "nvs" }
}