Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
The .nvmrc file is the smallest config file in any developer's repo: one line, containing one Node.js version number. Drop `20.11.0` (or `lts/iron`, or just `20`) into a file named .nvmrc at your project root, and any team member using nvm gets the right version with `nvm use`. Configure your shell to auto-switch when you `cd` into the directory and version mismatches across a team disappear entirely.
The syntax accepts whatever nvm understands as a version reference: a full version (`20.11.0`), a major version (`20`), an LTS codename (`lts/iron` for Node 20, `lts/hydrogen` for Node 18), or `node` for the latest. Most projects pin a major version to balance stability with the ability to pick up patch releases. Pinning a full version locks down the build environment exactly — useful for CI reproducibility.
Beyond nvm itself, .nvmrc is a de facto standard read by fnm, n, asdf (with the nodejs plugin), and Volta. CI providers like GitHub Actions support it directly via `actions/setup-node`'s `node-version-file: .nvmrc` input. The file is small enough that adding it to a project takes 10 seconds and saves the team hours of "works on my machine" debugging when someone is silently running Node 18 against code that expects Node 20.