Why one bundler matters

Vite previously used esbuild for fast development transforms and Rollup for production bundles. Two pipelines created differences in module handling, separate settings, and a compatibility layer.

Rolldown is designed as a fast bundler with Rollup API compatibility. In Vite 8 it handles dependency optimization and production builds.

What a project gains

A common development and production foundation reduces “works locally, fails in build” errors and creates room for persistent caching, better chunk splitting, and Module Federation.

Most Vite and Rollup plugins should keep working. Plugins that depend on Rollup internals or esbuild-specific options need closer review.

A migration without heroics

  1. Upgrade Node to a supported version.
  2. Record current build metrics and bundle composition.
  3. Upgrade Vite on a separate branch and read the migration guide.
  4. Review custom plugins and renamed esbuild options.
  5. Compare unit, e2e, SSR, and production preview results.

Products that support older browsers should declare a target explicitly.

Should you upgrade immediately?

A new project can reasonably start with Vite 8. For a stable product, the answer depends on plugins and CI cost. The closer the configuration is to defaults, the easier the migration.

Users only feel measured outcomes: a faster dev server, shorter builds, or a more stable pipeline.

Sources

  1. Vite — Vite 8 announcement
  2. Vite — Migration from v7
  3. Vite — Releases