I wrote this one (my own blog). I tested node app.ts with no tsx or build step on Node 22.20, 24.22 and 26.13. Interfaces, generics, as casts and import type just work. Enums, namespaces, parameter properties, decorators, .tsx files and extensionless imports all fail, with the exact errors in the post, plus a tsconfig (erasableSyntaxOnly, verbatimModuleSyntax) that catches them before runtime. Note that --experimental-transform-types is gone in Node 26.

Happy to hear if anyone is running this in production and hit other edges.

modern-web-types is a drop-in replacement for TypeScript’s official “DOM” and “WebWorker” libraries, built on TypeScript’s own generator but with a single-engine support threshold.

Anders Hejlsberg is the creator of TypeScript and C#, and I asked him about how the TypeScript compiler got 10x faster through a rewrite in Go and his thoughts on how AI has impacted software engineering.

I’m testing a tiny idea: “README policy as code.”

Not markdown style linting, but more of a maintainer checks:

• required sections
• example presence
• link checks

Would this be useful in your projects?

If yes, what’s the one rule you’d want first?