Impact Score: 5/10
Vitest v1.1.3 — 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 v1.1.3. Source highlight: 🐞 Bug Fixes
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.
🔧 Bug Fixes & Patches (2)
- Vi.mock breaks tests when using imported variables inside the factory - by @sheremet-va and **Dunqing** in https://github.com/vitest-dev/vitest/issues/4873 <samp>(7719e)</samp>
- Apply `slowTestThreshold` to all reporters - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4876 <samp>(1769c)</samp>
📄 View Raw Release Notes (Original Developer Log)
### 🐞 Bug Fixes
- **vitest**:
- Vi.mock breaks tests when using imported variables inside the factory - by @sheremet-va and **Dunqing** in https://github.com/vitest-dev/vitest/issues/4873 [<samp>(7719e)</samp>](https://github.com/vitest-dev/vitest/commit/7719e79e)
- Apply `slowTestThreshold` to all reporters - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/4876 [<samp>(1769c)</samp>](https://github.com/vitest-dev/vitest/commit/1769c796)
##### [View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v1.1.2...v1.1.3)