Vitest 4.0 is out! To stay updated, read our blog post and check the migration guide. 🚨 Breaking Changes Remove 'basic' reporter - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/7884 (82fcf) Simplify default exclude pattern
Vitest breaking changes
The 3 releases whose own notes call out a breaking change, out of 60 the archive holds. Scattered one per release page, this is a run nobody can see; gathered, it is the shape of how often Vitest asks you to change your code.
- Tagged breaking
- 3of 60 releases
- Roughly
- 1 in 20releases held here
- Most recent
- 22 Oct 202510 months ago
- Across
- 11 monthsback to 2 Dec 2024
How this is decided
A release appears here because the word breaking is in the notes its publisher wrote, not because anyone here read the diff. That cuts both ways. A release that changed an API without using the word is missing from this page, and a release that used the word about something minor is on it. It is the publisher’s own signal, reported rather than judged, which is the same rule the security page follows.
Newest first
All Vitest releasesVitest 3 is here! There are a few breaking changes, but we expect the migration to be smooth. This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation. 🚨 Breaking C
🐞 Bug Fixes Revert support for Vite 6 - by @sheremet-va (fbe5c) This introduced some breaking changes (https://github.com/vitest-dev/vitest/issues/6992). We will enable support for it later. In the meantime, you can still use pnpm.override