Cloudflare and VoidZero announced on October 20 that they are working with Owner.com's Max Schwenk on tsrs, an experimental Rust port of the TypeScript compiler. The project is being incubated in the Oxc toolchain in collaboration with the TypeScript team. Cloudflare's announcement gives developers another compiler to try for faster type checking, while acknowledging differences from upstream TypeScript.
Cloudflare's reported speed and memory savings depend on the TypeScript version and worker settings used for comparison. MrKeyoor read the announcement and project documentation. We have not run tsrs or reproduced its benchmarks.
The speed claim has a specific baseline
Cloudflare reports up to eight times faster type checking and about 70% less memory use than TypeScript 7.0 with the same number of type-checking workers. The same announcement says TypeScript 7.1 beta is itself up to 2.5 times faster than 7.0, with some optimizations contributed from tsrs. The eightfold figure therefore doesn't describe a comparison against every available TypeScript build.
Default settings introduce another variable. According to Cloudflare, tsrs adapts to the machine and can run faster while using more memory. The benchmark guide explains that checker-thread settings control type checking, while parsing and binding can still use every core. Equal checker counts are useful context, but they don't mean the entire compiler runs on that many threads.
There is also a scope limit: the documented benchmark invocation disables code emission and incremental compilation. It measures a fresh type check rather than a complete application build. The guide now describes comparisons against a TypeScript 7.1 nightly, too. Keep those results separate from the announcement's 7.0 comparison when estimating what your own project might gain.
Compatibility includes the errors you get
The README describes tsrs as a replacement for the TypeScript 7 compiler and language server. It currently targets TypeScript's main branch and sets full conformance with TypeScript 7.1 as the goal for a stable release. That's a target, rather than a claim that every workflow already behaves identically.
Two concrete gaps are documented: tsrs doesn't support --init or --showConfig. There are also known differences involving diagnostic order. Cloudflare acknowledges the ordering issue in its announcement, while the README explains that parallel parsing, resolution and checking can affect diagnostic output. Scripts that generate configuration or compare compiler output need their own checks before switching.
Matching error totals would be an incomplete check. The project's benchmark methodology compares error locations and codes, and explicitly flags cases with the same count but different locations. It also distinguishes differences caused by the TypeScript revision being tested. A useful trial should compare the actual diagnostics against the corresponding upstream version before treating a shorter runtime as a win.
A trial before a switch
For a project with slow type checks, the evidence supports trying tsrs alongside the existing compiler. Pin both compiler versions, keep the project configuration fixed, and record diagnostics before comparing elapsed time and peak memory. The published methodology identifies the variables that this approach holds steady.
Cloudflare says it is working with Theo Browne to merge tsc-rs and tsrs, and plans to track upstream TypeScript changes through automated checks. The next useful milestone is a stable release with documented conformance against its named TypeScript version. Watch whether the known gaps close and whether the speed advantage holds against the upstream version your project would actually use.