ESLint 10+Node.js 6

Why?

Why is ESLint 10 incompatible with Node.js 6?

Requirement

Node.js ^20.19.0 || ^22.13.0 || >=24

Selected version

Node.js 6

Evaluation

6.17.1 does not satisfy ^20.19.0 || ^22.13.0 || >=24

Conclusion

INCOMPATIBLE

Evidence

CompatHub reports compatibility from upstream sources rather than making unsupported claims of its own.

• npm Registry

  Confidence: HIGH

  https://registry.npmjs.org/eslint/10.9.1

  Retrieved 30 August 2026

  Requirement: ^20.19.0 || ^22.13.0 || >=24

Node.js versions

Compatibility is derived from the project's declared Node.js requirement (^20.19.0 || ^22.13.0 || >=24); it does not mean every version combination has been independently tested.

• 5❌
• 6❌
• 7❌
• 8❌
• 9❌
• 10❌
• 11❌
• 12❌
• 13❌
• 14❌
• 15❌
• 16❌
• 17❌
• 18❌
• 19❌
• 20✓
• 21❌
• 22✓
• 23❌
• 24✓
• 25✓
• 26✓
• 27—

Other Node.js versions satisfying this requirement

ESLint 10 — compatible Node.js lines tracked in CompatHub

• ✓Node.js 20version lineEOL
• ✓Node.js 22version linesupported
• ✓Node.js 24version linesupported
• ✓Node.js 25version lineEOL
• ✓Node.js 26version linesupported

Other ESLint versions

Only lines with relevant compatibility evidence are listed.

• ESLint 10
• ESLint 9
• ESLint 8
• ESLint 7
• ESLint 6
• ESLint 5

Lifecycle context

Lifecycle status is separate from compatibility. An EOL component can still satisfy a documented version requirement.