@vitest/coverage-v8
5.1.0 · 2 Nov 2026MIT66.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vitest/coverage-v8 From 1.2.2 to 1.6.1
9 releases in betweenevery note read
- 2
- changes to make
- 0
- advisories fixed
- 34
- new
- 90
- fixes
Before you upgrade
Tick each one off as you go- Deprecated1.4.0
- Deprecated1.3.0
Security
Release by release
- Security
- Fixed
Backport #7317 to v1
- New
Support standalone mode
- New
Custom "snapshotEnvironment" option
- New
benchmark: Support comparing benchmark result
- New
browser: Allow injecting scripts
- New
- Fixed
Use package.json name for a workspace project if not provided
- Fixed
Backport jest iterable equality within object
- Fixed
browser: Support benchmark
- Fixed
reporter: Use default error formatter for JUnit
- Fixed
- Fixed
Check for null before storing in weakmap
- Fixed
- New
api:
startVitest()to acceptstdoutandstdin - Fixed
Close vite servers on all resolved projects
- Fixed
Fix default
import.meta.env.PROD: false - Fixed
Resolve cwd correctly when initiating projects
- New
- New
Add configuration for diff truncation
- New
Remove unrelated noise from diff for toMatchObject()
- New
Allow custom host for --inspect and --inspect-brk
- New
coverage: V8 to ignore empty lines, comments, types
- New
- Deprecated
config: Deprecate
cache.diroption - New
Throw error when using snapshot assertion with
not - New
Add a flag to include test location in tasks
- New
cli: Support wildcards in
--projectoption
- Deprecated
- New
vitest: Expose parseCLI method
- New
Add task tests iteratively
- Fixed
coverage: Ignore generated TS decorators
- Fixed
ui: Auto reload coverage iframe after test run
- New
1 internal line (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.