Migrate Webpack → Vite

Vite's dev experience (sub-second cold start, instant HMR) is dramatic compared to webpack. Migration is moderately complex; the key insight is that Vite is config-by-omission — most webpack config disappears entirely.

When to use

• Webpack dev server takes > 10s to start, > 200ms HMR.
• Maintenance of webpack config is a tax — too many plugins, brittle config.
• Project is Vue/Svelte (Vite is more native).
• React project willing to pay one-time migration cost for ongoing dev-time win.

When NOT to use

• Heavy use of webpack-specific plugins with no Vite equivalent (rare, but check).
• Module Federation (some Vite plugins exist but maturity varies).
• Server-side render with Webpack-managed SSR (use Next.js or Nuxt instead — they handle their own bundler).

Core differences