Angular CLI and Node.js: Which Runtime Does a Pinned Toolchain Actually Support?

Where the lockfile ends

A reproducible Angular workspace is usually pinned in two places: package.json plus a lockfile, so npm ci restores the exact CLI, compiler, and build plugins on any machine, and the project-local ng binary rather than a global install whose version can drift. The one input the lockfile never captures is the Node.js runtime itself.

The boundary that stays open

Each Angular major documents a supported range of Node.js versions; running outside it can surface warnings at install time or failures at build time. Those ranges are release-specific and change between majors, so they must be read from the compatibility table for the pinned major rather than assumed. Even within a supported range, build output depends on the local toolchain, so byte-identical artifacts are not guaranteed across differing Node versions.

The undecided mechanism

Teams commonly align the runtime through a version-manager file such as .nvmrc or a pinned container base image; neither is documented as authoritative over the other.

For a workspace pinned to one Angular major:

• Which exact Node.js versions does that release officially support, and does minor drift within an LTS line matter?
• Does a version-manager file or a pinned container image give stronger guarantees that developers and CI resolve the same runtime?
• Should identical build output be expected across two supported Node versions, or only a successful build?