Describe the bug
When setting up vitest browser mode with vp (specifically with playwright, I haven't tried other providers), the migration script change the import to import { playwright } from "vite-plus/test/browser-playwright"; and removed the relevant vitest dependencies including @vitest/browser-playwright. However, in this case, playwright is no longer included as a peer dependency and so it is missing from the resolved dependency tree.
I can get past this by manually installing playwright as a dependency but I'll get a warning as below:
Loaded vitest@0.1.14 and @vitest/browser@4.1.1 .
Running mixed versions is not supported and may lead into bugs
Update your dependencies and make sure the versions match.
It seems to be an oversight or there needs to be some clearer documentation around how the dependency should be handled here.
Reproduction
n/a
Steps to reproduce
No response
System Info
VITE+ - The Unified Toolchain for the Web
Environment:
Version 24.14.1
Source lts
Tool Paths:
node /home/limzykenneth/.vite-plus/js_runtime/node/24.14.1/bin/node
npm /home/limzykenneth/.vite-plus/js_runtime/node/24.14.1/bin/npm
npx /home/limzykenneth/.vite-plus/js_runtime/node/24.14.1/bin/npx
VITE+ - The Unified Toolchain for the Web
vp v0.1.14
Local vite-plus:
vite-plus v0.1.14
Tools:
vite v8.0.2
rolldown v1.0.0-rc.11
vitest v4.1.1
oxfmt v0.42.0
oxlint v1.57.0
oxlint-tsgolint v0.17.3
tsdown v0.21.4
Environment:
Package manager npm v11.12.1
Node.js v24.14.1
Used Package Manager
npm
Logs
Validations
Describe the bug
When setting up vitest browser mode with vp (specifically with playwright, I haven't tried other providers), the migration script change the import to
import { playwright } from "vite-plus/test/browser-playwright";and removed the relevant vitest dependencies including@vitest/browser-playwright. However, in this case, playwright is no longer included as a peer dependency and so it is missing from the resolved dependency tree.I can get past this by manually installing playwright as a dependency but I'll get a warning as below:
It seems to be an oversight or there needs to be some clearer documentation around how the dependency should be handled here.
Reproduction
n/a
Steps to reproduce
No response
System Info
Used Package Manager
npm
Logs
Validations