Shipped on March 12 if you missed the notification. The CHANGELOG.md is long. I've had a specific vite-plugin-svgr issue ...
Shipped on March 12 if you missed the notification. The CHANGELOG.md is long.
I've had a specific vite-plugin-svgr issue sitting in our prod build worked fine in dev, failed silently in production output for the better part of eight months. Turns out the root cause was exactly what everyone sort of knew but nobody wanted to say out loud: esbuild and Rollup are two completely different bundlers doing two completely different jobs inside the same tool, and keeping plugin behavior consistent across both of them is, charitably, hard. Vite 8 kills the split.
Rolldown is the replacement. Single Rust-based bundler, Rollup-compatible API (so most of your existing plugins don't immediately explode), and it handles both dev and production. VoidZero, the org behind Vite, Rolldown, and Oxc, has been building toward this for a while. The claim is 10-30x faster than Rollup, which I'd treat with some skepticism depending on where your project actually spends its time. If your build is slow because of TypeScript type-checking or a bloated dep graph, Rolldown alone isn't going to save you. Linear reportedly went from a 46-second build to 6 seconds, Beehiiv cut 64%, Ramp 57%. Those numbers are real. They're also for specific stacks at specific companies, which is worth keeping in mind before you expect identical results on a monorepo with 12 Webpack-era assumptions baked in.
The migration story is saner than I expected. If you want to test Rolldown without fully committing to Vite 8, there's a rolldown-vite package you can drop in as a replacement while still on Vite 7, same config, different bundler under the hood. That's the two-step they recommend for complex projects: isolate the bundler switch first, then do the version bump. Node.js 20.19+ or 22.12+ required either way.
The other stuff that quietly shipped
resolve.tsconfigPaths is built in now, which means one less plugin in my config for path alias resolution. server.forwardConsole pipes browser console output to your terminal, weirdly useful if you're running any kind of agent or automated test flow that needs client-side visibility without a browser open. Plugin React v6 drops Babel and uses Oxc for transforms, which I'm... cautiously optimistic about. I haven't hit an edge case yet but I'm genuinely unsure how Oxc handles some of the weirder decorator patterns in our codebase, and that's an open question I haven't resolved.
Also a new plugin registry at registry.vite.dev presumably because the ecosystem is going to fragment slightly during the transition period and having a curated list of Rolldown-compatible plugins matters.
The practical answer for most teams is: try rolldown-vite on a branch this week. If your build passes, the Vite 8 upgrade probably takes an afternoon.
More posts on frontend tooling, build configs, and React setups at atxsoft.com. If you hit something weird during the Vite 8 migration, drop a comment.
References
