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.