nodenv
github.com
- Free plan
- macOS
- Linux
What nodenv is
nodenv manages Node.js versions so projects on one machine can use different versions. Users can set a version globally, for an individual project, or for a shell session. When a project has a .node-version file, nodenv can switch to its specified version as the user enters that directory. It places command shims in PATH so tools such as node, npm, and npx follow the selected version. Installing Node.js versions requires the separate node-build plugin; nodenv does not include an install command out of the box. Bash-written plugins can extend the tool, including plugins for installing versions and managing default npm packages. Globally installed npm packages are scoped to the currently active Node.js version. The project provides shell completion and setup instructions for Bash, Zsh, and Fish. Installation options include Homebrew, Arch Linux’s AUR, and a manual Git checkout; Debian, Ubuntu, and Fedora repositories do not currently package it. nodenv is MIT licensed and free. The project directs users to its GitHub issue tracker for bugs and pull requests.
Who it suits
nodenv suits people developing Node.js applications who need to switch versions across projects on one machine. Its documented shell setup covers Bash, Zsh, and Fish.
Good to know, and what to watch
- Selects Node.js versions per project, globally, or per shell.
- Can switch versions using a .node-version file.
- Shims route node, npm, and npx to the selected version.
- MIT licensed and free.
- Installing versions requires the separate node-build plugin.
- Debian, Ubuntu, and Fedora repositories do not package it.
Plans
Every plan and pricenodenv
Free plan
The verdict
nodenv handles version selection and switching for Node.js projects on a single machine. Users should account for the separate node-build plugin when they need to install versions.
What the maker publishes
- Audience
- The project is intended for people working on Node.js applications who need to switch versions across projects on one machine. source
- Automatic switching
- It checks a project’s .node-version file and switches Node.js versions as you move between project directories. source
- Command shims
- nodenv places shims in PATH so commands such as node, npm, and npx use the selected Node.js version. source
- Install options
- Installation options include Homebrew, Arch Linux’s AUR, or a manual Git checkout; Debian, Ubuntu, and Fedora repositories do not currently package it. source
- License
- The repository identifies the project as MIT licensed. source
- Package scope
- Globally installed npm packages are scoped to the currently active Node.js version. source
- Platforms
- The project describes nodenv as a version manager for Unix-like systems and recommends Homebrew installation on macOS or Linux. source
- Plugins
- nodenv is customizable through plugins written in Bash, including plugins for installing versions and managing default npm packages. source
- Purpose
- nodenv manages Node.js versions so projects can use the correct version on the same machine. source
- Security
- The repository links to a security policy, but the opened README does not state a security certification or compliance standard. source
- Shell support
- The project provides completion scripts for Bash, Zsh, and Fish and documents shell initialization for these shells. source
- Support
- The project directs users to file bugs in its GitHub issue tracker and submit pull requests. source
- Version installation
- Installing Node.js versions requires the separate node-build plugin; the install command is not included out of the box. source
- Version selection
- You can set Node.js versions per project, globally, or for a shell session. source
Checked against the maker's pages on 5 Oct 2026.