npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

node-version-use

v2.4.7

Published

Cross-platform solution for using multiple versions of node. Useful for compatibility testing

Readme

node-version-use

Cross-platform solution for using multiple versions of Node.js. Transparent version switching via command interception.

Installation

npm install -g node-version-use
export PATH="$HOME/.nvu/bin:$PATH"  # Add to shell profile

Quick Start

nvu default 20           # Set global default
nvu local 18             # Set project version (.nvmrc)
node --version           # Uses v20 (or v18 in project)

Commands

nvu default 20           # Global default
nvu default system       # Use system Node
nvu local 18             # Project version (.nvmrc)
nvu install 22           # Install Node
nvu uninstall 22         # Uninstall Node
nvu list                 # List installed
nvu 22 npm run test      # Run with specific version

How It Works

~/.nvu/bin/              # Go binary shims (node, npm, npx, nvu, ...)
  ↓
~/.nvu/default          # Contains "22", "20", or "system"
  ↓
~/.nvu/installed/v22/   # Real Node.js installation
  └── bin/node          # Actual Node binary

Key design decisions:

  1. Strict routing - Each command routes to exactly one version (the default)
  2. npm compatibility - Uses npm_config_prefix so npm behaves normally
  3. System escape hatch - nvu system npm ... bypasses version routing
  4. Version-specific packages - Global npm packages live in the version's directory

Frequently Asked Questions

How do I reinstall nvu if it's missing?

nvu system npm install -g node-version-use

This bypasses version routing entirely.

Are global npm packages shared across versions?

No. Each Node version has its own lib/node_modules/. Install separately:

nvu 22 npm install -g some-package
nvu 20 npm install -g some-package

Can I use system Node?

nvu default system

Routes all commands to system binaries via PATH.

Why not search all installed versions for binaries?

Explicit is better than implicit. You know exactly which version runs. Use nvu <version> <command> for specific versions.

How nvu Differs from Other Version Managers

| Feature | nvu | nvm | Volta | |---------|-----|-----|-------| | Command routing | Go binary shim | Shell function | npm shim | | Default version | Global or per-project | Global | Per-project (package.json) | | Global packages | Version-specific | Shared (via symlinks) | Pin to version | | System Node | nvu default system | nvm use system | volta off | | Recovery when broken | nvu system npm ... | Reinstall nvm | Reinstall volta |

nvu uses a single Go binary that intercepts commands. Simple, predictable routing.

nvm is a shell function that changes $NODE_HOME environment variable.

Volta pins packages to specific Node versions in package.json and uses npm shims.

JavaScript API

const nvu = require('node-version-use');
const results = await nvu('>=0.8', 'node', ['--version'], { stdio: 'inherit' });

Uninstall

nvu teardown           # Remove ~/.nvu/bin
rm -rf ~/.nvu          # Remove all data

Compatibility

  • macOS (arm64, x64)
  • Linux (arm64, x64)
  • Windows (arm64, x64)

Compatible with .nvmrc files from nvm, fnm, and other tools.