gustavoguichard / string-ts

Strongly typed string functions
MIT License
1.2k stars 17 forks source link

chore(deps-dev): bump @vitest/coverage-v8 from 2.0.3 to 2.1.1 #246

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 2 months ago

Bumps @vitest/coverage-v8 from 2.0.3 to 2.1.1.

Release notes

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

v2.1.1

   🐞 Bug Fixes

    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

... (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
  • 91dea8c fix(coverage): v8 to warn instead of crash when conversion fails (#6318)
  • 1f6cb59 fix(coverage): v8 to support source maps with multiple sources (#6120)
  • Additional commits viewable in compare view


Dependabot compatibility score

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)
dependabot[bot] commented 1 month ago

Superseded by #252.