@vitest/coverage-v8
5.1.0 · 2 Nov 2026MIT66.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vitest/coverage-v8 From 0.32.2 to 0.34.6
10 releases in betweenevery note read
- 9
- changes to make
- 0
- advisories fixed
- 17
- new
- 67
- fixes
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
- Deprecated0.34.0
Release by release
- 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
Use lazy require in vm pool
- Fixed
Update HappyDOMOptions to be compatible with v12
- Fixed
Print value shape when .resolves and .rejects fails
- New
- Fixed
Resolving dep optimizer issues with workspace
- Fixed
Don't process config file twice
- Fixed
- New
Add workspace config files to default coverage excludes
- Fixed
Should remove mockPath from callstack whether success or failed
- Fixed
Report file error as a <failure> on JUnit
- 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
- Breaking
Transform mode affects only test files, not regular files
- Breaking
Custom environment now should be processed before Vitest can consume it. It means that you cannot specify a path to a TS file or use import paths that should be processed by Vite.
- Breaking
Disable
coverage.reportOnFailureby default - Breaking
Remove
@vitest/coverage-c8package
- Breaking
- Breaking
Revert default include patterns
- New
Add missing JSDom living keys
- Fixed
vite-node: Don't fail when importing Promise module
- Fixed
vite-node: Allow importing node:test
- Breaking
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.
2 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.