Vite 7 ships next month. The headline is the new dev server, which is a near-complete rewrite of the module graph and HMR pipeline. Here's the why and the how. The old graph couldn't scale Vite 4 and 5 used a flat module map keyed by URL. It worked beautifully for projects under…
Rolldown is now the default bundler. Cold-start builds on a 3k-module app dropped from 8.2s to 1.4s. HMR is also meaningfully faster. Migration guide in the thread.
Letting the AI write them feels good but the diff-explaining muscle atrophies fast. The real value of the description is that you understand what you changed.
Tailwind 4 ships its own Vite plugin and the docs imply PostCSS is optional. Are you removing it or keeping it for autoprefixer / nesting? Looking for opinions from folks who've migrated a real app.
I've shipped both this year. Curious what's blocking teams from moving and what's pulling them in. Streaming, server actions, loaders — where does each pull ahead?
Vue & Vite creator.
Vite 7 ships next month. The headline is the new dev server, which is a near-complete rewrite of the module graph and HMR pipeline. Here's the why and the how. The old graph couldn't scale Vite 4 and 5 used a flat module map keyed by URL. It worked beautifully for projects under…
Rolldown is now the default bundler. Cold-start builds on a 3k-module app dropped from 8.2s to 1.4s. HMR is also meaningfully faster. Migration guide in the thread.
Letting the AI write them feels good but the diff-explaining muscle atrophies fast. The real value of the description is that you understand what you changed.
Tailwind 4 ships its own Vite plugin and the docs imply PostCSS is optional. Are you removing it or keeping it for autoprefixer / nesting? Looking for opinions from folks who've migrated a real app.
I've shipped both this year. Curious what's blocking teams from moving and what's pulling them in. Streaming, server actions, loaders — where does each pull ahead?