The Rust version of the React Compiler is now showing up in Vite workflows, and at least one production codebase says the payoff is not just theoretical.
A new Master.dev blog post says the team behind Outlyne, a 1,036-file React Router application, moved from the Babel-based React Compiler to the Rust version after oxc released official support on August 4, 2026. In its account, compiler time fell from 14.3 seconds to 0.81 seconds in a single-threaded run, a change the post describes as more than a 17× improvement on that part of the build.
The company is careful to say that the total build does not speed up by the same factor. In the reported case, the overall build improved from 22.1 seconds to 9.3 seconds, which is still significant but much smaller than the compiler-only gain. That distinction matters because build pipelines often include much more than compilation alone.
The article also points to a broader tooling shift. It says `@vitejs/plugin-react` version 6.1.0 introduced experimental native React Compiler support, which can be enabled with `{ compiler: true }` in the Vite config. For projects that cannot use that plugin, the post highlights `@acusti/vite-plugin-react-compiler` as an alternative path for applying the compiler in a Vite-based stack.
The practical argument is not just speed. The blog says the Rust compiler covers cases the earlier Babel-based compiler struggled with, including conditional logic inside `try/catch` blocks, destructured component props that are reassigned and later used in nested closures, and computed object property keys. According to the post, those fixes expanded compatibility for the author’s app by seven more functions.
The author also says the Rust path makes the toolchain more internally consistent. After an earlier setup where linting and build-time compilation were not perfectly aligned, the team says both sides now use the same React Compiler implementation and the same feature set. That reduces the risk of a component being skipped in build output without showing up as a lint issue.
For teams already on Vite 8 or later, the post argues the migration is largely a simplification exercise. The writer says the Babel-based flow can be reduced by removing `@rolldown/plugin-babel`, while React Router framework-mode projects can shed `vite-plugin-babel`, `babel-plugin-react-compiler` and `@babel/preset-typescript` in favor of the newer setup.
The post still notes limitations. Logical assignment operators remain unsupported, and a `throw` inside a `try` block can still cause the compiler to skip a component or hook. But the direction is clear: the Rust port is turning React Compiler support into something that feels closer to a normal build feature than a fragile experiment.
For developers watching CI bills and build times, that is the real story. Faster compilation is useful on its own, but a smaller configuration surface and better feature parity between lint and build are what make the Rust compiler look ready for wider adoption.
