What changed
On 20 October 2026 Cloudflare, VoidZero and collaborators announced tsrs, an experimental Rust port of the TypeScript compiler incubated within the Oxc JavaScript toolchain in coordination with TypeScript's maintainers. Cloudflare reports up to eightfold speed and about 70% lower memory use than TypeScript 7.0 in early matched-worker benchmarks. The project can be installed from npm with npm install tsrs and run using npx tsrs. The maintainers plan to merge the separate tsc-rs work, improve feature and diagnostic compatibility, and eventually add Language Server Protocol and source-map functionality.
Why it matters
Type-checking time and memory cost shape build times, CI spending and whether developers can run complete toolchains inside browser or sandboxed agent environments. A Rust implementation targets low-overhead WebAssembly execution, different from the official TypeScript team's Go-based native port. Builders should treat this as a promising experiment and benchmark it against their actual projects rather than replacing production checks on the basis of early headline numbers.
A port, not a new TypeScript language fork
The maintainers explicitly defer language design and semantics to the TypeScript team. Their challenge is keeping a second implementation behaviourally aligned as TypeScript evolves. The port is being incubated in Oxc, whose Rust tooling already covers linting and transformation workflows.
The performance figures have a defined comparison
Cloudflare reports up to 8x faster checks and approximately 70% less memory versus TypeScript 7.0 with the same number of type-check workers. It also says TypeScript 7.1 beta is already up to 2.5x faster than 7.0 in its tests. These are author-produced early benchmarks, not an independently reproduced industry-wide result; tsrs adaptive defaults may trade memory for additional speed.
WebAssembly is the architectural reason for another port
The official Go TypeScript compiler already offers major native speedups. Rust can be compiled to compact WebAssembly without bringing Go's runtime and garbage collector into the guest. That matters for browser-hosted IDEs, edge runtimes and isolated coding-agent environments, but production viability depends on feature coverage and compatibility.
Migration should be experimental until compatibility matures
The team acknowledges differences such as diagnostic ordering and plans to combine tsrs and tsc-rs, extend language-service support, and keep pace with upstream changes using automated tracking and tests. Run tsrs alongside an existing compiler in CI to compare diagnostics, memory and elapsed time; do not assume a passing experimental check matches the official compiler on all constructs.