chore(deps): update vitest monorepo to ^2.1.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vitest/ui (source)	^2.1.4 -> ^2.1.5
vitest (source)	^2.0.5 -> ^2.1.5

---

Release Notes

vitest-dev/vitest (@​vitest/ui)

v2.1.5

Compare Source

   🚀 Features

• experimental: Expose vite on the test project as a separate field  -  by @​sheremet-va (bcc59)

   🐞 Bug Fixes

• dangerouslyIgnoreUnhandledErrors without base reporter  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6808 (0bf0a)
• Capture unhandledRejection even when base reporter is not used  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6812 (8878b)
• Don't change the working directory when loading workspace projects  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6811 (f0aea)
• Remove sequence.concurrent from the RuntimeConfig type  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6880 (6af73)
• Stop the runner before restarting, restart on workspace config change  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6859 (b01df)
• Don't rerun on Esc or Ctrl-C during watch filter  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6895 (98f76)
• Print ssrTransform error  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6885 (4c96c)
• Throw an error and a warning if .poll, .element, .rejects/.resolves, and locator.* weren't awaited  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6877 (93b67)
• browser:
  • Don't process the default css styles  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6861 (0d67f)
  • Support non US key input  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6873 (5969d)
  • Stop the browser rpc when the pool is closed  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6858 (9a0c9)
  • Init browsers eagerly when tests are running  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6876 (417bd)
• coverage:
  • Report uncovered files when re-run by enter or 'a'  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/6848 (487c8)
• ui:
  • Remove crossorigin attributes for same origin assets  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6883 (6e793)
• vite-node:
  • Improve esm check to decide external  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6816 (7e1fa)
  • Top-level throw in module is not reported properly  -  by @​vanaigr and @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/6840 (cf0cb)
• vitest:
  • Use fetch() implementation from happy-dom  -  by @​capricorn86 in https://github.com/vitest-dev/vitest/issues/6879 (3c56f)

   🏎 Performance

• Limit workspace project concurrency to available cores  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/6869 (f4c04)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.