Vite 8 beta promises 10-30x faster builds by replacing esbuild and Rollup with Rolldown, a Rust-powered bundler. Linear’s production builds dropped from 46 seconds to 6 seconds. Another team saw compile times for a 3MB project shrink from 15 seconds to 3 seconds. But migration isn’t automatic. Breaking changes require configuration updates, and developers need to choose between two migration paths. Here’s how to upgrade to Vite 8 + Rolldown without breaking your project.
Choose Your Migration Path
Vite 8 offers two migration strategies. Pick based on your project complexity and risk tolerance.
Direct upgrade works for simple projects with minimal custom configuration. Update package.json to Vite 8 beta, run install, update config for breaking changes, test your dev server, and build for production. Five steps, done in under an hour for most projects.
Gradual migration reduces risk for complex production applications. First, migrate to the rolldown-vite package. Test for Rolldown-specific issues in isolation. Once stable, upgrade to Vite 8 proper. This two-phase approach separates Rolldown compatibility from other Vite 8 changes, making debugging easier.
The gradual path takes longer but matters for enterprise apps where a broken build costs time and money. Direct upgrade works when you have good test coverage and can afford to troubleshoot issues as they surface.
Three Breaking Changes You’ll Hit
Most developers encounter three configuration changes. Handle these and you’re 90% done.
Manual chunks changed. Vite 7’s rollupOptions.output.manualChunks object form is gone. Vite 8 uses rolldownOptions.output.codeSplitting instead. If you’re manually splitting vendor code, update your config:
// BEFORE (Vite 7)
export default {
build: {
rollupOptions: {
output: {
manualChunks: {
vendor: ['react', 'react-dom']
}
}
}
}
}
// AFTER (Vite 8)
export default {
build: {
rolldownOptions: {
output: {
codeSplitting: {
// More flexible configuration
}
}
}
}
}Dependency optimization switched from esbuild to Rolldown. Vite auto-converts optimizeDeps.esbuildOptions to rolldownOptions, but the old syntax is deprecated. Use optimizeDeps.rolldownOptions directly for future compatibility.
Plugin hooks need module type specification. If your custom plugin transforms content to JavaScript from another format, add moduleType: 'js' to the return value. This only affects custom plugins that convert module types. Standard Vite plugins work without changes.
Standard Vite configurations work without modification. These breaking changes only matter if you’re using advanced Rollup config or custom plugins. Check the official migration guide for your specific setup.
Performance Wins Are Immediate
The reason to tolerate breaking changes: builds get dramatically faster.
Linear’s production builds dropped from 46 seconds to 6 seconds. That’s 7.6x faster, or 40 seconds saved per build. Multiply that across a team running dozens of builds daily, and you’re saving hours. Another team reported a 3MB project compiling in 0.7 seconds (dev mode) instead of 2.5 seconds, and 3 seconds (production) instead of 15 seconds.
The general performance range is 10-30x faster than Rollup. Your mileage varies based on project size and configuration, but the wins are consistent. Faster builds mean faster feedback loops. You catch bugs sooner, iterate quicker, and deploy faster. CI/CD pipelines benefit too—shorter build times reduce queue wait and infrastructure costs.
An upcoming feature called Full Bundle Mode promises 3x faster dev server startup, 40% faster full reloads, and 10x fewer network requests. Vite’s already-excellent DX is getting better. See real-world benchmarks for detailed comparisons.
Plugin Compatibility Is Better Than Expected
The plugin ecosystem was a migration concern, but compatibility exceeded expectations. Most Vite plugins work out of the box with Vite 8. Rolldown supports the same plugin API as Rollup and Vite, so ecosystem plugins rarely need updates.
The VoidZero team tested key frameworks and meta-frameworks: SvelteKit, react-router, and Storybook all work without changes. A compatibility layer helps migrate from Rollup and esbuild options automatically, smoothing the transition for most codebases.
Two edge cases matter for plugin developers. If a plugin uses transformWithEsbuild, esbuild becomes an optional peer dependency you must install manually. The recommended fix: use the new transformWithOxc function instead. Some obscure Rollup-specific options aren’t supported by Rolldown, which triggers warnings (not errors). Check the Rolldown integration docs if you rely on advanced Rollup features.
For most developers, plugin compatibility is a non-issue. The breaking changes affect configuration, not the plugin ecosystem.
When to Migrate: Test Now, Produce Later
Here’s the honest guidance: Vite 8 is beta, not production-ready. But that doesn’t mean you should ignore it.
Test and experiment now. Side projects are safe to upgrade. Local development environments are ideal testing grounds. Non-production apps let you validate the migration path without risk. Early adopters using the gradual migration strategy can test Rolldown compatibility today, then upgrade to stable when it ships.
Wait for stable release on production apps. Don’t deploy beta releases to critical business applications. The Vite team hasn’t announced a stable release date—they follow a feedback-driven schedule, not a fixed timeline. Based on past patterns, expect 8.0.0 stable in Q2-Q3 2026.
Beta is stable enough for experimentation. The community feedback has been overwhelmingly positive. But pre-releases may ship breaking changes between versions, and thorough testing is required after any upgrade. The risk/reward calculation favors testing now, migrating production later.
One developer summarized it well: “Huge upgrade in not having to wait 4 seconds each time when testing builds repeatedly.” Those seconds compound. Early adopters get a preview of the future, find compatibility issues before stable launch, and smooth their migration timeline. Just don’t bet the company on beta software.
Bottom Line
Vite 8 + Rolldown delivers 10-30x faster builds with a smoother migration path than the version bump suggests. Choose direct upgrade for simple projects, gradual migration for complex production apps. Handle three breaking changes (manual chunks, dependency optimization, plugin module types), validate your plugin compatibility, and test thoroughly. Performance wins are immediate and measurable—Linear’s 40-second savings per build is real.
Test Vite 8 beta now on non-production projects. When the stable release ships, you’ll already know your migration path. Visit the official announcement for installation instructions and detailed documentation.
