Coming from nvm
An nvm alternative for Mac
Last checked 17 November 2026
In short: nvm is a free shell script that installs Node.js versions and switches between them when you run nvm use. Termhint is a paid Mac app that reads the same .nvmrc files and switches Node on its own as you change folders, checks each download against Node's release signature, and moves your global npm packages when you leave nvm. It also manages Python, Ruby, Go, Java, Xcode and more (all languages). If you need nvm on Linux, an Intel Mac or a POSIX shell other than zsh and bash, keep nvm.
How nvm works
- A sourced shell function. nvm's install script clones the project to
~/.nvmand adds lines to~/.zshrcor another profile file that loadnvm.sh. That is whywhich nvmfinds nothing: nvm is a shell function, not a program. .nvmrcis read when you ask.nvm use,nvm installandnvm whichlook for.nvmrcin the folder and its parents. Switching on everycdtakes a snippet in your profile; the README offers recipes contributed by users and says they are not supported by the maintainers.- Downloads from nodejs.org, with a checksum. The README shows nvm computing a sha256 checksum and comparing it after the download. Where nodejs.org has no binary for the platform, nvm compiles Node from source by default, which needs a C++ toolchain.
- Global packages per version.
nvm install --reinstall-packages-from=…andnvm reinstall-packagescopy global npm packages from one Node version to another.
From nvm's README on 17 November 2026.
What changes with Termhint
| nvm | Termhint | |
|---|---|---|
| What it is | Shell function, open source, free | Mac menu-bar app with a termhint command; paid after a 7-day trial |
| Switching by folder | nvm use, or a profile snippet you add | Automatic in zsh and bash as you change folders, with shell builtins only |
| Version files | .nvmrc | .nvmrc, .node-version, .tool-versions |
| Download check | sha256 checksum | SHASUMS256.txt must carry a valid signature from a Node release key; a missing signature is a refusal |
| Builds | Binary, or compiled from source as a fallback | Prebuilt only; nothing is compiled |
| Platforms and shells | sh, dash, ksh, zsh, bash; macOS, Linux, WSL | zsh and bash; macOS 14+ on Apple silicon |
| Other languages | Node only | 13 more languages and Xcode |
nvm column: nvm README, 17 November 2026.
Your .nvmrc files keep working
Termhint walks up from the current folder and uses the nearest .nvmrc, .node-version or .tool-versions line for Node. It reads the first version in the file and skips comments. The common nvm spellings work:
In .nvmrc | Termhint uses |
|---|---|
20 or v20 | The newest Node 20 you installed |
lts/* | The newest LTS you installed |
lts/iron | The newest Iron LTS (Node 20) you installed |
node | The newest Node you installed (never a pre-release) |
system | Leaves Node alone |
The file is read as data and never run. If a folder asks for a Node you don't have, the shell prints one line with the install command; nothing installs on cd. To check a folder:
$ termhint runtime current
node lts /Users/you/.local/share/termhint/runtimes/node/22.23.5 (/Users/you/app/.nvmrc)
termhint runtime use node 20 pins a folder by writing .tool-versions, not .nvmrc. Where both files exist in one folder, .tool-versions wins.
The nvm commands you know
| nvm | Termhint |
|---|---|
nvm install 22 | termhint runtime install node 22 |
nvm install --lts | termhint runtime install node lts |
nvm ls-remote | termhint runtime list-remote node |
nvm ls | termhint runtime list node |
nvm alias default 22 | termhint runtime use -g node 22 |
nvm exec 20 npm test | termhint runtime exec node@20 -- npm test |
nvm uninstall 20.20.2 | termhint runtime uninstall node 20.20.2 |
termhint runtime exec is for scripts, cron jobs and CI steps on your Mac, where no prompt runs. Editors and GUI apps can point at ~/.local/share/termhint/runtimes/node/default.
Leaving nvm without losing your global packages
termhint runtime migrate nvm --dry-run # the plan: versions, packages, lines to turn off
termhint runtime migrate nvm # do it
termhint runtime migrate --undo # turn nvm's lines back on, byte for byte
termhint runtime migrate --remove nvm # also remove nvm, once everything moved
- Each Node version you have in nvm is downloaded again from nodejs.org and checked. Nothing is copied from
~/.nvm. - nvm's default becomes Termhint's default.
- The global npm packages of each version are reinstalled into the matching Termhint version. Packages you added with
npm linkare listed, not moved. - nvm's lines in
~/.zshrc,~/.zprofile,~/.bash_profile,~/.bashrcand~/.profileare backed up, then turned off with#termhint-off#in front. - With
--remove(or "Also remove nvm" in Settings), nvm is uninstalled with Homebrew if Homebrew installed it, and its folders go to the Trash, only once every version installed and every package moved. Otherwise its folders stay and you see what did not move.
The same steps are a button: Settings → Runtimes → Other Managers → Replace with Termhint. fnm, Volta and nodenv can be taken over the same way.
Keep nvm if…
- You also work on Linux or WSL, or on an Intel Mac. Termhint is for Apple-silicon Macs on macOS 14 or later.
- You use sh, dash, ksh or fish. Termhint switches versions in zsh and bash.
- Your Dockerfiles or CI images use nvm. nvm's README covers Docker and CI setups; Termhint is a desktop app.
- You need Node versions without a macOS binary for your Mac, which nvm can compile from source. Termhint lists only prebuilt releases.
- Node is the only runtime you manage and you are happy with
nvm use. nvm is free and open source; Termhint costs money.
What it costs
Every feature works for 7 days with no account and no card. After that, a one-time license: $11.99 for 1 Mac, $19.99 for 3, $29.99 for 5 (pricing). The same license covers autocomplete, prompt themes and terminal colors. Node versions you installed keep working if the license lapses.
Termhint is not affiliated with nvm or the OpenJS Foundation.