chore(deps-dev): bump vitest from 2.0.5 to 2.1.1 in /sdk
Bumps 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
@aqandrewin vitest-dev/vitest#6484 (16aa7)- Optimize vitest-browser-vue correctly - by
@sheremet-vain vitest-dev/vitest#6490 (5cbb0)- workspace:
- Resolve glob pattern once to avoid name collision - by
@sheremet-vain 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
pageobject from@vitest/browser/context.Potential Breaking Change
- workspace:
- Correctly resolve workspace globs and file paths - by
@sheremet-vain 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.tsorvite.config.tsinside the folder)- For example,
projects/*will match anything inside theprojectsfolder. 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-vain vitest-dev/vitest#6355 (874a1)- browser:
- Move page.config to server.config, add more docs - by
@sheremet-vain vitest-dev/vitest#6252 (af2b8)- Make iframe scalable, improve documentation - by
@sheremet-vain vitest-dev/vitest#6257 (74ca1)- Introduce built-in locators - by
@sheremet-vain vitest-dev/vitest#6084 (3347f)- Support v8 coverage - by
@AriPerkkioin vitest-dev/vitest#6273 (34199)- Support
userEvent.uploadin playwright provider - by@sheremet-vain vitest-dev/vitest#6442 (cf148)- Support
--inspect- by@AriPerkkioin vitest-dev/vitest#6433 (0499a)- Support
--inspect-brk- by@AriPerkkioin vitest-dev/vitest#6434 (7ab0f)
... (truncated)
Commits
699055echore: release v2.1.136b5acefix(workspace): resolve glob pattern once to avoid name collision (#6489)16aa76cfix(browser): make example test callbacks async (#6484)9f1fd18chore: release v2.1.094a186efix(ui): render project name consistently (#6329)ac698b1fix:expect.getState().testPathalways returns correct path (#6472)b2be23echore: release v2.1.0-beta.70b44722fix: ignore importer when resolving Vitest (#6469)97773e2chore: fix edge case in license files bundling (#6460)7ab0f4afeat(browser): support--inspect-brk(#6434)- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| bob | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Sep 18, 2024 8:59am |
⚠️ No Changeset found
Latest commit: d93ef78bc6a344aed7430f35e3e52496ecb8c27f
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.
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
A newer version of vitest exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.
@dependabot rebase
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!
If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.
@dependabot recreate
Superseded by #472.