db906fd85a
- Replace .eslintrc.cjs with eslint.config.mjs (ESLint 9 flat config)
using direct eslint-plugin-solid + @typescript-eslint/parser approach
- Add @typescript-eslint/parser to root devDependencies
- Add main/module/types top-level fields to packages/core/package.json
- Add resolve.conditions to packages/core/vite.config.ts
- Create packages/core/tsconfig.test.json for test type-checking
- Remove empty paths:{} from packages/core/tsconfig.json
12 KiB
Share
Vite 8.0 stable dropped on March 12, 2026, replacing its dual-bundler architecture with Rolldown, a single Rust-based bundler delivering 10-30x faster builds. Linear saw production builds shrink from 46 seconds to 6 seconds—an 87% reduction. With Vite downloaded 65 million times weekly, this upgrade affects millions of developers. Here’s your migration guide.
Vite 8 Unifies Build Pipeline with Rolldown
Vite 8 consolidates two bundlers into one. Previously, Vite used esbuild for fast development and Rollup for optimized production builds. This dual-bundler approach worked but created potential inconsistencies between dev and prod environments. Rolldown eliminates that split.
Rolldown is a Rust-based bundler with full Rollup API compatibility. It matches esbuild’s development speed while delivering 10-30x faster production builds than Rollup. In official benchmarks testing 19,000 modules, Rolldown completed in 1.61 seconds versus Rollup’s 40.10 seconds—a 25x improvement.
The architectural unification simplifies configuration. Developers no longer juggle separate esbuild and rollupOptions settings. One bundler, one config, consistent behavior across environments.
10-30x Faster Builds in Real-World Projects
Performance gains are substantial. Linear reduced production build times by 87%, dropping from 46 seconds to 6 seconds. Beehiiv’s large codebase saw 64% improvement. Mercedes-Benz.io cut build times by 38%.
However, performance gains scale with project size. Small projects under 100 modules see 2-5x improvements. Mid-sized projects between 100-500 modules hit 5-10x. Large projects with 500+ modules achieve the advertised 10-30x gains.
One developer testing a single-page app watched builds shrink from 3.8 seconds to 0.8 seconds—a clean 5x improvement. For large enterprise apps, these savings multiply across hundreds of daily builds, cutting hours from CI/CD pipelines.
How to Migrate to Vite 8
Migration is straightforward for most projects. Update Vite to 8.0, test locally, deploy if no issues arise. A compatibility layer auto-converts esbuild and rollupOptions configurations to Rolldown equivalents.
Basic migration:
# Update to Vite 8.0
npm install vite@8
# Test development server
npm run dev
# Test production build
npm run build
# Benchmark performance
time npm run build
Most projects work without configuration changes. The compatibility layer handles the transition automatically. If you encounter issues, Vite provides a gradual migration path: test with rolldown-vite on Vite 7 first, then upgrade to Vite 8 stable. This two-step approach isolates Rolldown-specific problems from general upgrade issues.
Should You Upgrade? Decision Framework
Upgrade priority depends on project size and build frequency. Large codebases with 500+ modules benefit most—10-30x gains justify immediate migration. Teams running multiple builds daily see compounding time savings. If CI/CD pipelines take 40 seconds per build, Rolldown cuts that to 2 seconds, saving 38 seconds × 100 builds = 63 minutes daily.
Mid-sized projects between 100-500 modules should upgrade within the month. You’ll see 5-10x improvements—noticeable but not game-changing. Standard release cycles (daily or weekly deploys) make this a medium priority.
Small projects under 100 modules see 2-5x gains. Still worthwhile, but less impactful. If you’re risk-averse or running mission-critical production apps, waiting 1-2 months for community feedback is reasonable. Let others find the edge cases first.
Skip immediate upgrade if you rely on obscure Rollup plugins that may lack Rolldown compatibility. Check the Vite plugin registry first. Also skip if you’re on Vite 6 or older—address that gap before jumping to Vite 8.
Troubleshooting Common Migration Issues
Three issues account for most migration headaches: CommonJS interop changes, manualChunks deprecation, and esbuild transform failures.
CommonJS imports may break due to Rolldown’s stricter module handling. If runtime errors appear when importing CJS modules, add legacy.inconsistentCjsInterop: true to your config temporarily. Long-term, migrate to ESM or fix module resolution. This isn’t Vite’s fault—it’s exposing existing module system inconsistencies.
The manualChunks config no longer works. Vite 8 uses codeSplitting instead, offering more granular control:
// OLD (Vite 7)
export default defineConfig({
build: {
rollupOptions: {
output: {
manualChunks(id) {
if (/\/react(?:-dom)?/.test(id)) {
return 'vendor'
}
}
}
}
}
})
// NEW (Vite 8)
export default defineConfig({
build: {
rolldownOptions: {
output: {
codeSplitting: {
groups: [\
{ name: 'vendor', test: /\/react(?:-dom)?/ }\
]
}
}
}
}
})
Plugins using transformWithEsbuild will fail because esbuild is no longer bundled. Migrate to transformWithOxc or install esbuild manually as a peer dependency. The @vitejs/plugin-react v6 already made this switch, using Oxc for React Refresh transforms and eliminating the Babel dependency entirely.
What’s Next for Vite
Vite’s roadmap includes Full Bundle Mode (experimental), which serves bundled files in development for 3× faster dev server startup, 40% faster full reloads, and 10× fewer network requests. This addresses one of Vite’s last pain points—hundreds of separate module requests in large apps.
VoidZero, the team behind Vite and Rolldown, is building a unified Rust toolchain for JavaScript development. Rolldown handles bundling, Oxc powers compilation and minification, and more tools are coming. The trend is clear: Rust-based tooling is replacing JavaScript-based build tools across the ecosystem, from swc to turbopack to Biome.
Key Takeaways
- Vite 8.0 stable replaces esbuild + Rollup with a single Rust bundler (Rolldown), delivering 10-30x faster production builds while maintaining plugin compatibility
- Large projects (500+ modules) see the biggest gains (10-30x), mid-sized projects hit 5-10x, small projects get 2-5x—performance scales with codebase size
- Most projects migrate without config changes thanks to auto-conversion, but CommonJS interop and manualChunks require manual fixes
- Upgrade now if you’re on Vite 7 with large codebases or frequent builds—the stable release is production-ready and compatibility is high
- Future Vite improvements (Full Bundle Mode, Rust toolchain expansion) show continued innovation, making this a safe long-term bet
Vite 8 isn’t just faster—it’s simpler. One bundler, one config, one mental model. The dual-bundler era is over.
Share
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.
BitNet Tutorial: Run 100B LLMs on CPU with 1-Bit Inference
OpenClaw China Ban: First AI Agent Crackdown
You may also like
Reddit Bot Verification: 100K Daily Removals Drive Crackdown
2 hours ago
AMD Ryzen 9 9950X3D2: First Dual-Cache CPU Hits 208MB
4 hours ago
Cloud Waste 2026: $235B Lost to Idle Resources
5 hours ago
LG 1Hz Display Pushes Dell XPS 16 to 27-Hour Battery Life
6 hours ago
macOS 26 Consistently Bad: It’s Design, Not Bugs
8 hours ago
Cursor Composer 2: 10x Cheaper Than Claude, Beats Opus 4.6
9 hours ago
Leave a reply Cancel reply
Your email address will not be published.Required fields are marked *
Comment
Name *
Email *
Website
Save my name, email, and website in this browser for the next time I comment.
Δ
More in: JavaScript
HTMX Tutorial 2026: Replace React with 14KB HTML
5 days ago
TanStack Start: Type-Safe React Framework for 2026
5 days ago
Hono Framework: Build Edge APIs on Cloudflare Workers
6 days ago
React Server Components: The Practical Guide for 2026
6 days ago
JavaScript Bloat: 3 Pillars Killing Bundle Size
6 days ago
Hono Framework: 14KB Edge API Alternative to Express
March 13, 2026
Next Article:
March 13, 2026
min read
-21 %
Latest Posts
Reddit Bot Verification: 100K Daily Removals Drive Crackdown
AMD Ryzen 9 9950X3D2: First Dual-Cache CPU Hits 208MB
Cloud Waste 2026: $235B Lost to Idle Resources
LG 1Hz Display Pushes Dell XPS 16 to 27-Hour Battery Life
macOS 26 Consistently Bad: It’s Design, Not Bugs
×