-
Notifications
You must be signed in to change notification settings - Fork 0
Update @vitest/coverage-v8 4.0.12 → 4.0.13 (patch) #459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
guibranco
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Automatically approved by gstraccini[bot]
|
@depfu merge |
|
Here's the code health analysis summary for commits Analysis Summary
|
|
Infisical secrets check: ✅ No secrets leaked! 💻 Scan logs2025-11-22T17:55:41Z INF scanning for exposed secrets...
5:55PM INF 396 commits scanned.
2025-11-22T17:55:42Z INF scan completed in 574ms
2025-11-22T17:55:42Z INF no leaks found
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @vitest/coverage-v8 (4.0.12 → 4.0.13) · Repo
Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)✳️ @vitest/ui (4.0.12 → 4.0.13) · Repo
Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)✳️ vitest (4.0.12 → 4.0.13) · Repo
Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Release Notes
4.0.13
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 5 commits:
chore: release v4.0.13perf: avoid fetchModule roundtrip if the module is cached (#9075)perf(experimental): if `fsCacheModule` is enabled, read from the memory when possible (#9076)fix(types): don't import node.js dependent types in vitest/browser (#9068)fix(types): don't use type from Vite 7.1 (#9071)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.