Orbit · Explore

Web Dev · by Iryna Melnyk · 2026-10-20

Cloudflare ported the TypeScript compiler to Rust and called it tsrs

blog.cloudflare.com

Cloudflare has a writeup on tsrs, their port of the TypeScript compiler to Rust. Native ports of the TS toolchain keep showing up and it's starting to feel like the JS-hosted compiler's days are numbered for big codebases. The thing I'd want to know is how close it tracks upstream semantics, since a fast type checker that disagrees with tsc on edge cases is a nightmare in CI. Would you actually switch your build to something like this, or wait for the ecosystem to settle?

88 sparks · 21 comments

Comments

Pixel Orbit · 14 likes

rewrite it in rust has finally come for the type checker lol

Rohan Mehta · 9 likes

it was always going to. the compiler was the last boss

Haruto Sato · 6 likes

next up: rewriting rust in rust (oh wait)

Midnight Rider · 13 likes

our monorepo typecheck is the slowest step in CI by a mile so I'm interested in anything here

Jasmine Cruz · 8 likes

same. we split into project references just to make it bearable and it still crawls

Sleepy Mango · 10 likes

hoping this means faster language server in the editor eventually, that's where I actually feel the pain every day

Lotte Jansen · 11 likes

the LSP side is the real prize. CI waiting is annoying, editor lag is miserable

Ethan Brooks · 7 likes

does this do emit too or just checking? if it's only checking, most of us already strip types with swc or esbuild anyway

Tanvir Rahman · 6 likes

if it does checking only that's still the expensive part imo

Rohan Mehta · 5 likes

worth reading the post for that, I couldn't tell from the title either

Diego García · 6 likes

Honestly fine with tsc being slow on my small projects. this matters for like the top 5% of codebases

Midnight Mango · 1 likes

fair, but editor responsiveness on mid size projects also matters more than people admit

Priya Nair · 0 likes

the top 5% of codebases is where most of the paid dev hours are though

Pixel Comet · 2 likes

Interesting that they went Rust when the official native effort went with Go. Curious if the blog explains why they didn't just wait for that

Omar Hassan · 0 likes

my guess is they needed something embeddable in their own Rust tooling, but that's just a guess

Paper Marauder · 0 likes

two native compilers is fine honestly, competition keeps both honest

Theo Bennett · 0 likes

the real question is who keeps it in sync when TS ships a new release every few months

Emma Tremblay · 8 likes

presumably cloudflare has enough internal TS that they're motivated to keep up

Aoi Ito · 7 likes

that's always the catch with ports. day one is easy, year three is the hard part

Aarav Sharma · 0 likes

I'd be careful about trusting the error output until people throw real world weird generics at it. conditional types are where every alternative implementation falls over

Maya Williams · 14 likes

yeah the happy path benchmarks never tell you about the 3% of files that type differently