Bump vitest from 1.6.0 to 2.0.5

[dependabot[bot]]

Bumps vitest from 1.6.0 to 2.0.5.

Release notes

Sourced from vitest's releases.

v2.0.5

   🚀 Features

• Introduce experimental reported tasks  -  by @​sheremet-va in vitest-dev/vitest#6149 (13d85)
  • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

   🐞 Bug Fixes

• Show a difference between string characters if both values are strings  -  by @​sheremet-va in vitest-dev/vitest#6191 (29176)
• testNamePattern adds leading space  -  by @​AriPerkkio in vitest-dev/vitest#6186 (073a5)
• browser:
  • Don't bundle afterEach cleanup hooks in node entrypoint  -  by @​sheremet-va in vitest-dev/vitest#6192 (e6fbc)
  • UserEvent.setup initiates a separate state for userEvent instance  -  by @​sheremet-va in vitest-dev/vitest#6088 (883f3)
  • Correctly import optimized module in vi.importActual  -  by @​sheremet-va in vitest-dev/vitest#6219 (804ff)
  • Passing options to hover/unhover  -  by @​MNeverOff in vitest-dev/vitest#6175 (d4c00)
  • Improve unique CSS selector generation  -  by @​zacharyvoase and Zack Voase in vitest-dev/vitest#6243 (e7acd)
• vitest:
  • Remove nuxt from auto inline deps  -  by @​sheremet-va (93882)
  • Improve defineProject and defineWorkspace types  -  by @​sheremet-va in vitest-dev/vitest#6198 (8cd82)
  • Correctly resolve mocked node:* imports in __mocks__ folder  -  by @​sheremet-va in vitest-dev/vitest#6204 (a48be)
• web-worker:
  • Expose globals on self  -  by @​sheremet-va in vitest-dev/vitest#6170 (12bb5)

    View changes on GitHub

v2.0.4

   🐞 Bug Fixes

• One-line environment options  -  by @​hahanein in vitest-dev/vitest#5105 (38269)
• Resolve assets imported with require  -  by @​sheremet-va in vitest-dev/vitest#6159 (807a2)
• browser:
  • Don't panic if @​vitest/browser is installed outside of project root  -  by @​sheremet-va in vitest-dev/vitest#6135 (ccfcd)
  • Set global filepath  -  by @​sheremet-va in vitest-dev/vitest#6190 (0d0b4)
  • Allow preview and open in the editor screenshot error from ui  -  by @​userquin in vitest-dev/vitest#6113 (2d620)
• coverage:
  • Global thresholds to include files from glob thresholds  -  by @​thor-juhasz and @​AriPerkkio in vitest-dev/vitest#6172 (02e3f)
  • Consistent type-only file handling  -  by @​AriPerkkio in vitest-dev/vitest#6183 (90576)
  • Ignore *.cts files  -  by @​AriPerkkio in vitest-dev/vitest#6189 (5da45)
  • Add thresholds.<glob>.100 option  -  by @​thor-juhasz and @​AriPerkkio in vitest-dev/vitest#6174 (f6845)
• spy:
  • Fix mockImplementation for function overload and unions  -  by @​hi-ogawa in vitest-dev/vitest#6181 (7a75b)

    View changes on GitHub

v2.0.3

   🚀 Features

• ui: Show all suites/tests when parent matches  -  by @​userquin in vitest-dev/vitest#6106 (840e0)

   🐞 Bug Fixes

... (truncated)

Commits

• 99452a7 chore: release v2.0.5
• 9b9bdf7 chore: remove unnecessary await (#6249)
• 40dfad8 docs: add reported tasks docs (#6245)
• 13d85bd feat: introduce experimental reported tasks (#6149)
• b76a927 refactor(vitest): move public exports to public folder (#6218)
• 56dbfa6 refactor: make a distinction between node and runtime types (#6214)
• a48be6f fix(vitest): correctly resolve mocked node:* imports in mocks folder (#6204)
• 3aab8a1 refactor: deprecate all config types from the main Vitest entrypoint, introdu...
• 57d23ce docs: fix inconsistencies, remove low informative twoslash examples (#6200)
• 8cd8272 fix(vitest): improve defineProject and defineWorkspace types (#6198)
• 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: fd0d10e033de388b6de53e0b31c80ed33ac7e8d3

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.