chore(deps-dev): bump vitest and @vitest/coverage-istanbul

[dependabot]

Bumps vitest and @vitest/coverage-istanbul. These dependencies needed to be updated together.
Updates vitest from 2.0.5 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

• browser:
  • Make example test callbacks async  -  by @​aqandrew in vitest-dev/vitest#6484 (16aa7)
  • Optimize vitest-browser-vue correctly  -  by @​sheremet-va in vitest-dev/vitest#6490 (5cbb0)
• workspace:
  • Resolve glob pattern once to avoid name collision  -  by @​sheremet-va in vitest-dev/vitest#6489 (36b5a)

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

• workspace:
  • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
  • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
  • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
  • This change doesn't affect non-glob usage.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in vitest-dev/vitest#6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in vitest-dev/vitest#6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in vitest-dev/vitest#6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in vitest-dev/vitest#6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in vitest-dev/vitest#6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in vitest-dev/vitest#6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in vitest-dev/vitest#6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in vitest-dev/vitest#6434 (7ab0f)

... (truncated)

Commits

• 699055e chore: release v2.1.1
• 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
• 16aa76c fix(browser): make example test callbacks async (#6484)
• 9f1fd18 chore: release v2.1.0
• 94a186e fix(ui): render project name consistently (#6329)
• ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
• b2be23e chore: release v2.1.0-beta.7
• 0b44722 fix: ignore importer when resolving Vitest (#6469)
• 97773e2 chore: fix edge case in license files bundling (#6460)
• 7ab0f4a feat(browser): support --inspect-brk (#6434)
• Additional commits viewable in compare view

Updates @vitest/coverage-istanbul from 2.0.5 to 2.1.1

Release notes

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

v2.1.1

   🐞 Bug Fixes

• browser:
  • Make example test callbacks async  -  by @​aqandrew in vitest-dev/vitest#6484 (16aa7)
  • Optimize vitest-browser-vue correctly  -  by @​sheremet-va in vitest-dev/vitest#6490 (5cbb0)
• workspace:
  • Resolve glob pattern once to avoid name collision  -  by @​sheremet-va in vitest-dev/vitest#6489 (36b5a)

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

• workspace:
  • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
  • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
  • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
  • This change doesn't affect non-glob usage.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in vitest-dev/vitest#6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in vitest-dev/vitest#6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in vitest-dev/vitest#6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in vitest-dev/vitest#6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in vitest-dev/vitest#6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in vitest-dev/vitest#6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in vitest-dev/vitest#6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in vitest-dev/vitest#6434 (7ab0f)

... (truncated)

Commits

• 699055e chore: release v2.1.1
• 9f1fd18 chore: release v2.1.0
• b2be23e chore: release v2.1.0-beta.7
• 8ac7011 chore: release v2.1.0-beta.6
• da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
• 5932a7f feat(coverage): add --exclude-after-remap (#6309)
• 34199bd feat(browser): support v8 coverage (#6273)
• 72056b5 chore: release v2.1.0-beta.5
• e662c7b fix(coverage): warn if vitest and @vitest/* versions don't match (#6317)
• 67b086b chore: release v2.1.0-beta.4
• 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 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)

[coveralls]

Pull Request Test Coverage Report for Build 10857395967

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 45.379%

---

Totals
Change from base Build 10792560241:	0.0%
Covered Lines:	253
Relevant Lines:	507

---

💛 - Coveralls

[dependabot]

Looks like these dependencies are up-to-date now, so this is no longer needed.