Every nvm user knows this loop. You install a CLI globally, it works, then a week later nvm use 18 for some legacy project and the command is gone. Not broken — gone. command not found. Because nvm doesn't have global packages; each node version has its own lib/node_modules, and switching versions swaps the entire world out from under you.
The standard answers are all bad. nvm reinstall-packages copies everything between versions, which is a sledgehammer and reinstalls things into versions where they don't belong. --default-packages only helps at install time. And "just use npx" means cold-starting your tools through the network.
So I built with the reasoning and, where it exists, the terminal receipt. Four real bugs got caught before a single user existed. I'd rather ship the bug list myself than read it in the issues.
Try it
npm i -g nvmpin
nvmpin setup
nvmpin add <your-most-missed-cli> --node 22
POSIX only (macOS/Linux), node ≥ 18, MIT. If you're on an npm version I haven't verified, run NVMPIN_INTEGRATION=1 npm test in the repo and tell me what the diagnostic line says — that's free contract verification for everyone.
GitHub: github.com/alexkolovsky/nvmpin · npm: npmjs.com/package/nvmpin
SOCIAL SHARE CARD GENERATOR