chore(deps): 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)