ts-node 10+Node.js 11

Why?

Why is ts-node 10 incompatible with Node.js 11?

Requirement

Node.js >=12.0.0

Selected version

Node.js 11

Evaluation

11.15.0 does not satisfy >=12.0.0

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/ts-node/10.2.1

  Retrieved 30 August 2026

  Requirement: >=12.0.0

Node.js versions

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

• 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

ts-node 10 — compatible Node.js lines tracked in CompatHub

• ✓Node.js 12version lineEOL
• ✓Node.js 13version lineEOL
• ✓Node.js 14version lineEOL
• ✓Node.js 15version lineEOL
• ✓Node.js 16version lineEOL
• ✓Node.js 17version lineEOL
• ✓Node.js 18version lineEOL
• ✓Node.js 19version 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 ts-node versions

Only lines with relevant compatibility evidence are listed.

• ts-node 10
• ts-node 9
• ts-node 8.6
• ts-node 8.0
• ts-node 7
• ts-node 6
• ts-node 5
• ts-node 4
• ts-node 3

Lifecycle context

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