---
title: REQUIRE_NODE_VERSION_FILE
product: vercel
url: /docs/conformance/rules/REQUIRE_NODE_VERSION_FILE
canonical_url: "https://vercel.com/docs/conformance/rules/REQUIRE_NODE_VERSION_FILE"
last_updated: 2025-03-04
type: conceptual
prerequisites:
  []
related:
  - /docs/conformance/customize
summary: Requires that workspaces have a valid Node.js version file (`.node-version` or `.nvmrc`) file defined.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
search_with_vercel_cli: npx vercel@latest docs search "<query>"
---

# REQUIRE_NODE_VERSION_FILE

> Conformance is available on Enterprise plans

> **💡 Note:** This rule is available from version 1.2.0.

Using a Node.js version file (`.node-version` or `.nvmrc`) ensures that all
developers and tooling (e.g., CI systems) use the same version of Node.js. This
practice helps to avoid inconsistencies between environments and can even
prevent bugs from being shipped to production.

As another benefit, committing a Node.js version file improves developer
experience, as many Node.js version management tools can automatically detect
and use the version defined in the file. This includes [GitHub Actions](https://docs.github.com/en/actions),
and popular Node.js version managers such as [`fnm`](https://github.com/Schniz/fnm)
and [`nvm`](https://github.com/nvm-sh/nvm).

This rule also validates to ensure that the version in the file is defined
in a way that is compatible with common tooling.

By default, this rule is disabled. To enable it, refer to
[customizing Conformance](/docs/conformance/customize).

## How to fix

If you hit this issue, you can resolve it by adding a Node.js version file at
the root of your workspace.

The example `.node-version` file below requires that Node.js `20.9` is used in
the workspace, allowing for any patch version (i.e. `20.9.1`). The level of
strictness can be adjusted based on your teams needs.

```text filename=".node-version"
v20.9
```

## Search the docs from your terminal

Search the Vercel docs and read pages as Markdown with the Vercel CLI. No login required.

```bash
# Find docs pages by keyword
npx vercel@latest docs search "environment variables"
npx vercel@latest docs search "function timeout"

# Print a docs page as Markdown, by path or URL
npx vercel@latest docs inspect <page>
```

---

[View full sitemap](/docs/sitemap)


If you encounter incorrect information, can’t find what you need, need a capability Vercel doesn’t currently offer, or have any other feedback to report, please do it by following the instructions at https://vercel.com/feedback.md.
