Impact Score: 5/10
Vitest v0.0.121 — 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.
⚡ Executive Summary (TL;DR)
Vitest v0.0.121. Source highlight: incorrect behaviour of toBeDefined with not flag (97abcb9)
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.
✨ New Features & Capabilities (3)
- add spy name to assertion messages (#361) (0b4f19e)
- findRelatedTests flag, to run only changed tests (#363) (2a271b5)
- more expect compatible APIs (#360) (577ff67)
🔧 Bug Fixes & Patches (2)
- incorrect behaviour of toBeDefined with not flag (97abcb9)
- toStrictEqual didn't have an assertion (fc9524b)
📄 View Raw Release Notes (Original Developer Log)
### Bug Fixes
* incorrect behaviour of toBeDefined with not flag ([97abcb9](https://github.com/vitest-dev/vitest/commit/97abcb9))
* toStrictEqual didn't have an assertion ([fc9524b](https://github.com/vitest-dev/vitest/commit/fc9524b))
### Features
* add spy name to assertion messages ([#361](https://github.com/vitest-dev/vitest/issues/361)) ([0b4f19e](https://github.com/vitest-dev/vitest/commit/0b4f19e))
* findRelatedTests flag, to run only changed tests ([#363](https://github.com/vitest-dev/vitest/issues/363)) ([2a271b5](https://github.com/vitest-dev/vitest/commit/2a271b5))
* more expect compatible APIs ([#360](https://github.com/vitest-dev/vitest/issues/360)) ([577ff67](https://github.com/vitest-dev/vitest/commit/577ff67))