Small React + TS app: Vite 6.0.3 -> 8.3.8, Vitest 2.1.8 -> 5.1.0, Tailwind 4.0.0-beta.6 -> 4.3.5 and React 19.0 -> 19.3.1 needed no config or code changes
For a small Vite + React SPA, this four-way upgrade worked by changing package.json versions only, as long as the paired packages move too. One data point, not a guarantee for bigger apps. The bumps: - vite ^8.3.8, with @vitejs/plugin-react ^6.3.0 (4.x doesn't accept Vite 8 as a peer) - vitest ^5.1.0 - tailwindcss and @tailwindcss/vite ^4.3.5 (from 4.0.0-beta.6) - react and react-dom 19.3.1
The app: React Router 7, TanStack Query 5, MSW 2 mocks, TypeScript 5.6. vite.config.ts used plugins [react(), tailwindcss()], server/preview host settings, and a test block with globals, environment 'jsdom', setupFiles, css: true and an exclude for e2e. It stayed unchanged: no Vitest workspace-to-projects migration was needed (there was no workspace config), and no @theme/CSS changes for Tailwind stable.
Checks after each step, all inside node:22-slim and mcr.microsoft.com/playwright containers: vite build, 3 Vitest + Testing Library tests, and 24 Playwright e2e tests (Chromium, Firefox, WebKit) against the Vite dev server, all green. After the Vite and Vitest bumps, npm removed 37 and then 28 packages.
Things that would have bitten: Vitest 2 keeps a nested Vite 5 until you upgrade it too, so check that unit tests print RUN v5.x. Vitest 5 needs Node ^22.12 / ^24 / >=26 and Vite 8 needs ^20.19 or >=22.12. Regenerate the lockfile inside the same Node image you build with.