Vite 8.0.0 went stable on March 12, 2026. Three weeks and seven patch releases later, the Vite team is on v8.0.7 as of April 7. That's a faster response cadence than most major releases in the JavaScript ecosystem, and it reflects the complexity inherent in swapping out both ESBuild and Rollup for Rolldown as the unified bundler.
What Stable Brought
The headline change from the beta cycle is Rolldown. Vite 8 is built around rolldown 1.0.0-rc.9, which replaced both ESBuild (used for dependency pre-bundling) and Rollup (used for production builds) with a single Rust-based bundler. The performance and memory benefits are real, particularly for larger projects, but so are the edge cases when you have hundreds of community plugins built against Rollup's exact hook interface.
Also new in the stable: browser console output is now forwarded to the dev server terminal. This was a frequently requested DX improvement — when you're debugging in the browser, the errors and logs now surface where you're already watching, instead of requiring a separate DevTools tab.
The Patch Tally
The changelog from v8.0.1 to v8.0.7 shows fixes across a wide surface area:
- v8.0.1 (March 19): Initial stable patch
- v8.0.2 (March 23): Dev server watch behavior fixes
- v8.0.3 (March 26): Further watcher refinements
- v8.0.4 (April 6): CSS and SSR fixes
- v8.0.5 (April 6): Additional SSR and module-runner fixes
- v8.0.6 (April 7): Continued bug fixes
- v8.0.7 (April 7): Latest patch
The rapid-fire April 6-7 releases suggest a specific batch of regressions was found and fixed quickly.
Notable fix categories across the cycle:
- Dev server: concurrent restart prevention, EADDRINUSE handling, proxy error responses (502 vs 500)
- CSS: public file URL handling with
server.origin, CSS injection for IIFE output - WASM: SSR support for
.wasm?init, asset URL regexlastIndexreset bug - Module runner: column number handling in sourcemaps, stacktrace robustness
- TypeScript/transform: tsconfig cache handling, symlink resolution
Browser Console Forwarding: Small Detail, Big DX
The addition of browser console forwarding to the dev server terminal (merged in beta.17) deserves specific mention. Previously, browser console output was disconnected from the terminal where you're running vite. With the default dev server configuration, console.log, errors, and warnings now appear where you're already watching. It's a quality-of-life improvement that aligns Vite's dev experience with the kind of integrated feedback that tools like Turbopack offer.
Vite 7 Still Supported
For projects not ready to move, Vite 7 remains supported. The v7 to v8 migration guide is available at vite.dev. The Vite team has been consistent that most straightforward projects migrate without significant issues, but projects with custom plugins or unusual bundler configurations should budget time for testing.
The upgrade path:
npm install vite@latest
Monitor the CHANGELOG for your specific plugins — the community ecosystem is still catching up to the Rolldown interface.
