Describe the bug
Latest vitest 4.1.0 beta includes a update to peerDependecies done in #9587, in which it was changed from ^6.0.0 || ^7.0.0-0 to ^6.0.0 || ^7.0.0 || ^8.0.0-0.
However, vitest also pulls in an internal package @vitest/mocker (directly and indirectly via @vitest/browser-playwright), in which vite peerDependency is still set to ^6.0.0 || ^7.0.0-0, causing warnings in package managers when Vite 8 is used.
Reproduction
n/a
System Info
System:
OS: macOS 26.3
CPU: (10) arm64 Apple M1 Max
Memory: 834.45 MB / 64.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.11.1 - /usr/local/bin/node
Yarn: 4.10.3 - /Users/wojciech.maj/.yarn/switch/bin/yarn
npm: 11.6.2 - /usr/local/bin/npm
Browsers:
Chrome: 144.0.7559.134
Firefox: 141.0.3
Safari: 26.3
Used Package Manager
yarn
Validations
Describe the bug
Latest vitest 4.1.0 beta includes a update to peerDependecies done in #9587, in which it was changed from
^6.0.0 || ^7.0.0-0to^6.0.0 || ^7.0.0 || ^8.0.0-0.However, vitest also pulls in an internal package @vitest/mocker (directly and indirectly via @vitest/browser-playwright), in which vite peerDependency is still set to
^6.0.0 || ^7.0.0-0, causing warnings in package managers when Vite 8 is used.Reproduction
n/a
System Info
System: OS: macOS 26.3 CPU: (10) arm64 Apple M1 Max Memory: 834.45 MB / 64.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 24.11.1 - /usr/local/bin/node Yarn: 4.10.3 - /Users/wojciech.maj/.yarn/switch/bin/yarn npm: 11.6.2 - /usr/local/bin/npm Browsers: Chrome: 144.0.7559.134 Firefox: 141.0.3 Safari: 26.3Used Package Manager
yarn
Validations