Bump vitest from 1.6.0 to 2.0.2

[dependabot[bot]]

Bumps vitest from 1.6.0 to 2.0.2.

Release notes

Sourced from vitest's releases.

v2.0.2

   🐞 Bug Fixes

• browser:
  • Remove @​vitest/runner > pretty-format from prebundling because it doesn't exist  -  by @​sheremet-va in vitest-dev/vitest#6075 (a169d)
  • Inline pretty-format and replace picocolors with tinyrainbow  -  by @​sheremet-va in vitest-dev/vitest#6077 (80a43)
  • Remove crypto.randomUUID from the client  -  by @​userquin in vitest-dev/vitest#6079 (04c83)
  • Correctly overwrite loupe require  -  by @​sheremet-va (756ac)
  • Dedupe @​vitest/browser/client  -  by @​sheremet-va in vitest-dev/vitest#6081 (ee725)
  • Don't release keyboard automatically  -  by @​sheremet-va in vitest-dev/vitest#6083 (58fac)
• ui:
  • Test files notified only when running  -  by @​userquin in vitest-dev/vitest#6069 (af7fe)
  • Encode html entities in task name  -  by @​userquin and @​sheremet-va in vitest-dev/vitest#6070 (7f0cc)
• web-worker:
  • Peer dependency version on vitest  -  by @​AriPerkkio in vitest-dev/vitest#6060 (95a2d)

   🏎 Performance

• browser: Don't import msw if no modules are mocked  -  by @​sheremet-va in vitest-dev/vitest#6073 (aa527)

    View changes on GitHub

v2.0.1

   🐞 Bug Fixes

• browser: Correctly inherit browser config in a workspace  -  by @​sheremet-va in vitest-dev/vitest#6054 (4b03e)
• ui: Move virtual scroller to dev dependencies  -  by @​userquin in vitest-dev/vitest#6053 (f94ed)
• vitest: Print only running files, not every file  -  by @​sheremet-va in vitest-dev/vitest#6052 (4d559)

    View changes on GitHub

v2.0.0

Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

🚨 Breaking Changes

• Simplify mock function generic types and align with jest - by @​hi-ogawa in vitest-dev/vitest#4784 (a0c1d37)
• Remove --segfault-retry - by @​sheremet-va in vitest-dev/vitest#5514 (ed60e)
  • This flag was introduced to combat threads segfaults. Our current recommendation is to use the new default forks pool instead.
• Run suite hooks in a stack - by @​sheremet-va in vitest-dev/vitest#5609 (1277d)
  • This feels like a more sensible default. Especially with the new onTestFinished hook. This can make your tests run a little bit slower.
• Enable coverage.ignoreEmptyLines by default - by @​AriPerkkio in vitest-dev/vitest#5543 (31994)
  • ⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See vitest-dev/vitest#5423 for more details.
• Add correct location and snapshot fields in json reporter - by @​sheremet-va in vitest-dev/vitest#5434 (bcccc)
  • Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
• Update dependency chai to v5 - by renovate[bot] and @​sheremet-va in vitest-dev/vitest#5135 (73646)
• Remove watchExclude - by @​patak-dev in vitest-dev/vitest#5177 (d7371)
• Change default pool to 'forks' - by @​AriPerkkio in vitest-dev/vitest#5047 (7f8f9)
  • This change is done for compatibility issues
  • This pool may be slightly slower than previous threads pool: https://vitest.dev/guide/improving-performance.html#pool

... (truncated)

Commits

• 99a12ae chore: release v2.0.2
• 80a43d5 fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...
• 7012f8c docs: add env documentation (#6063)
• 16eb6c8 chore: release v2.0.1
• 4b03e72 fix(browser): correctly inherit browser config in a workspace (#6054)
• 4d5597d fix(vitest): print only running files, not every file (#6052)
• 1b150a3 chore: release v2.0.0
• 5131992 docs: default pool in the types of 2.0 config (#6043)
• 5611895 chore: release v2.0.0-beta.13
• 8f65ae9 fix: transpile esnext to node18 to support newest JS and TS features (#4409)
• Additional commits viewable in compare view

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 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)

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: d73f09d1e78d9ddb93052eab74e4baf04c9a1140

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai[bot]]

[!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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[dependabot[bot]]

Superseded by #884.