nodenv

List available Node versions

$ nodenv install --list

$ nodenv install [18.17.0]

$ nodenv global [18.17.0]

$ nodenv local [16.20.0]

$ nodenv version

$ nodenv versions

$ nodenv uninstall [16.20.0]

$ nodenv rehash

nodenv command [options] [arguments]

nodenv manages multiple Node.js versions per-project. It uses shims to intercept Node commands and route them to the correct version.
Version selection uses a hierarchy: NODENV_VERSION environment variable, .node-version file in current/parent directories, global version setting. This enables project-specific versions without manual switching.
Installation requires the node-build plugin, included by default in most installation methods. It compiles Node.js from source or downloads binaries.
Shims are lightweight executables in ~/.nodenv/shims/ that determine the correct Node version before executing. After installing npm packages with executables, run `nodenv rehash` to create shims for them.
The .node-version file in a project root specifies the Node version. When you enter the directory, nodenv automatically uses that version. Version managers like package.json's "engines" can complement this.

install VERSION

Install Node version.

Uninstall Node version.

List installed versions.

Show current version.

Set/show global version.

Set/show local version.

Set shell-specific version.

Rebuild shim executables.

Show path for command.

List versions with command.

Show nodenv root directory.

Shell initialization.

List available versions.

List all versions including old.

Requires shell initialization in profile. New global packages need rehash. Building from source takes time. Not compatible with nvm. Some systems need build dependencies. Shims add slight overhead.

nodenv was created by Will Farrington and Jason Karns around 2014, modeled after rbenv for Ruby. It brought rbenv's proven version management model to Node.js. The plugin architecture enables customization while keeping the core simple.

nvm(1), fnm(1), volta(1), asdf(1), rbenv(1)