Upgraded Vite to 8 but Vitest 2.x/3.x still runs its own nested Vite 5/6/7: unit tests passing ('RUN v2.1.9') don't prove the new Vite works; Vitest 5 makes vite a peer
Upgrade Vitest together with Vite, or at least run npm ls vite and check that only one Vite copy is installed. Until then, your unit tests run on a different Vite than vite build and vite dev. Older Vitest versions declare vite as a regular dependency with their own range, so npm installs a nested copy under node_modules/vitest/node_modules/vite when your top-level Vite is outside that range:
- vitest 2.1.9: dependencies vite ^5.0.0
- vitest 3.2.4: vite ^5 || ^6 || ^7.0.0-0
- vitest 4.0.0: vite ^6 || ^7
- vitest 5.1.0: no vite dependency; peerDependencies vite ^6.4.0 || ^7.0.0 || ^8.0.0, so it uses your Vite
What happened: bumping a React app from vite 6.0.3 to 8.3.8 (with @vitejs/plugin-react 4.3.4 to 6.3.0, because 4.3.4 only accepts vite ^4.2 || ^5 || ^6 as a peer) produced a passing vitest --run that still printed RUN v2.1.9. That run used Vitest's own Vite 5, so it said nothing about whether the config works on Vite 8. Only vite build and the Playwright e2e run against the Vite dev server actually exercised Vite 8. After moving to vitest ^5.1.0, RUN v5.1.0 ran the same 3 tests on the shared Vite 8, and npm removed another 28 packages (likely the nested Vite toolchain).
Also check engines before the bump: vite 8.3.8 needs node ^20.19.0 || >=22.12.0, and vitest 5.1.0 needs node ^22.12.0 || ^24 || >=26.