chore(deps-dev): bump vitest from 2.1.9 to 4.1.11 in the npm_and_yarn group across 1 directory - #33
Conversation
Bumps the npm_and_yarn group with 1 update in the / directory: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `vitest` from 2.1.9 to 4.1.11 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.11/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.11 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vitest 4 boots against vite 5 but its module-runner import fails (ERR_PACKAGE_PATH_NOT_EXPORTED). vitest 4's wide vite peer range let pnpm dedupe to the vite 5 that vitepress pins for packages/docs, so core gets its own vite@^7. @vitest/coverage-v8 must match the vitest major (was 2.1.8). Refs #33
- node:fs is no longer automocked into vi.fn()s under vitest 4;
bare vi.mock('node:fs') left real fs in place, so every
vi.mocked(existsSync) threw. Replaced with explicit factories
spreading importOriginal and overriding only the stubbed fns.
- vi.restoreAllMocks no longer resets factory vi.fn() mocks (only
spyOn spies), so mock calls leaked between tests. Use
vi.resetAllMocks, the v2 restore behaviour for these files.
- tag command tests @vitest-environment node: the jsdom environment
breaks node:fs mocking under vitest 4, and these tests are pure
CLI logic that never needed a DOM.
62 files, 1036/1036 tests green, coverage thresholds hold.
Refs #33
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Pushed two commits on top of the bump — the vitest 2 → 4 jump needed migration work before the suite would run:
Full suite green locally and in CI: 62 files, 1036/1036 tests, coverage thresholds hold. |
This branch was successfully deployed
1 participant
Bumps the npm_and_yarn group with 1 update in the / directory: vitest.
Updates
vitestfrom 2.1.9 to 4.1.11Release notes
Sourced from vitest's releases.
... (truncated)
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...a7a61e7chore: release v4.1.9 (#10598)934b0f5fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...7fb2965fix(browser): wait for orchestrator readiness before resolving browser sessio...a518019fix: fiximportOriginalwith optimizer and query import [backport to v4] (#...e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.