Node Version Manager Helper
Generate .nvmrc files to pin Node.js versions for your project — supports nvm, fnm, asdf, and Volta
About this ToolHow it works, benefits & use casesTap to collapse
Pinning the Node.js version for a project is a one-line file, and this helper generates it for you. Type a version — a bare major like 20, a minor like 20.10, or a full semver like 20.10.0 — and it validates the format and produces the exact contents of a .nvmrc file you save in your project root. Quick-select buttons offer the maintained LTS lines (Iron, Hydrogen, Gallium) with the currently recommended release marked, and selecting an LTS surfaces a details card with its codename, release date, and end-of-life date so you can avoid pinning to a version that is already out of support. The generated .nvmrc is read by nvm, fnm, asdf, Volta, and the GitHub Actions setup-node action via node-version-file, all of which the usage guide spells out. It runs entirely in the browser with no install.
How to Use
- 1Type a Node.js version in the Version field — major (20), minor (20.10), or full semver (20.10.0).
- 2Or click an LTS quick-select button; the ★ marks the currently recommended LTS release.
- 3Check the inline validation — an invalid format is flagged with the accepted patterns.
- 4Review the version details card (codename, release date, end-of-life) when an LTS is selected.
- 5Copy or download the generated .nvmrc and save it in your project root.
Key Benefits
- Generates a valid .nvmrc from a major, minor, or full semver version
- Live format validation that explains the accepted version patterns
- One-click LTS quick-select with the recommended release highlighted
- Version details card shows codename, release date, and end-of-life
- Output works with nvm, fnm, asdf, Volta, and GitHub Actions setup-node
- Usage guide lists the exact command for each version manager
- Runs entirely in the browser — copy, download, or pipe the file
Common Use Cases
- Pinning a consistent Node version across a team so everyone runs the same runtime
- Adding a .nvmrc so GitHub Actions can read node-version-file in setup-node
- Checking whether a Node major you plan to pin is still within its support window
- Standardising the Node version between local dev, CI, and production images
- Quickly grabbing the current recommended LTS version for a new project
Node.js version
Major (20), minor (20.10), or full semver (20.10.0)
LTS versions
★ = Currently recommended LTS
Version details
- Version
- Node.js 20
- Codename
- Iron
- Released
- 2023-10-24
- End of life
- 2026-04-30
Updates live — save as .nvmrc in your project root
20
Using .nvmrc
- nvm:
nvm install && nvm use - fnm:
fnm use - asdf:
asdf install nodejs && asdf local nodejs $(cat .nvmrc) - GitHub Actions:
node-version-file: '.nvmrc'in the setup-node step
Was this tool helpful?
Share Your Experience
Help others discover this tool!
Related tools
- Package.json GeneratorBuild a complete package.json with framework presets, scripts, deps, exports map, engines, and live validation
- Badge GeneratorBuild shields.io README badges with live preview, assemble a badge row, and export Markdown, HTML, reStructuredText or AsciiDoc
- npm to Yarn ConverterConvert npm commands and package-lock.json to Yarn equivalents
- Package.json Scripts GeneratorGenerate common npm scripts for different project types and workflows
- Bundle Size CalculatorEstimate package sizes and analyze bundle impact on your application
- License CheckerVerify package licenses and ensure compliance with your project license
You can enter a bare major version like 20, a major.minor like 20.10, or a full semver like 20.10.0. A leading v is stripped automatically. Anything that does not match these patterns is rejected with an inline error showing the accepted formats.
The .nvmrc file is a plain version string read by nvm (nvm install && nvm use), fnm (fnm use), asdf, and Volta, as well as GitHub Actions when you set node-version-file: '.nvmrc' in the setup-node step. The usage guide on the page lists the exact command for each.