Suggestion: Update Node.js version support

[Pixel998]

What problem do you want to solve?

The engines field in package.json is currently set to >= 20, but newer versions of eslint-scope, espree, and the @eslint/* packages require ^20.19.0 || ^22.13.0 || >=24.

That means our declared Node.js support range is broader than the range supported by key parts of the ESLint ecosystem we depend on. This can make upgrades confusing and can leave us advertising support for Node.js versions that are no longer actually compatible with the packages we want to use.

It also seems like a good time to revisit Node 20 support more generally, since Node 20 reaches end of life on April 30, 2026.

What do you think is the correct solution?

Update the engines.node range in package.json so it reflects the support policy we actually want.

I think there are two reasonable options:

• Match the current ESLint ecosystem minimum exactly: ^20.19.0 || ^22.13.0 || >=24
• Drop Node 20 support entirely and move to a more forward-looking range: ^22.13.0 || >=24

Participation

• I am willing to submit a pull request for this change.

AI acknowledgment

• I did not use AI to generate this issue report.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

Additional comments

No response

[amareshsm]

I’m in favor of dropping Node v20 since it’s about to reach EOL (by April 30, 2026).

That said, keeping Node 20 with a stricter range (^20.19.0) also seems reasonable. If there’s a strong reason to continue supporting v20, I’m happy to consider that.

[lumirlumir]

I also think Node.js 20 should be dropped, since it will reach end-of-life at the end of this month.

However, I have a couple of open questions: what version range should we specify, and which Node.js version should we use in Netlify CI?

---

First question: should we use a version range such as ^20.19.0 || ^22.13.0 || >=24 instead of pinning a specific version like 24?

Since eslint.org and code-explorer are apps rather than packages, we can specify a Node.js version range (for example, ^20.19.0 || ^22.13.0 || >=24), but Netlify CI will still use a specifically pinned Node.js major version during builds. (Example: #374 (comment))

So even if we specify a version range, Netlify CI will use a pinned major version, which can create a discrepancy between the Node.js version used in CI and the version contributors use locally.

I think that’s why we have .nvmrc and the nvm setup at the repository root, and why the engines version range can simply be >=20. (To be more precise, I think the Node.js version range in package.json should probably be ^20 rather than >=20.)

code-explorer/.nvmrc

Line 1 in 60aadf3

20

code-explorer/package.json

Line 31 in 60aadf3

"node": ">= 20"

---

Second question: if we configure Netlify CI to use a specific major Node.js version, should we skip Node.js 22 and go straight to Node.js 24?

When Node.js 18 reached end-of-life, the Node.js blog recommended skipping Node.js 20 and upgrading directly to Node.js 22.

https://nodejs.org/en/blog/announcements/node-18-eol-support#why-skip-v20-and-go-straight-to-v22

The reason was to avoid upgrade fatigue. Major Node.js upgrades can require testing, dependency updates, and potential code changes. By moving to v24 now, we may be able to avoid another upgrade cycle in 2027–2028.

---

To summarize, a pinning strategy for app development and moving directly to Node.js 24 seems like the more reasonable choice to me.

That said, opinions may differ, so I’d like to hear more feedback from the team. @eslint/eslint-team

[DMartens]

I agree with @lumirlumir that we should have different Node.js version ranges for our applications and other packages.
To keep it simple I also agree to just use the latest Node.js LTS version for applications.

[lumirlumir]

TSC Summary:

• Node.js 20 reached End-of-Life on April 30, 2026, but web apps such as code-explorer and eslint.org are still depending on it.

TSC Question:

• Which Node.js version would be best to update to? Should we move directly to version 24 or take it one step at a time with version 22?
• Also, what would be the recommended first step for this transition, especially since some parts of the setup might require setup changes on Netlify?

[mdjermanovic]

• Which Node.js version would be best to update to? Should we move directly to version 24 or take it one step at a time with version 22?

In the 2026-05-14 TSC meeting, we decided to upgrade all our Netlify apps (i.e., websites) to Node.js 24.

• Also, what would be the recommended first step for this transition, especially since some parts of the setup might require setup changes on Netlify?

For this particular app, I'm going to try the following:

1. Update Node.js version to 24 on Netlify. This might not have any effects as Netlify should honor .nvmrc, but just in case.
2. Update engines in package.json and package-lock.json and update .nvmrc.