4 ms·

> without having to figure out if a type analysis bug is from me, or the tool Deno uses regular Typescript for static type checking, it's just built-in. Bun al

by whstl 3y ago

> without having to figure out if a type analysis bug is from me, or the tool Deno uses regular Typescript for static type checking, it's just built-in. Bun also doesn't do type checking by itself, they recommend using tsc [2]. [1] https://docs.deno.com/runtime/manual/advanced/typescript/faqs#what-versions-of-typescript-does-deno-support https://docs.deno.com/runtime/manual/advanced/typescript/faq... [2] https://bun.sh/docs/runtime/typescript#running-ts-files https://bun.sh/docs/runtime/typescript#running-ts-files

pjmlp 3y ago
Until they bundle Microsoft's compiler, it isn't the same thing. It is like tracking down if a C bug in GCC relates to developer, or GCC understanding of ISO C documentation. Just this alone proves it isn't the same thing, => Deno tries to keep up to date with general releases of TypeScript, providing them in the next patch or minor release of Deno.
- whstl 3y ago
  The “Microsoft compiler” is exactly what tsc is, and is exactly what is bundled with Deno. Sorry if that wasn't clear.