Vite migration: switch without downtime
An executable path for moving an existing project to Vite, with a rollback plan.
Quick answer
How do I keep Vite and Rollup versions aligned?
Vite bundles a specific Rollup major version. Do not bump Rollup independently when upgrading Vite, or manualChunks behavior and the resulting split will drift.
Machine-readable page data: /data/vite-migration.json
In-depth analysis
Vite's native-ESM dev server and Rollup-based production bundling set the baseline for modern frontend build performance and developer experience. Migration runs in parallel with validation and gradual cutover — keep a switch that rolls back in seconds so business never breaks.
// vite.config.ts — production build, deep optimization
import { defineConfig } from 'vite';
export default defineConfig({
build: {
target: 'es2022',
cssCodeSplit: true,
rollupOptions: {
output: { manualChunks: { vendor: ['vue', 'react'] } },
},
},
});Vite Migration · Key takeaways
- Full branch build passes
- All 8 Preview drills green
- Production and Preview KV isolated
- Rollback switch ready
FAQ & pitfalls
How do Vite build artifacts get long-cached at the edge?
Hash-filename assets get immutable long cache; entry HTML gets must-revalidate. Changing the filename changes the URL, which naturally sidesteps cache stampedes.
Explore the hub
See all 5 guides in Edge ArchitectureSame category as this article, sorted across the codebase.
AI Search migration: switch without downtime
An executable path for moving an existing project to AI Search, with a rollback plan.
Astro migration: switch without downtime
An executable path for moving an existing project to Astro, with a rollback plan.
Cloudflare Pages migration: switch without downtime
An executable path for moving an existing project to Cloudflare Pages, with a rollback plan.
Cloudflare Pages deployment guide
A hands-on, zero-ops edge deployment using Git-driven Cloudflare Pages.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
What goes wrong when Vite manualChunks is misconfigured?
A wrong split pushes styles into the JS bundle or creates circular dependencies, and first-paint size goes up instead of down. Start with a coarse vendor split, then refine it.
See the full guide → - 02
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 03
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide →