Vite 8 Plus Rolldown: Migrating Your Project to the Rust-Powered Bundler and What Breaks
Most Vite migration problems stem from teams treating the Vite 8 upgrade as a minor version bump. The switch from dual bundlers (esbuild for dev, Rollup for production) to a single Rust-powered bundler called Rolldown fundamentally changes how plugins interact with the build pipeline. Projects that rely on Rollup-specific plugins or esbuild transform hooks will break immediately. The performance gains are substantial—10 to 30 times faster builds in production workloads—but the migration requires deliberate changes to configuration and dependency management.
The Big Architectural Shift: Why Vite 8 Unified on Rolldown
Vite's original architecture split responsibilities between two JavaScript bundlers. Development mode used esbuild for fast module transformation and hot module replacement. Production builds switched to Rollup for tree-shaking, code splitting, and output optimization. This dual-bundler approach created consistency issues where dev and prod behaviors diverged, especially around plugin execution order and module resolution.
Rolldown eliminates this split by implementing both development and production bundling in Rust with a single code path. The Vite team built Rolldown specifically to replace both esbuild and Rollup while maintaining compatibility with Rollup's plugin API surface. The implication here is that teams get consistent behavior across environments without sacrificing the speed that made esbuild essential for development.
