Vitest v0.29.3stable Released Mar 15, 2023
Impact Score: 5/10

Vitest v0.29.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.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Vitest v0.29.3. Source highlight:    ๐Ÿš€ Features

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)

  • Use custom colors implementation instead of picocolors &nbsp;-&nbsp; by @sheremet-va <samp>(427b0)</samp>
  • Uncaught errors to indicate env teardown &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2982 <samp>(1fe82)</samp>
  • **config**: Add an option to run setupFiles in sequence &nbsp;-&nbsp; by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3008 <samp>(c2e25)</samp>

โšก Performance & Enhancements (1)

  • **reporters**: Overall improvements &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3006 <samp>(22ca0)</samp>

๐Ÿ”ง Bug Fixes & Patches (6)

  • Console log not visible &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2943 <samp>(02808)</samp>
  • Remove duplicate execArgv when deps.registerNodeLoader: true &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2965 <samp>(a1954)</samp>
  • Prevent running test cases timers after environment teardown &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2971 <samp>(bde75)</samp>
  • Don't mark setupFiles as test files, if experimentaOptimizer is used &nbsp;-&nbsp; by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2974 <samp>(819c6)</samp>
  • Config errors not visible &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2995 <samp>(f01c7)</samp>
  • --inspect to work inside workers &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2983 <samp>(36087)</samp>
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
### &nbsp;&nbsp;&nbsp;๐Ÿš€ Features - Use custom colors implementation instead of picocolors &nbsp;-&nbsp; by @sheremet-va [<samp>(427b0)</samp>](https://github.com/vitest-dev/vitest/commit/427b0622) - Uncaught errors to indicate env teardown &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2982 [<samp>(1fe82)</samp>](https://github.com/vitest-dev/vitest/commit/1fe8286c) - **config**: Add an option to run setupFiles in sequence &nbsp;-&nbsp; by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3008 [<samp>(c2e25)</samp>](https://github.com/vitest-dev/vitest/commit/c2e25bb9) ### &nbsp;&nbsp;&nbsp;๐Ÿž Bug Fixes - Console log not visible &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2943 [<samp>(02808)</samp>](https://github.com/vitest-dev/vitest/commit/0280825f) - Remove duplicate execArgv when deps.registerNodeLoader: true &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2965 [<samp>(a1954)</samp>](https://github.com/vitest-dev/vitest/commit/a1954cc0) - Prevent running test cases timers after environment teardown &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2971 [<samp>(bde75)</samp>](https://github.com/vitest-dev/vitest/commit/bde75a34) - Don't mark setupFiles as test files, if experimentaOptimizer is used &nbsp;-&nbsp; by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2974 [<samp>(819c6)</samp>](https://github.com/vitest-dev/vitest/commit/819c6cbe) - Config errors not visible &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2995 [<samp>(f01c7)</samp>](https://github.com/vitest-dev/vitest/commit/f01c7833) - --inspect to work inside workers &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2983 [<samp>(36087)</samp>](https://github.com/vitest-dev/vitest/commit/36087d1e) - **types**: Use `any` as default value for TArgs in vi.fn() &nbsp;-&nbsp; by @jessevanassen in https://github.com/vitest-dev/vitest/issues/2947 [<samp>(1bdcc)</samp>](https://github.com/vitest-dev/vitest/commit/1bdcc212) ### &nbsp;&nbsp;&nbsp;๐ŸŽ Performance - **reporters**: Overall improvements &nbsp;-&nbsp; by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3006 [<samp>(22ca0)</samp>](https://github.com/vitest-dev/vitest/commit/22ca0b6b) ##### &nbsp;&nbsp;&nbsp;&nbsp;[View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v0.29.2...v0.29.3)