⚠️ Breaking Change
Impact Score: 7/10
Vitest v0.20.0 — Release Notes & Engineering Impact
Source available — automated, not human-reviewed
Component: vitest · Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-11-01.
Breaking-change evidence from the source
🚨 Breaking Changes - Apply Vite resolving algorithm to node_modules libraries - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/1673
⚡ Executive Summary (TL;DR)
Vitest v0.20.0. Source highlight: 🚨 Breaking Changes
Who Does This Impact? (Role-Based Analysis)
💻 Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
📊 Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
⚙️ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
⚠️ Breaking Changes & Deprecations (1)
- 🚨 Breaking Changes - Apply Vite resolving algorithm to node_modules libraries - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/1673
✨ New Features & Capabilities (1)
- Add option for ignoring unhandled errors -
🔧 Bug Fixes & Patches (6)
- **vite-node**: Allow dumpping the transformed code to debug -
- Don't clear mocks with vi.resetModules, cache normalised mock paths -
- Improve execution time counter - by @antfu <samp>(0d1f1)</samp>
- **browser**: Wait for files scanning in browser -
- **coverage**: Include `clover` reporter by default - by @antfu <samp>(5862e)</samp>
- **jsdom**: Use jsdom ArrayBuffer instead of Node, if jsdom is enabled -
📄 View Raw Release Notes (Original Developer Log)
### 🚨 Breaking Changes
- Apply Vite resolving algorithm to node_modules libraries - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/1673
### 🚀 Features
- Add option for ignoring unhandled errors - by @DerYeger in https://github.com/vitest-dev/vitest/issues/1678
- **vite-node**: Allow dumpping the transformed code to debug - by @antfu in https://github.com/vitest-dev/vitest/issues/1723
### 🐞 Bug Fixes
- Don't clear mocks with vi.resetModules, cache normalised mock paths - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/1726
- Improve execution time counter - by @antfu [<samp>(0d1f1)</samp>](https://github.com/vitest-dev/vitest/commit/0d1f1e87)
- **browser**: Wait for files scanning in browser - by @Aslemammad in https://github.com/vitest-dev/vitest/issues/1704
- **coverage**: Include `clover` reporter by default - by @antfu [<samp>(5862e)</samp>](https://github.com/vitest-dev/vitest/commit/5862e32e)
- **jsdom**: Use jsdom ArrayBuffer instead of Node, if jsdom is enabled - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/1727
- **types**: Fix MockedClass typeParams - by @Tanimodori in https://github.com/vitest-dev/vitest/issues/1735
- **ui**: Do not load graph if never displayed (fix #1602) - by @MPeloquin in https://github.com/vitest-dev/vitest/issues/1719
##### [View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v0.19.1...v0.20.0)