nodenv

nodenv command [options] [arguments]

nodenv manages multiple Node.js versions per-project. After injecting itself into your PATH, any invocation of `node`, `npm`, `npx`, or other Node.js executables first activates nodenv, which uses shims to intercept commands and route them to the correct version.Version selection uses a hierarchy: NODENV_VERSION environment variable, `.node-version` file in current/parent directories, then the global version setting. This enables project-specific versions without manual switching.The `nodenv install` command is provided by the node-build plugin, included by default in most installation methods (e.g., Homebrew). It downloads prebuilt binaries or compiles Node.js from source.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.

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 (`eval "$(nodenv init -)"` in .bashrc/.zshrc). New global packages need `nodenv rehash`. Building from source takes time and requires build dependencies. Not compatible with nvm. Shims add slight overhead to command startup.

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)