Cloudflare and VoidZero have announced a collaborative initiative alongside Max Schwenk of Owner.com to develop tsrs, a faithful Rust port of the TypeScript compiler. Incubated as part of the broader Oxc JavaScript compiler toolchain, the project is being developed in close cooperation with the core TypeScript team. The primary goal of this effort is to reduce developer wait times during code checking, improve memory efficiency, and unlock the
potential for fully encapsulated, high-performance development environments to run directly inside web browsers and edge networks.
Rather than attempting to fracture the ecosystem, the project maintainers have emphasized that they are explicitly not forking TypeScript. The core TypeScript team will retain full control over the language’s design, syntax, and long-term strategic direction. Over the years, the TypeScript team has successfully guided the language’s widespread adoption across the modern JavaScript and web development community. The creators of tsrs intend to preserve this balance, recognizing that while the TypeScript team moves quickly on many fronts, certain architectural features require years of careful exploration, prototyping, and validation. A community port must track these decisions strictly to maintain absolute compatibility, ensuring the TypeScript team remains solely responsible for defining the language standard.
Performance and Memory Improvements
Early benchmarks of the tsrs project demonstrate significant performance and efficiency gains. When configured with the same number of type-checking workers, tsrs has been shown to execute up to eight times faster while consuming roughly 70 percent less memory compared to TypeScript 7.0.
These optimization efforts are already benefiting the broader ecosystem. The upcoming TypeScript 7.1 beta release introduces substantial performance improvements, making it up to 2.5 times faster than version 7.0. Several of these performance optimizations were directly upstreamed from the experimental tsrs codebase, with developers hoping to contribute additional enhancements in the future.
While various alternative TypeScript ports have emerged with differing performance claims—often relying on high-end machine configurations and non-standard default settings—the tsrs team collaborated directly with the TypeScript team to ensure that their published benchmarks utilize identical configurations. Out of the box, tsrs can also deploy an adaptive configuration tailored to specific machine types, trading a slightly higher memory footprint for even greater execution speed.
Developers interested in experimenting with the technology can install the experimental release directly from npm using standard package management workflows, allowing them to test the compiler within their local build pipelines.
Why Now?
Efforts to port TypeScript to alternative languages have a long history, but historically faced immense architectural complexity. For a long time, the only fully successful language port was the TypeScript team’s own transition of the compiler from JavaScript to Go.
However, the advent of frontier artificial intelligence models has fundamentally shifted what is possible in software engineering, enabling large-scale, automated code porting and analysis over the course of just a few days. This technological shift has spurred a wave of new experiments, ranging from superficial ports and faithful rewrites to entirely re-architected versions of TypeScript written in systems languages like Rust and C++. This proliferation underscores a persistent, industry-wide demand for faster development toolchains.
Why Rust?
While the official Go port already delivered dramatic speed and memory improvements over the original JavaScript implementation, the choice of Rust offers distinct technical advantages, particularly regarding WebAssembly (Wasm) integration.

A persistent challenge when compiling Go programs to WebAssembly is the necessity of bundling Go’s garbage collector alongside the binary. Rust, by contrast, relies on a deterministic memory management model that facilitates straightforward, lightweight memory interactions between a WebAssembly guest and host. This efficiency makes Rust exceptionally well-suited for running complex developer tooling inside WebAssembly environments.
Cloudflare Workers have supported WebAssembly for an extended period, and the platform recently introduced native Rust support via a new Emscripten target for wasm-bindgen. When complex software build and deployment systems execute in tight loops on edge infrastructure, minimizing the memory footprint yields immediate operational benefits. This efficiency makes it feasible to run fully encapsulated development toolchains in environments where they could previously never operate.
Combined with modern agentic workflows, these capabilities allow development toolchains to run end-to-end within fully sandboxed server-side environments. Simultaneously, WebAssembly enables developers to execute these same environments safely on the client side inside a browser, on embedded hardware, or within constrained Internet of Things (IoT) applications.
How Will the tsrs Port Be Maintained?
To consolidate community efforts, the project is joining forces with Theo Browne to merge tsc-rs and tsrs into a unified package. This consolidated project will support the full feature set of TypeScript, including the Language Server Protocol (LSP) and content mappers.
Maintenance strategies draw inspiration from successful synchronization models used in projects like Vinext, which keeps Next.js running seamlessly on Vite. Automated agents regularly review upstream changes, analyze code diffs, and generate tracking issues for any modifications that could impact compatibility. Nightly test suites run continuously against upstream test matrices, allowing automated systems to identify discrepancies, construct code reproductions, port relevant tests, and propose fixes across both codebases simultaneously.
The tsrs team intends to apply this exact methodology to TypeScript, exercising extreme caution to prevent behavioral divergence from the upstream compiler. Whenever performance bottlenecks or improvements are identified, maintainers will attempt to contribute those optimizations back to the upstream Go codebase so the entire community benefits. While minor differences currently exist—such as the exact sequencing of diagnostic error messages—the project aims to minimize these divergences entirely prior to reaching a stable release.
What’s Next?
Cloudflare already serves as a major hub for open-source Rust tools driving the modern JavaScript ecosystem, including Vite, Rolldown, Oxlint, and Oxfmt. With over ten million developers building applications on Cloudflare infrastructure, optimizing foundational developer toolchains for speed, portability, and execution flexibility remains a core priority.
The engineering teams are eager to explore deeper integrations of tsrs across their existing technology stack, such as implementing type-aware lint rules within Oxlint. The overarching objective is to maintain tsrs as a healthy, well-supported open-source project that complements rather than competes with the official TypeScript ecosystem.
With the TypeScript team simultaneously exploring its own internal memory and performance enhancements for the compiler, this collaborative environment promises to accelerate the evolution of fast, reliable tooling for developers worldwide.