As reported on November 17, 2026, VoidZero released Vitest 5.0 with a focus on faster test runs and changes to defaults that may require updates to existing suites.
In benchmarks spanning a five-file utility package to a monolithic application with 1,280 modules, the Vitest team reported performance gains of about 8% to 25% in most configurations and up to 53% with VM pools. VoidZero also said overall performance, including browser mode, improved by about 18%. The reported gains come from inline projects sharing a Vite server, a now-stable disk fsModuleCache, fewer round trips between the main process and workers, and VM pools that can reuse compiled code. A new vitest doctor command reruns a suite under different configurations and suggests faster options.
Browser mode adds Trace View, which records interactions and assertions as DOM snapshots for step-by-step replay. The new vi.when API lets a single listener return different values for different arguments.
Several changes could affect existing tests: clearMocks now defaults to true; asynchronous assertions without await fail rather than warn; hoisted vi.mock calls outside the top-level scope throw errors; and toThrow('') now matches any error. OpenReplay noted that most of these changes expose already-invalid test code, but warned that suites relying on mock history leaking between tests could fail in CI despite passing locally under Vitest 4.
Vitest 5 requires Vite 6.4 and Node.js 22.12 or later. Yarn users must install Vite separately because it is now a peer dependency. Reports, attachments and blob reports have moved to .vitest/, so CI artifact paths may need updating. Ecosystem compatibility work was still underway: an issue report for Cloudflare’s vitest-pool-workers said its peer-dependency range was pinned to Vitest 4, which could prevent affected projects from running tests after upgrading.



