Rsbuild 2.1 brings Rust-based React Compiler, speeds frontend builds

Rsbuild 2.1 landed on June 26 with a clear message for frontend teams: the fastest path through a React build can now run through Rust. The release added a Rust-based React Compiler, built on Rspack 2.1, and paired it with build-system changes meant to cut latency in the places that usually drag JavaScript tooling down.

The headline claim is concrete. Rsbuild says its Rust implementation of React Compiler is 7 to 13 times faster than the Babel implementation when you measure only the extra compilation work the compiler adds. That matters because React Compiler is supposed to optimize components and hooks at build time, which makes it valuable and expensive at the same time. Moving that work into Rust shifts it from a bottleneck into part of the speed story, rather than another layer of overhead in already heavy frontend pipelines.

The compiler is available through @rsbuild/plugin-react, with extra setup required for React 17 and React 18 projects. That keeps the integration inside the existing plugin flow instead of forcing teams into a separate build path. Rsbuild 2.1 also added first-class support for TanStack Start, making it a native option for teams using that stack rather than a patched-in workaround.

The rest of the release reinforces the same direction. Rsbuild added a Tailwind CSS v4 plugin, automatic externals, parallel Babel and SVGR processing, and new resource import capabilities including CSS URL imports, worker query imports, and Wasm source imports. Those are the kinds of changes that show up in developer time: less configuration friction, less serialized work in the build, and fewer odd gaps when a project starts leaning on modern asset types.

Taken together, Rsbuild 2.1 reads less like a routine JavaScript tooling update and more like another step in Rust’s quiet expansion as the performance layer under mainstream frontend infrastructure. The interesting part is not that Rust is present in the stack. It is that Rust is now carrying visible user-facing wins in compile speed, plugin integration, and build throughput, right where frontend teams feel them first.