Bump @vitest/browser-playwright from 4.1.7 to 4.1.8

[dependabot]

Bumps @vitest/browser-playwright from 4.1.7 to 4.1.8.

Release notes

Sourced from @​vitest/browser-playwright's releases.

v4.1.8

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple ids [backport to v4]  -  by @​toxik and @​Zelys-DFKH in vitest-dev/vitest#10474 (675b4)

    View changes on GitHub

Commits

• e61f2dd chore: release v4.1.8
• 675b434 fix(browser): remove orphaned Playwright route when same module is mocked via...
• e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
• See full diff 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 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)

[greptile-apps]

Greptile Summary

This is a Dependabot-generated patch bump of @vitest/browser-playwright from 4.1.7 to 4.1.8, picking up two browser-mode bug fixes (orphaned Playwright route cleanup and CDP API gating). The cascading lock-file update also pulls in @vitest/browser@4.1.8, @vitest/mocker@4.1.8, several other @vitest/*@4.1.8 sub-packages, and ws@8.21.0.

• package.json: single version bump for @vitest/browser-playwright; vitest itself is left at 4.1.7, creating a peer dependency mismatch with the new 4.1.8 packages.
• pnpm-lock.yaml: lock file regenerated to reflect the cascading updates; pnpm resolves the mismatched peer but the mismatch will produce warnings and could hide compatibility issues at the vitest-core / browser-adapter boundary.

Confidence Score: 4/5

Safe to merge with one caveat: vitest itself should also be bumped to 4.1.8 to stay in sync with the newly installed browser packages.

The @vitest/browser-playwright@4.1.8 and its pulled-in companions (@vitest/browser, @vitest/mocker, etc.) all declare vitest: 4.1.8 as a peer dependency, but the project's vitest remains at 4.1.7. pnpm resolves it anyway, but the mismatch means the browser adapter and the vitest core are at different patch levels — these packages are co-released precisely because they must stay in sync, and running them at different versions can expose subtle behavioural gaps.

package.json — vitest and any other @vitest/* packages still pinned at 4.1.7 should be bumped to 4.1.8 to match the updated browser-playwright packages.

Important Files Changed

Filename	Overview
package.json	Bumps @vitest/browser-playwright from 4.1.7 to 4.1.8; the new version declares vitest@4.1.8 as a peer dependency but the project still pins vitest@4.1.7.
pnpm-lock.yaml	Lock file updated to reflect the version bump; cascading updates pull in @vitest/browser@4.1.8, @vitest/mocker@4.1.8, @vitest/utils@4.1.8, @vitest/spy@4.1.8, and ws@8.21.0, but vitest itself remains at 4.1.7.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["vitest@4.1.7\n(unchanged)"] -->|"peer dep\n⚠️ expects 4.1.8"| B["@vitest/browser-playwright@4.1.8\n(bumped)"]
    B --> C["@vitest/browser@4.1.8"]
    C --> D["@vitest/mocker@4.1.8"]
    C --> E["@vitest/utils@4.1.8"]
    D --> F["@vitest/spy@4.1.8"]
    C --> G["ws@8.21.0\n(was 8.20.0)"]
    E --> H["@vitest/pretty-format@4.1.8"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["vitest@4.1.7\n(unchanged)"] -->|"peer dep\n⚠️ expects 4.1.8"| B["@vitest/browser-playwright@4.1.8\n(bumped)"]
    B --> C["@vitest/browser@4.1.8"]
    C --> D["@vitest/mocker@4.1.8"]
    C --> E["@vitest/utils@4.1.8"]
    D --> F["@vitest/spy@4.1.8"]
    C --> G["ws@8.21.0\n(was 8.20.0)"]
    E --> H["@vitest/pretty-format@4.1.8"]

Loading

_{Reviews (1): Last reviewed commit: "Bump @vitest/browser-playwright from 4.1..." | Re-trigger Greptile}

[greptile-apps]

Peer dependency mismatch: vitest still at 4.1.7

@vitest/browser-playwright@4.1.8 (and the transitively pulled @vitest/browser@4.1.8) now declare vitest: 4.1.8 as a peer dependency, but vitest remains pinned at 4.1.7 in this project. The lock file resolves it anyway, but pnpm will emit an unsatisfied-peer-dependency warning and the two packages were authored and released together — running a 4.1.8 browser adapter against a 4.1.7 core can expose subtle behavioural mismatches at the boundary. The safe fix is to also bump vitest (and any other @vitest/* packages pinned at 4.1.7) to 4.1.8.