Featured starting point
nvm explained: a Node version manager that lives in your shell
Understand per-user installations, per-shell runtime selection and why nvm-sh/nvm is not interchangeable with every Windows tool named nvm.
Browse all 9 articles in this open-source series. Nine source-backed lessons on Node version management, shell initialization, PATH ordering and safe team workflows, with 16 isolated helper cases.
Featured starting point
Understand per-user installations, per-shell runtime selection and why nvm-sh/nvm is not interchangeable with every Windows tool named nvm.
Suggested learning path
01 → 09
Understand per-user installations, per-shell runtime selection and why nvm-sh/nvm is not interchangeable with every Windows tool named nvm.
Build a predictable first workflow using an explicit runtime and verify the difference between a project version request and the active Node binary.
Plan manager pinning, profile ownership and noninteractive initialization without mistaking an interactive terminal for a reproducible CI environment.
Trace the distinction between stored Node versions, selectors, PATH changes and the process created by an explicit nvm exec command.
Reproduce the pinned PATH replacement rules and .nvmrc validation boundaries with 16 isolated cases instead of guessing from command names.
Measure shell initialization and runtime installation separately, account for caches and binary availability, and avoid unsupported speedup claims.
Review executable downloads, profile writes and checksum limitations without equating user-level installation with isolation or complete supply-chain verification.
Compare per-shell version management, fixed runtimes and separate platform tools through concrete requirements rather than invented rankings.
Design a proposed read-only PATH and .nvmrc explorer that separates syntax, resolution and execution and avoids unsafe automatic installation.