# Vite 8 replaces its dual bundlers with Rolldown > Vite 8 makes the Rust-based Rolldown bundler its unified development and production pipeline, with compatibility shims and migration guidance. Canonical URL: https://www.devobs.io/news/news-vite-8-rolldown-release/ By: Elias Brooks Published: 2026-09-06T11:58:54.648Z Updated: 2026-09-06T11:58:54.648Z Event date: 2026-03-12 Section: Developer tools Vite 8 reached stable release on March 12 with Rolldown as its single bundler. The [Vite team’s announcement](https://vite.dev/blog/announcing-vite8) describes the change as a replacement for the previous split between esbuild during development and Rollup for production builds. ## One pipeline removes a source of divergence The earlier design optimized each phase independently, but it also meant that module resolution and transformations could pass through different implementations. Rolldown uses a Rollup-compatible plugin model and now handles both sides of Vite’s workflow. Vite says a compatibility layer translates existing `esbuild` and `rollupOptions` configuration in many projects. The release also adds optional TypeScript path resolution, WebAssembly imports for server-side rendering, browser-console forwarding to the development terminal, and an integrated DevTools option. Alongside core Vite 8, `@vitejs/plugin-react` v6 moves its React Refresh transform to Oxc and removes Babel from the default dependency path. ## Plugin behavior is the migration test A unified bundler does not make every plugin automatically equivalent. Plugins that depend on undocumented Rollup details, transform ordering, emitted chunk names, or esbuild-specific options deserve targeted checks. Vite recommends a staged route for complex projects: try the `rolldown-vite` preview package with Vite 7 first, then move to Vite 8 once bundler-specific differences are isolated. Teams should compare production chunk graphs, dynamic imports, CSS ordering, source maps, and SSR output before and after the change. Keep measurements local to the application: the project publishes large benchmark gains, but custom plugins and dependency shapes determine actual results. The architectural benefit is easier to assess than a headline speed number—development and production now share more of the same parsing, resolution, and transformation machinery. ## Source references -