chore(deps-dev): bump vitest from 3.2.4 to 4.0.4

[dependabot]

Bumps vitest from 3.2.4 to 4.0.4.

Release notes

Sourced from vitest's releases.

v4.0.4

   🐞 Bug Fixes

• browser:
  • Correct typo  -  by @​benmccann in vitest-dev/vitest#8796 (ede1f)
  • Publish a missing context file for webdriverio  -  by @​sheremet-va in vitest-dev/vitest#8824 (7c7b6)
• mocker:
  • Support mocking builtins without node: prefix  -  by @​sheremet-va in vitest-dev/vitest#8829 (06208)
• pool:
  • Runner's error listener causing MaxListenersExceededWarning  -  by @​AriPerkkio in vitest-dev/vitest#8820 (d1bff)
  • Capture workers stdio to logger  -  by @​AriPerkkio in vitest-dev/vitest#8809 (fb95f)
• spy:
  • Allow classes in vi.mocked utility  -  by @​sheremet-va in vitest-dev/vitest#8839 (f8756)
• worker:
  • Rpc listener leak when isolate: false  -  by @​AriPerkkio in vitest-dev/vitest#8821 (573dc)

   🏎 Performance

• utils: Optimized reducer to avoid creating new objects  -  by @​Connormiha in vitest-dev/vitest#8818 (d19ce)

    View changes on GitHub

v4.0.3

   🐞 Bug Fixes

• Preserve reporter options from config when CLI reporters override them  -  by @​Copilot and sheremet-va in vitest-dev/vitest#8794 (15552)
• browser: More stable in-source testing validation  -  by @​sheremet-va in vitest-dev/vitest#8793 (62297)
• happy-dom: Support fetch globals  -  by @​sheremet-va in vitest-dev/vitest#8791 (0fb74)
• init: Use correct jsx/tsx extension  -  by @​sheremet-va in vitest-dev/vitest#8792 (abc04)

    View changes on GitHub

v4.0.2

   🐞 Bug Fixes

• browser:
  • Don't print the deprecation notice in node_modules  -  by @​sheremet-va in vitest-dev/vitest#8779 (588f7)
• pool:
  • Assign envs before running tests to keep in sync with process.env  -  by @​sheremet-va in vitest-dev/vitest#8769 (26ce8)
• spy:
  • Properly inherit implementation's length  -  by @​sheremet-va in vitest-dev/vitest#8778 (d4c2b)
  • Reset spies if both restoreMocks and mockReset are set in the config  -  by @​sheremet-va in vitest-dev/vitest#8781 (2eedb)

    View changes on GitHub

v4.0.1

   🐞 Bug Fixes

• Move the getBuiltins check  -  by @​sheremet-va in vitest-dev/vitest#8765 (81000)
• pool: Don't teardown the communication channel too soon if something is running after the test  -  by @​sheremet-va in vitest-dev/vitest#8767 (3fae7)

... (truncated)

Commits

• 9b75ec5 chore: release v4.0.4
• fb95fc7 fix(pool): capture workers stdio to logger (#8809)
• 06208d3 fix(mocker): support mocking builtins without node: prefix (#8829)
• 573dc06 fix(worker): rpc listener leak when isolate: false (#8821)
• d1bff3b fix(pool): runner's error listener causing MaxListenersExceededWarning (#8820)
• d19cece perf(utils): optimized reducer to avoid creating new objects (#8818)
• ede1f39 fix(browser): correct typo (#8796)
• ca1766f chore: release v4.0.3
• 155521a fix: preserve reporter options from config when CLI reporters override them (...
• abc046f fix(init): use correct jsx/tsx extension (#8792)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated development testing tooling to a newer version for improved performance and compatibility.

Walkthrough

The package.json file was updated to upgrade the vitest devDependency from version ^3.2.4 to ^4.0.4. This is a major version bump of the testing framework. No changes to public API signatures or module exports were made.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Single-file change: Only package.json modified
• Major version bump: vitest 3.x → 4.x warrants checking for potential breaking changes in test configuration or test suite compatibility
• DevDependency: No runtime code impact; changes only affect development and testing infrastructure
• Recommended focus areas:
  • Verify test suite runs successfully with vitest 4.0.4
  • Check for any breaking changes in vitest 4.x that may affect existing tests
  • Confirm compatibility with current test configuration if any version-specific settings exist

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "chore(deps-dev): bump vitest from 3.2.4 to 4.0.4" directly and clearly describes the main change in the changeset, which is updating the vitest devDependency from version 3.2.4 to 4.0.4. The title uses appropriate conventional commit formatting with a scope, is concise and readable, and provides sufficient specificity that a teammate scanning the history would immediately understand the update. The title accurately reflects what the raw summary indicates as the only modification to package.json.
Description Check	✅ Passed	The pull request description is directly related to the changeset as it explicitly discusses bumping vitest from 3.2.4 to 4.0.4, provides comprehensive release notes covering bug fixes and performance improvements in the new versions, and includes relevant metadata such as compatibility information and commit references. The description clearly communicates the purpose of the dependency upgrade and provides context about what has changed in the new version, making it well-suited for understanding the update.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7dbf2c7 and 7e81804.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (1)

package.json (1)

38-38: Verify tests pass after vitest 4.0 major version upgrade.

This is a major version bump from 3.2.4 to 4.0.4. Major version upgrades typically introduce breaking changes. While the release notes highlight bug fixes and performance improvements, we need to confirm that:

• All tests continue to pass without modification
• The vitest configuration (if one exists) is compatible with 4.0.x
• Any test code relying on deprecated or changed APIs is updated

Can you confirm that the test suite (npm run test) executes successfully with vitest 4.0.4? If there are CI/CD logs or a build report, those would help verify compatibility. You may also want to check the vitest migration guide for any breaking changes between 3.x and 4.0 that affect this project.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}