3 ms·
For previous attempts at a faster tsc, but in rust, see: 1. https://github.com/dudykr/stc https://github.com/dudykr/stc - Abandoned (https://github.com/swc-pro
by kevlened 2y ago
For previous attempts at a faster tsc, but in rust, see:
1. https://github.com/dudykr/stc https://github.com/dudykr/stc - Abandoned (https://github.com/swc-project/swc/issues/571#issuecomment-1915966297 https://github.com/swc-project/swc/issues/571#issuecomment-1...)
2. https://github.com/kaleidawave/ezno https://github.com/kaleidawave/ezno - In active development. Does not have the goal of 1:1 parity to tsc.
- smarx007 2y agoI think Deno and Bun are the two successful attempts at a faster tsc :)
- keturakis 2y agoBoth Deno and Bun still use current tsc for type checking
- madjam002 2y agoThey just strip types and don’t do any type checking
- Cthulhu_ 2y agoThose are runtimes primarily, not compilers/type checkers. Likewise, TSC is not a TS runtime.
- smarx007 2y agoWell, of course. But TSC output (transpiled JS source code) is then run by a JS runtime like Node that has a VM like V8 that makes an internal representation for the JS code. Using Bun or Deno allows you to go to a VM IR from the TypeScript directly without a need for TSC transpilation into JS first. But as @keturakis pointed out (thanks!), Deno/Bun still rely on TSC, which I was not aware of.
- morcus 2y agoBun doesn't even support a way to check types, just remove them. > Note — Similar to other build tools, Bun does not typecheck the files. Use tsc (the official TypeScript CLI) if you're looking to catch static type errors.