Re:Future of TypeScript on ESLint
by mirekrusin on Friday January 18, 2019 @03:17PM
(#18942624)
I still feel better with thin/no tooling for transpiling, flow types in comments. There’s something nice about no or ultra flat dependencies and instant npm i that keeps me there.
[ Parent
| on HN ]
Typescript also supports type checking pure JS files, as well as type annotations via JSDoc comments, if you don't want to transpile.
I like how TS also enables future JS features by transpilation. async / await was great to have quite early on.
If you use VSCode just put `// @ts-check` at the top of your files. I find a bunch of bugs with just that.
100%! Whatever happened to progressive enhancement?
Re:Future of TypeScript on ESLint
by munchbunny on Friday January 18, 2019 @04:42PM
(#18943381)
It's a design trade-off. TypeScript is close enough to JavaScript but adding the compiler step actually enables worthwhile changes to improve code safety. And Typescript can import JavaScript modules anyway, so really you just lose the ability to write both in the same file.