By ByteBot
Rolldown 1.0 hit stable on May 7, 2026. If you’re using Vite 8, you’ve been running it for months — Rolldown shipped as Vite’s default bundler back in March and has been under every build since. The 1.0 tag means the API is locked: option names, types, and plugin hook signatures are now backward-compatible under semver. ^1.0.0 is safe to pin. This isn’t a launch — it’s a graduation.
The Problem Vite Finally Fixed
Vite’s original architecture had a split personality. During development, esbuild handled transforms. For production builds, Rollup took over. Two different bundlers, two different plugin surfaces, two different behaviors to reason about — and occasional surprises when production builds disagreed with what you’d seen in dev.
Rolldown replaces both with a single Rust engine. It’s Rollup-compatible at the API layer — your existing plugins still work — but built on the same performance foundations as esbuild. The dual-bundler era ends here.
The Numbers Are Not Exaggerated
Rolldown is 10–30x faster than Rollup, and the gap widens with project size. A 19,000-module benchmark clocks Rolldown at 1.61 seconds; Rollup takes 40.10 seconds for the same job. At large scale, Rolldown lands roughly on par with esbuild (within 10–15%), which is notable given that esbuild held “fastest bundler” status for years.
Real-world numbers from early adopters tell the story more clearly than synthetic benchmarks:
- Linear: Build time dropped from 46 seconds to 6 seconds
- Beehiiv: 64% reduction (240s → 86s)
- Ramp: 57% faster builds
- Mercedes-Benz.io: 38% reduction (180s → 112s)
- Framer: 67% chunk reduction via granular code splitting
Framer and PLAID are both running Rolldown in production — the latter being a payments company. When fintech ships on a bundler, the stability story is already written.
What “Stable” Actually Means
The 1.0 release locks Rolldown’s public API under semantic versioning. The VoidZero team is explicit: no planned breaking changes to option names, types, or plugin hook signatures. Output behavior may evolve for optimization — meaning your bundle might get smaller or faster in a patch release — but runtime behavior stays consistent.
Experimental features remain subject to change; the core bundler surface that Vite and plugins depend on is what’s locked. The RC announcement in January 2026 was already the API stability declaration — 1.0 stable makes it official.
Upgrading from Vite 7
If you’re on Vite 8, there’s nothing to do. You’re already running Rolldown. For teams still on Vite 7, the Vite 8 migration guide recommends a two-step path:
- Switch to the
rolldown-vitepackage on Vite 7 first — this isolates any Rolldown-specific issues from other Vite 8 changes - Then upgrade to Vite 8
A compatibility layer handles most existing rollupOptions and esbuild configurations automatically, so the majority of projects require no code changes. Node.js 20.19+ or 22.12+ is required — same as Vite 7. The install size is about 15 MB larger (lightningcss is now a standard dependency, plus the Rolldown binary), which is worth knowing but rarely a real constraint. The Rolldown repository has detailed compatibility notes if you run into edge cases.
What’s Coming Next
The roadmap item worth watching is Vite Full Bundle Mode. Currently, the dev server uses Rolldown for transforms but still serves modules individually. Full Bundle Mode would bundle the entire app during development — preliminary benchmarks show 3x faster startup, 40% faster full reloads, and 10x fewer network requests. That last number matters most for large apps where hundreds of unbundled imports hammer the browser on every reload.
Lazy Barrel Optimization is also being stabilized. Barrel files — index.ts files that re-export everything from a directory — are a known performance sink in large codebases. This feature compiles only what’s actually used, which can meaningfully reduce what Rolldown has to process at build time.
VoidZero owns the full toolchain: Rolldown, Vite, Vitest, and Oxc. Rolldown 1.0 stable means improvements flow through to all Vite users by default — there’s no separate adoption step. The Rust-based tooling trend has been building for years alongside Turbopack, Rspack, and Biome. Vite 8’s reception confirmed the direction. Rolldown 1.0 is the milestone that makes it permanent.
