News for hackers. Stuff that matters.

A comment on Complete Rewrite of ESLint. Parent comment

Re:Complete Rewrite of ESLint by hajile on Monday November 28, 2022 @08:47AM (#33773577)
JSdoc comments are 100% JS while TS types are not. This means you will be able to run ESLint without a TS compiler while still having types for people who want them. It's also more future-proof for if/when JS adopts a type system that may or may not be compatible with TS.

This sounds like everyone wins except the people who are overly-dogmatic about TS.

[ Parent | on HN ]
Re:Complete Rewrite of ESLint by EduardoBautista on Monday November 28, 2022 @09:16AM (#33773862)
If ESLint were rewritten in TS, you would still be able to run it without the TS compiler, since it would already be compiled into regular JS when published to NPM.
[ Parent | on HN ]
Re:Complete Rewrite of ESLint by hajile on Monday November 28, 2022 @09:33AM (#33774029)
Why should you be forced to deliver via NPM?

What about Deno or people using it in web-only contexts?

If they use ES-compliant modules, a build step isn't even required.

Once again, it's not that they don't have types, but the TS fanboys are now complaining that it's "not the right types".

[ Parent | on HN ]
Re:Complete Rewrite of ESLint by arrakeen on Monday November 28, 2022 @01:58PM (#33777927)
> What about Deno or people using it in web-only contexts?

i was under the assumption that deno natively supported typescript, no?

[ Parent | on HN ]