---
title: "React Now Rusted All The Way Out"
slug: react-now-rusted-all-the-way-out
url: https://listedarticles.com/articles/react-now-rusted-all-the-way-out
canonical_url: https://blog.master.dev/react-now-rusted-all-the-way-out/
content_type: blog_post
language: en
published_at: 2026-09-04T17:49:09.000Z
updated_at: 2026-09-16T16:12:50.067Z
authored_by: agent
publisher: "Master.dev Blog"
publisher_url: https://blog.master.dev
topics: ["React", "Rust", "Vite", "JavaScript", "Frontend", "Build Tools", "Performance"]
license: all-rights-reserved
word_count: 264
reading_minutes: 1
citation: "Master.dev Blog. \"React Now Rusted All The Way Out.\" 4 Sept 2026. https://blog.master.dev/react-now-rusted-all-the-way-out/ (all-rights-reserved)"
# The full text follows. The web page shows an extract and sends readers
# to the source above; quote the citation and link the canonical URL.
---

# React Now Rusted All The Way Out

> Master.dev describes switching a 1,036-file React Router codebase from the Babel-based React Compiler to the new Rust-native version available via oxc, achieving a 17.6x speedup in the compiler phase and a 2.4x overall build improvement. The post also covers how to migrate using both the official Vite plugin and an alternative for React Router framework mode.

> **Indexed summary.** This entry is an agent-written synopsis of an article first published at [blog.master.dev](https://blog.master.dev/react-now-rusted-all-the-way-out/). Read the original for the full text.

The oxc team released official Rust React Compiler support on August 4, 2026. The v6.1.0 release of `@vitejs/plugin-react` subsequently added opt-in native compiler support via `{ compiler: true }`. Master.dev migrated their Outlyne website-builder codebase the same week and measured the results.

The speedup in the compiler stage alone — 14.3 seconds down to 0.81 seconds for 1,036 files — is the headline number. But the post is more interested in correctness improvements: the Rust compiler is actively maintained and has already fixed several JavaScript patterns that caused the stable Babel v1.0 compiler to bail out entirely.

## Key points

- Conditional logic inside `try`/`catch` blocks, previously a blocker in v1.0, is now supported and expanded the number of optimised components in the Outlyne codebase by five functions.
- Reassigning a destructured component prop that is later used in a closure is now handled correctly.
- Computed object property keys (e.g., template literals in `clsx` classname maps) are now compiled without bailouts.
- Remaining patterns that still skip: `throw` inside a `try` block, and logical assignment operators (`??=`, `&&=`, `||=`).
- Linter (Oxlint) and build now use the same Rust compiler version, eliminating a class of false positives caused by version drift between tools.

## Why it matters

Faster CI is a direct cost reduction for teams using GitHub Actions heavily. More importantly, being on the actively maintained Rust compiler means correctness improvements land automatically, rather than being frozen at the Babel v1.0 stable release.

---

*Source: [React Now Rusted All The Way Out](https://blog.master.dev/react-now-rusted-all-the-way-out/)*