A pattern that's hard to ignore anymore
There's a pattern that's played out repeatedly in the JavaScript ecosystem over the last few years: someone rewrites a core tool in a compiled language, and the performance gain is embarrassing enough to make the old version look broken. esbuild replaced webpack and made builds 10-100x faster. Biome replaced Prettier and ESLint with formatting that runs 25x faster. Now it's happening to the bundler layer itself.
Rolldown, the Rust-based bundler built by Evan You's VoidZero team, hit its 1.0 release candidate this month. It's designed to replace both halves of Vite's bundling story — esbuild for dev-mode transforms and Rollup for production bundling — with a single Rust binary underneath.
Why one bundler instead of two
Vite has always had a slightly awkward architecture: fast dev-mode builds via esbuild, but a switch to Rollup for production because esbuild's output wasn't considered mature enough for shipping. That meant your dev and prod builds were, technically, running through two different bundlers with two different sets of edge cases. Rolldown collapses that into one engine, which means what you test in development is architecturally closer to what actually ships.
Underneath Rolldown sits Oxc — the Oxidation Compiler — a Rust-based parser and transformer that's already benchmarking at over 30x Prettier's speed for formatting tasks. Oxc isn't just powering Rolldown; it's becoming the shared foundation for a growing stack of Rust-native JS tooling, the same way V8 quietly underpins half the JavaScript runtimes you've used.
What actually changes for you
If you're on Vite, this mostly happens to you rather than requiring action. The Rollup plugin API compatibility layer in Rolldown is solid enough that most existing Vite plugins — including framework-specific ones like @vitejs/plugin-react — work without modification. You don't rewrite your config; you get a faster build underneath it.
The bigger shift is conceptual. For a decade, "fast" JavaScript tooling meant JavaScript tools that were clever about caching and incremental work. Now "fast" increasingly means "not JavaScript at all." Formatters, linters, parsers, and bundlers are migrating to Rust one at a time, and the tools built on JavaScript are starting to look like the exception rather than the rule.
The practical takeaway
You don't need to migrate anything today. But if you're evaluating new tooling in 2026 — a linter, a formatter, a bundler — it's worth checking whether a Rust-based option already exists before reaching for the JavaScript-based default out of habit. The performance difference isn't marginal anymore, and increasingly, it isn't even close.