@vitest/expect
5.0.5 · 15 Oct 2026MIT151.9M / weekRepositoryHomepagenpmAtom feed
Upgrading @vitest/expect from 0.29.1 to 0.34.7
28 releases in betweennotes for 27
- 23+
- changes to make
- 0
- advisories fixed
- 62+
- new
- 198+
- fixes
Counted from 27 of 28 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- breaking0.34.0
- breaking0.34.0
- breaking0.34.0
- breaking0.34.0
- breaking0.34.0
- breaking0.34.0
- breaking0.34.0
- breaking0.33.0
- breaking0.32.0
- breaking0.32.0
Release by release
0.34.7no release note
- fixed
Overwrite global URL with environment's
- fixed
Correctly resolve external dependencies loaded by custom environments
- fixed
runner: The fixture of
test.extendshould be init once time in all test
- fixed
- new
config: Add
diffoption - new
coverage: Add
coverage['100']to istanbul provider - new
vitest: Support
vi.waitFormethod - new
vitest: Allow using unprocessed environment files
- new
- fixed
Resolving dep optimizer issues with workspace
- fixed
Don't process config file twice
- fixed
coverage: Log info only when terminal reporter is used
- fixed
happy-dom: Use the nodejs console in happy-dom v11
- fixed
- new
coverage: Add
allowExternaloption - new
vitest: Export all reporters in
vitest/reporters - new
Add workspace config files to default coverage excludes
- fixed
Should remove mockPath from callstack whether success or failed
- new
- new
Allow importing CSS and assets inside external dependencies when using
--experimental-vm-threads - new
vitest: Allow calling
ctx.skip()inside the running test - new
ui: Add support for ui coverage with subdir option
- new
dot-renderer: Speed up getTests
- new
- fixed
Pass
--experimental-vm-worker-memory-limittotinypool
- fixed
- new
Support
describe.sequential - new
Support config junit reporter className with env
- new
Running vitest with
--related --watchreruns non-affected tests if they were changed during a run - fixed
Isolate workers between envs and workspaces
- new
1 other line we could not sort, mostly version bumps
- 0.34.0
Most of
deps.options are now moved toserver.depswith a deprecation warning. Please, consider usingdeps.optimizerinstead ofdeps.inline/deps.external. Ideally, we would like to move away from usingserver.deps.inlinealtogether.
4 internal lines (docs, tests, tooling) left out.