⚠️ Breaking Change
Impact Score: 7/10
Vitest v0.26.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 - **vite-node:** Rewrite how vite-node resolves id - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2463 [<samp>(58ee8)</samp>](https://github.com/vitest-dev/vitest/commit/58ee8e9b)
⚡ Executive Summary (TL;DR)
Vitest v0.26.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 - **vite-node:** Rewrite how vite-node resolves id - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2463 [<samp>(58ee8)</samp>](https://github.com/vitest-dev/vitest/commit/58ee8e9b)
✨ New Features & Capabilities (4)
- Added support for `SharedWorker`
- Introduce a native way to set env and globals - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2515 <samp>(b114d)</samp>
- Add html reporter based on Vitest UI - by @poyoho and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2444 <samp>(b8f34)</samp>
- If you have `@vitest/ui` installed, you can now use `'html'` reporter to get a beautiful UI to view your test results, inspect module graph and read log messages.
🔧 Bug Fixes & Patches (1)
- Allow assigning new hotContext - by @cometkim in https://github.com/vitest-dev/vitest/issues/2524 <samp>(b4c43)</samp>
📄 View Raw Release Notes (Original Developer Log)
### 🚨 Breaking Changes
- **vite-node:** Rewrite how vite-node resolves id - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2463 [<samp>(58ee8)</samp>](https://github.com/vitest-dev/vitest/commit/58ee8e9b)
- Correctly interop nested default for external and inlined modules - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2512 [<samp>(084e9)</samp>](https://github.com/vitest-dev/vitest/commit/084e929c)
- If your environment is `node`, Vitest will not resolve invalid named exports (exports that are on "default" property will not magically appear as named exports), unless `deps.interopDefault` is enabled, or dependency is in `deps.inline`. This change doesn't affect `jsdom`, `happy-dom` or `edge` environments.
- **web-worker:** Make web-worker implementation more compatible with spec - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2431 [<samp>(c3a63)</samp>](https://github.com/vitest-dev/vitest/commit/c3a63524)
- Messages are now cloned with `structuredClone`, if it's available, or fallbacks to a polyfill.
- Added support for `SharedWorker`
### 🚀 Features
- Introduce a native way to set env and globals - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2515 [<samp>(b114d)</samp>](https://github.com/vitest-dev/vitest/commit/b114d49f)
- Add html reporter based on Vitest UI - by @poyoho and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2444 [<samp>(b8f34)</samp>](https://github.com/vitest-dev/vitest/commit/b8f34eb8)
- If you have `@vitest/ui` installed, you can now use `'html'` reporter to get a [beautiful UI](https://vitest.dev/guide/ui.html) to view your test results, inspect module graph and read log messages.
### 🐞 Bug Fixes
- Allow assigning new hotContext - by @cometkim in https://github.com/vitest-dev/vitest/issues/2524 [<samp>(b4c43)</samp>](https://github.com/vitest-dev/vitest/commit/b4c43cd5)
##### [View changes on GitHub](https://github.com/vitest-dev/vitest/compare/v0.25.8...v0.26.0)