Vite 8 Launches with a Radical Architecture Overhaul, Cutting Build Times from 46 s to 6 s

On March 12, the Vite team officially released version 8.0.

The most significant change is a complete rewrite of the build architecture. Vite 2 relied on a dual‑engine setup: esbuild for development pre‑bundling and Rollup for production bundling, which sometimes caused bugs that appeared only after deployment. Vite 8 discards both engines and introduces Rolldown , a Rust‑based bundler whose API is compatible with Rollup, together with Oxc , a Rust compiler that replaces Babel and other JavaScript transformers. The new stack consists of three Rust components: the Vite core, Rolldown as the bundling engine, and Oxc for compilation and transformation.

Performance gains are substantial. The official blog lists real‑world data: Linear’s build time dropped from 46 seconds to 6 seconds (≈8× faster), Ramp saw a 57 % improvement, Mercedes‑Benz.io achieved up to 38 % faster builds, and Beehiiv reported a 64 % speedup. A developer on Twitter measured a reduction from 43 seconds to 6.79 seconds. The magnitude of improvement varies with project size; larger projects benefit the most.

Another key change is the removal of Babel. The React plugin @vitejs/plugin-react was upgraded to v6, switching its underlying transformation engine from Babel to Oxc. This eliminates Babel as a required dependency, reduces install size, speeds up React compilation, and removes a historical “baggage” layer. Non‑React projects also no longer depend directly on esbuild or Rollup, resulting in a cleaner dependency tree.

Vite 8’s binary is about 15 MB larger than Vite 7, mainly due to lightningcss (~10 MB for better CSS minification) and Rolldown itself (~5 MB). The trade‑off is considered worthwhile given the time savings.

New features include:

Native TypeScript path alias support . Previously developers needed the vite-tsconfig-paths plugin; now a single configuration entry suffices:

export default defineConfig({
  resolve: {
    tsconfigPaths: true
  }
})

Decorator metadata support . Frameworks that rely on emitDecoratorMetadata (e.g., NestJS) work out of the box without extra Babel or SWC configuration.

Built‑in Vite Devtools for debugging and analyzing the build process, helping locate plugin performance bottlenecks.

Browser console.log forwarding to the dev server terminal, which simplifies SSR debugging.

WASM SSR support via the .wasm?init import syntax, enabling WebAssembly modules to run in server‑side rendering environments.

Upgrade considerations:

Node.js version requirement is raised to 20.19+, 22.12+, or newer; projects still on Node 18 need to upgrade.

The recommended migration path is to first install the transitional package rolldown-vite while on Vite 7, resolve any compatibility issues, and then upgrade to Vite 8.

Future directions hinted by the blog include an experimental “Full Bundle Mode” that builds during development for up to three‑fold faster startup, native AST manipulation in Rust to replace tools like MagicString, and a stabilized environment API that unifies Node, Edge, and browser builds.

From Vite 2 to Vite 8, the project has moved from a quick‑start community‑driven approach (esbuild + Rollup) to a self‑maintained Rust‑centric stack (Rolldown + Oxc). The core logic is clear: rewrite critical paths in Rust, eliminate dual‑engine inconsistencies, and push build performance to a new tier. For developers, the tangible benefits are faster builds, fewer configuration steps, and a cleaner dependency graph. Upgrading is optional for stable Vite 7 projects, but new projects have strong reasons to start with Vite 8.