Consistently recommend priority order of .node-version or .nvmrc
Author: fulldecentCreated Aug 24, 2026Updated Aug 24, 2026
Issue
The fnm project should recommend either .node-version or .nvmrc as a first choice for configuring the Node.js version.
Currently documentation is inconsistent by recommending one or the other as first choice.
Evidence
- The page https://www.fnmnode.com/guide/nvmrc.html mentions .nvmrc before .node-version.
- The page https://www.fnmnode.com/ mentions .node-version before .nvmrc
- In the sidebar of the documentation, the heading name is "Version Files (.nvmrc)". There is no heading named ".node-version" and no documentation URL ".../node-version.html" ordered before that.
Recommendation
- Decide which is the preferred file (perhaps .node-version).
- Ensure that the software does not treat the preferred file any worse than other files.
- Alternative: if we want to have a URL and heading specifically for the .nvmrc file and not for the .node-version file, then in the .nvmrc file specifically say at top "The fnm project recommends to use the .node-version configuration file instead of .nvmrc if there is a choice. This increases portability and is supported by multiple related projects, including nvm."
- Update all documentation to mention the /node-version.html URL before the /nvmrc.html.
Source: Schniz/fnm