TLDR; I'm making a Typescript type-checker in Rust. Right now it supports a smaller subset of the type-system and exists as a fun side-project, but the end goal is a compilation tool we can use to make Typescript compilation go brrrr...
In the past I’ve written about Typescript’s biggest underlying problem: it’s slow compilation speeds. Amazing projects like esbuild, SWC, and bun solve the first half of the problem, emitting JS from TS, but they skip the critical type-checking phase completely due to complexity.
In that post I briefly mentioned that most of the major players (also including Deno, Rome, etc.) in the JS compilation ecosystem don’t have any plans to type-check TS code. SWC is the only project actively solving this problem, but it’s unclear if it will be open-source or commercially licensed.
This basically means that the majority of us will be at the mercy of
tsc’s abysmally slow speed, and that prompted me to consider building an open-source type-checker of my own. It certainly would be a fun and challenging undertaking, and would provide utility to a vast number of people.
And thus, I started working on a TS type-checker arbitrarily named
tyty about a week ago in my spare time. It currently supports a small subset of Typescript, I plan to open-source it soon.
The obvious starting point was to build upon an existing JS/TS parser/bundler by type-checking its output AST. The difficult problem of parsing JS/TS has been solved many times over now, why reinvent the wheel? Of the existing projects out there, SWC is the only one which makes its AST nodes accessible to its public facing API, so it became the clear choice.
ChallengesλTypescript’s type-system is simple in some ways and complex in others. In the traditional type systems view, it is quite simple. Typescript uses bidirectional type-checking which has a very simple local type inference algorithm. There are type systems with more sophicasted inference, for example the Hindley-Milner type system. As a result, the majority of type-checking in Typescript is more straightforward than you’d think.
The remaining difficulty comes from some of Typescript’s unique features. One of the coolest features is its conditional and recursive types. When paired with generic parameters, they allow you to add complex logic to your type definitions, effectively giving you a simple functional programming language (that operates on types instead of data), all embedded within Typescript’s type-system. For example, see this JSON parser created entirely from Typescript types.
The consequence of this is the problem of type checking complex types becomes more of a problem of building an interpreter for this meta-language embedded within the type-system. Having created a programming language before, I am really excited to tackle this aspect of Typescript as it’s more familiar ground for me.
GoalsλThe end goal is to reach feature parity with Typescript and provide a way to compile TS code either through SWC’s upcoming plugin system or a wrapper around it.
I also want to leverage the speed of a Rust-based type-checker to create a very fast LSP server implementation that works well in all editors (not just VSCode!).
Additionally, I want to
tyty to have better and more descriptive error messages than
tsc‘s. Isn’t this nice?:
This is made using the amazing ariadne Rust crate.
Ideally I would also like to expose some of the type-checking functionality in a library, because Typescript’s compiler API is quite horrendous. This would give developers more robust tooling to manipulate Typescript types. When I was working on tsgql I had such a terrible time working with the TS compiler API.
This is more of a moonshot idea, but it would be amazing if
tyty could interoperate with other JS/TS compilers. It could be compiled into a dynamic library and called through FFI.