The State of Vitest
summary
Vitest announces a stable report API with standardized event arguments and a simpler reporter surface; browser mode gains multi-browser instances that reuse one Vite server to cut runtime and a new custom locators API; provider configuration becomes function-based (imported from the provider package) to remove triple-slash refs; Vitest 4 adds rewritten spies and improved automocking, an abort signal for long tasks, an annotations API, built‑in visual regression support, Playwright traces output and Chromium debugging in VS Code, plus ongoing perf and docs overhauls.
AI-written summary · about
chapters (12)
- 0:00Introduction and growth
- 2:08New reporter API
- 3:35Browser mode and locators
- 6:39Abort signal and annotations
- 8:06Vitest 4 overview
- 10:31Mocking and spy improvements
- 13:21Vite-node transition
- 14:07Visual regression testing
- 15:03Playwright traces
- 16:13Browser debugging
- 17:44Performance and documentation
- 18:47Browser testing demo
related talks
20mVitest: testing DX reimagined
15mThe Road to Vitest 1.0
27mAnatomy of a Test Runner: What Vitest Keeps Getting Right
15mVitest Browser Mode
01h 19mVite Panel Discussion 2023
32mTesting React apps like it’s 2026
20mA Tour of the Vite Ecosystem
20mDeveloping, Documenting, and Testing your Vite app with Storybook