Compatibility result
ESLint 9+Node.js 20
Why?
Why is ESLint 9 compatible with Node.js 20?
- Requirement
- Node.js ^18.18.0 || ^20.9.0 || >=21.1.0
- Selected version
- Node.js 20
- Evaluation
- 20.20.2 satisfies ^18.18.0 || ^20.9.0 || >=21.1.0
- Conclusion
- COMPATIBLE
Evidence
CompatHub reports compatibility from upstream sources rather than making unsupported claims of its own.
npm Registry
Confidence: HIGHhttps://registry.npmjs.org/eslint/9.39.5
Retrieved 30 August 2026
Requirement: ^18.18.0 || ^20.9.0 || >=21.1.0
Node.js versions
Compatibility is derived from the project's declared Node.js requirement (^18.18.0 || ^20.9.0 || >=21.1.0); it does not mean every version combination has been independently tested.
Other Node.js versions satisfying this requirement
ESLint 9 — compatible Node.js lines tracked in CompatHub
- ✓Node.js 18version lineEOL
- ✓Node.js 20version lineEOL
- ✓Node.js 21version lineEOL
- ✓Node.js 22version linesupported
- ✓Node.js 23version lineEOL
- ✓Node.js 24version linesupported
- ✓Node.js 25version lineEOL
- ✓Node.js 26version linesupported
Other ESLint versions
Only lines with relevant compatibility evidence are listed.
Lifecycle context
Lifecycle status is separate from compatibility. An EOL component can still satisfy a documented version requirement.
Compatible, but past end of life
These versions satisfy the documented compatibility requirement, but one or more components are past end of life. Node.js 20 lifecycle
- Status
- END OF LIFE
- EOL
- 30 April 2026
Supported alternatives
Node.js lines that satisfy this requirement and are still supported.
- Node.js 22supported
- Node.js 24supported
- Node.js 26supported
