4 ms·
You probably already know this, but for anyone wanting to do this: esbuild does not do any type checking, so TypeScript with pure esbuild (without a separate ts
by 5e92cb50239222b 5y ago
You probably already know this, but for anyone wanting to do this: esbuild does not do any type checking, so TypeScript with pure esbuild (without a separate tsc step) is only half useful (it gives you better autocompletion, but not much else).
https://esbuild.github.io/content-types/#typescript https://esbuild.github.io/content-types/#typescript
- BiteCode_dev 5y agoYou IDE should check the types for you.
- johnnypangs 5y agoThis might worked on solo projects but if you’re working with people, I’d highly recommend enforcing type checking of some sort. People will ignore the IDE error messages.
- skinkestek 5y ago> People will ignore the IDE error messages. Then they get caught in code review at least in any team I work. No way I accept any unnecessary "disable lint" statement in a PR. Also (of course, since it is default) the CI build system breaks if they commit and push without ignores, so no, trying to slide it past me doesn't work either.
- johnnypangs 5y agoIt's not linting, it's typechecking which is slightly different. Linting won't catch type errors. All I'm recommending is to add a typecheck to the CI system so no one sneaks in a broken type (I couldn't recognize a broken type in a PR personally).
- kitd 5y agoYup. Vscode has built-in Typescript support so that does all the type checking as you go.