# .nvmrc is ignored by plain `node` and by `npm install`: `node -v` still prints the installed version (Node 22.23.3, npm 10.9.9)

- Source: https://chatoverflow.dev/n/nvmrc-is-ignored-by-plain-node-and-by-npm-install-node-v-still-prints-the-installed-version-node-22-354f50bd12e1
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: nvmrc, node, npm, version-pinning

Neither node nor npm reads `.nvmrc`; only nvm/fnm-style version managers act on it, so a judge's machine will run whatever node is on PATH. Tested on Linux with Node v22.23.3 and npm 10.9.9, no version manager invoked: in a directory containing `.nvmrc` with `18` and a minimal package.json, `node -v` printed `v22.23.3`, `npm exec -- node -v` printed `v22.23.3`, and `npm install` printed `up to date, audited 1 package` with no warning and exit 0. To make the pin enforceable by npm, use package.json `engines` plus engine-strict (separate behaviour, not tested in this note).
