Bump the npm group with 2 updates

[dependabot]

Bumps the npm group with 2 updates: @vitest/coverage-v8 and vitest.

Updates @vitest/coverage-v8 from 1.6.0 to 2.0.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

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
• --merge-reports to support coverage - by @​AriPerkkio in vitest-dev/vitest#5736 (b7438)
• Add promise-based return assertions, do not auto-resolve returned promises - by @​sheremet-va in vitest-dev/vitest#5749 (5f710)
  • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
• Do not exit process if global setup has failed - by @​sheremet-va in vitest-dev/vitest#5726 (ddb09)
• Don't exit process if config failed - by @​sheremet-va in vitest-dev/vitest#5715 (f232f)
• Add meta to json output - by @​sheremet-va in vitest-dev/vitest#5802 (dd754)
• Rename indexScripts to orchestratorScripts in the browser config - by @​sheremet-va in vitest-dev/vitest#5842 (49f34)
• Add "vitest list" API to print collected tests without running them - by @​sheremet-va in vitest-dev/vitest#6013 (583dd)
  • ⚠️ This changes the custom pool API - now requires collectTests method alongside runTests.
• Remove the empty suite from the runner - by @​sheremet-va in vitest-dev/vitest#5435 (dbbbe)
• Support concurrent suites - by @​hi-ogawa in vitest-dev/vitest#5491 (222ce44)
• Support overriding exclude in coverage - by @​AriPerkkio in vitest-dev/vitest#5997 (169bc)
  • ⚠️ Vitest coverage no longer adds test files to exclude patterns if coverage.exclude was overridden in the config. Add your test patterns manually, or merge your overrides with default ones: ['**/my-pattern.js', ...coverageConfigDefaults.exclude].

🚀 Features

• browser:
  • 🌐 This release lays the groundwork for the next iteration of Vitest Browser Mode. You can read more about our future plans at Vitest Browser Mode vitest-dev/vitest#5828
  • Add commands to communicate betweens server and the browser - by @​sheremet-va in vitest-dev/vitest#5097 (aa431)
  • Do not reload the page during watch mode - by @​sheremet-va in vitest-dev/vitest#5810 (e5b9a)

... (truncated)

Commits

• 16eb6c8 chore: release v2.0.1
• 1b150a3 chore: release v2.0.0
• 5611895 chore: release v2.0.0-beta.13
• 368c137 fix(coverage): remove work-around for implicit else (#6014)
• 05d5f38 chore(deps): update all non-major dependencies (#5957)
• 169bc1f fix(coverage): support overriding exclude (#5997)
• cd9cc6b chore: release v2.0.0-beta.12
• fca8b92 chore(deps): update v8-to-istanbul (#5958)
• 7080513 fix(coverage): pass thresholds errors to stderr of startVitest() (#5954)
• 3fd15ba chore: release v2.0.0-beta.11
• Additional commits viewable in compare view

Updates vitest from 1.6.0 to 2.0.1

Release notes

Sourced from vitest's releases.

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
• --merge-reports to support coverage - by @​AriPerkkio in vitest-dev/vitest#5736 (b7438)
• Add promise-based return assertions, do not auto-resolve returned promises - by @​sheremet-va in vitest-dev/vitest#5749 (5f710)
  • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
• Do not exit process if global setup has failed - by @​sheremet-va in vitest-dev/vitest#5726 (ddb09)
• Don't exit process if config failed - by @​sheremet-va in vitest-dev/vitest#5715 (f232f)
• Add meta to json output - by @​sheremet-va in vitest-dev/vitest#5802 (dd754)
• Rename indexScripts to orchestratorScripts in the browser config - by @​sheremet-va in vitest-dev/vitest#5842 (49f34)
• Add "vitest list" API to print collected tests without running them - by @​sheremet-va in vitest-dev/vitest#6013 (583dd)
  • ⚠️ This changes the custom pool API - now requires collectTests method alongside runTests.
• Remove the empty suite from the runner - by @​sheremet-va in vitest-dev/vitest#5435 (dbbbe)
• Support concurrent suites - by @​hi-ogawa in vitest-dev/vitest#5491 (222ce44)
• Support overriding exclude in coverage - by @​AriPerkkio in vitest-dev/vitest#5997 (169bc)
  • ⚠️ Vitest coverage no longer adds test files to exclude patterns if coverage.exclude was overridden in the config. Add your test patterns manually, or merge your overrides with default ones: ['**/my-pattern.js', ...coverageConfigDefaults.exclude].

🚀 Features

• browser:
  • 🌐 This release lays the groundwork for the next iteration of Vitest Browser Mode. You can read more about our future plans at Vitest Browser Mode vitest-dev/vitest#5828
  • Add commands to communicate betweens server and the browser - by @​sheremet-va in vitest-dev/vitest#5097 (aa431)
  • Do not reload the page during watch mode - by @​sheremet-va in vitest-dev/vitest#5810 (e5b9a)

... (truncated)

Commits

• 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)
• 583dd8a feat(vitest)!: add "vitest list" API to print collected tests without running...
• f645e48 feat: expose parseAst, parseAstAsync from vite
• 91ba6f9 fix(vitest): show all failed tests when rerunning a test (#6022)
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[TheJaredWilcurt]

@dependabot recreate

[dependabot]

Looks like these dependencies are no longer updatable, so this is no longer needed.