[wwwigham]

Contrary to what seems to be popular opinion here on HN, I think it's fine they'd entertain keeping their code as JS with JSDoc, rather than TS. It's still typesafe, which is what's important from a maintenance and documentation perspective. A linter than goes all in on TS is what tslint was (and it worked on JS), and ultimately it lost to eslint in the linter popularity wars (as has jslint, and jshint, imo). If JS source is the sauce that keeps contributions coming and the downloads flowing, then so be it. There's also some value in dogfooding their own JS lints, rather than TS ones. Sure, there's overlap, but undoubtedly some differences, too (especially any rule that lints jsdoc).

[swyx]

also note that both Deno and Sveltekit moved from TypeScript to JSDoc (https://twitter.com/swyx/status/1350427690814251010)

[e12e]

For Deno at least, there were some pretty specific reasons for the change:

https://docs.google.com/document/u/0/d/1_WvwHl7BXUPmoiSeD8G8...

[Aeolun]

I’m kind of inclined to say that eslint won because they have typescript evaluation as well. If it didn’t work on Typescript you’d see less and less people using it.