Following the oxc team’s release of official support for the Rust React Compiler on August 4, 2026, we switched our 1,036-file React Router codebase (Outlyne, a website builder) over to it and saw a ~17.6× speedup on the compiler portion of our build. The v6.1.0 release of @vitejs/plugin-react brought “experimental native React Compiler support”, which you can opt in to by passing { compiler: true } to the plugin in your Vite config. And for those unable to use the Vite React plugin (e.g. if, like us, you’re using React Router in framework mode), @acusti/vite-plugin-react-compiler is a minimal Vite plugin to React-compile your codebase regardless of the rest of your build pipeline.

Faster Builds = Happier Devs + Cheaper CI. The headline feature is the speedup. Per Boshen, the oxc project lead: It is more than 10 times faster than Babel in our preliminary benchmark. We saw more than a 17× speedup, with 1,036 files going from 14.3s when built with Babel to 0.81s natively (single-threaded). This is huge for us because, with agent-assisted software development, CI usage and GitHub Actions minutes have become a real cost center. Note that those speedups apply only to the compiler part; overall build time improved around 2.4× (22.1s → 9.3s).

Despite speed being the headliner, I’m more excited about the benefits of being on the latest React Compiler, which has fixed substantial limitations in JavaScript support, including conditional logic in try/catch blocks, reassigning destructured props used in nested closures, and computed object property keys. These fixes expand compiler compatibility by seven additional functions. Still, limitations remain: throwing from inside a try block and logical assignment operators (??=, &&=, ||=) cause skips, but the Rust compiler will get those fixes when they land.

Finally, my full toolchain now uses the same React Compiler version with equivalent feature support, avoiding coverage gaps after adopting Oxlint’s React Compiler support.