chore(deps-dev): bump vitest and vitest-browser-svelte#2288
chore(deps-dev): bump vitest and vitest-browser-svelte#2288dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) and [vitest-browser-svelte](https://github.com/vitest-community/vitest-browser-svelte). These dependencies needed to be updated together. Updates `vitest` from 3.2.2 to 4.1.8 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.8/packages/vitest) Updates `vitest-browser-svelte` from 0.1.0 to 2.1.1 - [Release notes](https://github.com/vitest-community/vitest-browser-svelte/releases) - [Commits](vitest-community/vitest-browser-svelte@v0.1.0...v2.1.1) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.8 dependency-type: direct:development - dependency-name: vitest-browser-svelte dependency-version: 2.1.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 591c6ac2bc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "vitest": "^4.1.8", | ||
| "vitest-browser-svelte": "^2.1.1", |
There was a problem hiding this comment.
When VITEST_BROWSER=true, this repo's vite.config.ts still configures Browser Mode with provider: "playwright" and no @vitest/browser-playwright dependency; Vitest 4's browser provider rework requires importing playwright() from that package instead of using the old string provider. Because this bump removes the old @vitest/browser peer path without updating the config/dependencies, the opt-in Svelte browser component tests cannot start after installing these versions.
Useful? React with 👍 / 👎.
Bumps vitest and vitest-browser-svelte. These dependencies needed to be updated together.
Updates
vitestfrom 3.2.2 to 4.1.8Release notes
Sourced from vitest's releases.
... (truncated)
Commits
e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...a09d472chore: release v4.1.7a8fd24cchore: release v4.1.618af98cfix(browser): simplify orchestrator otel carrier (#10285)3188260feat(browser): provide project reference inToMatchScreenshotResolvePath(#...e399846chore: release v4.1.57dc6d54Revert "fix: respect diff config options in soft assertions (#8696)"9787dedfix: respect diff config options in soft assertions (#8696)325463afix(ast-collect): recognize _vi_import prefix in static test discovery (#10...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.
Updates
vitest-browser-sveltefrom 0.1.0 to 2.1.1Release notes
Sourced from vitest-browser-svelte's releases.
... (truncated)
Commits
092253bchore: release v2.1.1ff94b22fix: move@playwright/testout of dependencies (#26)c931ae6chore: release v2.1.03791c16feat: integrate trace mark with render (#24)53ed239chore: release v2.0.2a7d0576fix: inject testid for more stable locator query (#23)ea3a1dbfeat: use common testing library svelte core (#21)dc33f6bchore: release v2.0.129d38befix: update links to vitest-communityea54bc5chore: release v2.0.0Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for vitest-browser-svelte since your current version.
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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.