feat(deps): upgrade upstream dependencies

README.md

@@ -209,7 +209,7 @@ Add package-manager overrides so that other packages use the Vite+ versions. Ali
 ```json
 "overrides": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 
@@ -218,15 +218,15 @@ If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
 ```yaml
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 5.0.1
+  vitest: 5.0.2
 ```
 
 Or, if you are using Yarn:
 
 ```json
 "resolutions": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/migration_from_vitest_config/snapshots/migration_from_vitest_config.md

@@ -112,7 +112,7 @@ allowBuilds:
 overrides:
   vite@*: 'catalog:'
   vitest@*: 'catalog:'
-  '@vitest/browser@*': 5.0.1
+  '@vitest/browser@*': 5.0.2
 peerDependencyRules:
   allowAny:
     - vite

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/migration_upgrade_browser_webdriverio_pnpm/snapshots/migration_upgrade_browser_webdriverio_pnpm.md

@@ -74,7 +74,7 @@ catalog:
 overrides:
   vite@*: 'catalog:'
   vitest@*: 'catalog:'
-  '@vitest/browser@*': 5.0.1
+  '@vitest/browser@*': 5.0.2
 peerDependencyRules:
   allowAny:
     - vite

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/migration_upgrade_browser_webdriverio_pnpm/snapshots/upgrade_community_provider_catalog.md

@@ -69,7 +69,7 @@ catalogs:
 overrides:
   vite@*: 'catalog:'
   vitest@*: 'catalog:'
-  '@vitest/browser@*': 5.0.1
+  '@vitest/browser@*': 5.0.2
 allowBuilds:
   edgedriver: true
   geckodriver: true

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_browser_types/package.json

@@ -5,7 +5,7 @@
   "packageManager": "pnpm@11.24.0",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/browser-playwright": "5.0.1",
+    "@vitest/browser-playwright": "5.0.2",
     "playwright": "1.57.0",
     "typescript": "7.0.2"
   }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_coverage/package.json

@@ -4,7 +4,7 @@
   "type": "module",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/coverage-v8": "5.0.1",
-    "@vitest/coverage-istanbul": "5.0.1"
+    "@vitest/coverage-v8": "5.0.2",
+    "@vitest/coverage-istanbul": "5.0.2"
   }
 }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/package.json

@@ -2,5 +2,5 @@
   "name": "test-v5-install-managers",
   "private": true,
   "type": "module",
-  "devDependencies": { "vite-plus": "latest", "vitest": "5.0.1" }
+  "devDependencies": { "vite-plus": "latest", "vitest": "5.0.2" }
 }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/snapshots.toml

@@ -7,8 +7,8 @@ steps = [
   { argv = ["vpt", "json-edit", "package.json", "packageManager", "npm@10.9.4"], snapshot = false },
   # Match the bundled runner throughout npm's peer graph. Otherwise newer
   # Vitest patches reached through optional peers can crash npm 10's resolver.
-  { argv = ["vpt", "json-edit", "package.json", "overrides.vitest", "5.0.1"], snapshot = false },
-  { argv = ["vpt", "json-edit", "package.json", "overrides.@vitest/browser", "5.0.1"], snapshot = false },
+  { argv = ["vpt", "json-edit", "package.json", "overrides.vitest", "5.0.2"], snapshot = false },
+  { argv = ["vpt", "json-edit", "package.json", "overrides.@vitest/browser", "5.0.2"], snapshot = false },
   { argv = ["vp", "install", "--ignore-scripts", "--", "--no-audit", "--no-fund"], snapshot = false, timeout = 180000 },
   ["vp", "test", "run"],
 ]

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/snapshots/npm_install_and_runtime.md

@@ -3,10 +3,10 @@
 ## `vpt json-edit package.json packageManager npm@10.9.4`
 
 
-## `vpt json-edit package.json overrides.vitest 5.0.1`
+## `vpt json-edit package.json overrides.vitest 5.0.2`
 
 
-## `vpt json-edit package.json overrides.@vitest/browser 5.0.1`
+## `vpt json-edit package.json overrides.@vitest/browser 5.0.2`
 
 
 ## `vp install --ignore-scripts -- --no-audit --no-fund`

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_optional_packages/package.json

@@ -4,7 +4,7 @@
   "type": "module",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/ui": "5.0.1",
+    "@vitest/ui": "5.0.2",
     "jsdom": "27.2.0",
     "happy-dom": "20.0.10",
     "temporal-polyfill": "1.0.4"

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_preview/snapshots.toml

@@ -8,7 +8,7 @@ steps = [{ argv = ["node", "verify.mjs"], timeout = 120000 }]
 name = "upstream_real_timers"
 vp = "local"
 env = { PLAYWRIGHT_BROWSERS_PATH = "0" }
-comment = "Known upstream regression introduced in Vitest 4.1.1 and still present in 5.0.1, not a new v5 release blocker: Preview locator clicks advance fake timers while using real timers. Require success when upstream fixes it."
+comment = "Known upstream regression introduced in Vitest 4.1.1 and still present in 5.0.2, not a new v5 release blocker: Preview locator clicks advance fake timers while using real timers. Require success when upstream fixes it."
 steps = [{ argv = ["node", "verify.mjs", "--real-timers"], timeout = 120000 }]
 
 [[case]]

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_preview/snapshots/upstream_real_timers.md

@@ -1,12 +1,12 @@
 # upstream_real_timers
 
-Known upstream regression introduced in Vitest 4.1.1 and still present in 5.0.1, not a new v5 release blocker: Preview locator clicks advance fake timers while using real timers. Require success when upstream fixes it.
+Known upstream regression introduced in Vitest 4.1.1 and still present in 5.0.2, not a new v5 release blocker: Preview locator clicks advance fake timers while using real timers. Require success when upstream fixes it.
 
 ## `node verify.mjs --real-timers`
 
 ```
 Plugin "vitest:mocks:interceptor" defines Vite-specific hooks (configureServer) in a plugin returned from applyToEnvironment. These hooks will be ignored.
 Browser runner started at http://localhost:<port>/__vitest_test__/?sessionId=<uuid>
 
-Known upstream regression since Vitest 4.1.1: Preview locator clicks fail with real timers in 5.0.1
+Known upstream regression since Vitest 4.1.1: Preview locator clicks fail with real timers in 5.0.2
 ```

docs/guide/local-cli.md

@@ -52,20 +52,20 @@ You need to add overrides to your package manager so that other packages resolve
 ```yaml [pnpm-workspace.yaml]
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 5.0.1
+  vitest: 5.0.2
 ```
 
 ```json [npm / Bun package.json]
 "overrides": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 
 ```json [Yarn package.json]
 "resolutions": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 

docs/guide/migrate.md

@@ -151,7 +151,7 @@ View and copy this prompt into your coding agent to upgrade an existing Vite+ 0.
 
 ### Vitest
 
-Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.1` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
+Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.2` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
 
 For browser mode, you can use the base browser runtime (`@vitest/browser`) and Preview provider (`@vitest/browser-preview`) included in `vite-plus`. To use Playwright or WebDriverIO, you also need the opt-in provider (`@vitest/browser-playwright` or `@vitest/browser-webdriverio`) and its framework peer (`playwright` or `webdriverio`).
 

docs/guide/test.md

@@ -2,7 +2,7 @@
 
 `vp test` runs tests with [Vitest](https://vitest.dev).
 
-The bundled runner uses Vitest `5.0.1` and requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
+The bundled runner uses Vitest `5.0.2` and requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
 
 ## Overview
 

docs/guide/vitest-v5.md

@@ -1,6 +1,6 @@
 # Upgrade to Vitest 5
 
-Vite+ bundles Vitest `5.0.1`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
+Vite+ bundles Vitest `5.0.2`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
 
 ## Before you migrate
 
@@ -126,7 +126,7 @@ Review calls with benchmark options, imported or reassigned callbacks, callback
 
 ## Entry points and packages
 
-Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.1`. Keep `@vitest/web-worker` aligned when your project uses it.
+Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.2`. Keep `@vitest/web-worker` aligned when your project uses it.
 
 | v4 import                                | v5 import or action                                                         |
 | ---------------------------------------- | --------------------------------------------------------------------------- |
@@ -188,7 +188,7 @@ Use the file locations in the migration report to review these changes. Run brow
 
 For jest-dom matcher types, load `@testing-library/jest-dom/vitest` in `compilerOptions.types` or import it from a TypeScript setup file that your `tsconfig.json` includes. The root `@testing-library/jest-dom` type entry augments Jest. A JavaScript setup file excluded by `allowJs: false` does not load the Vitest augmentation for type checking. Review shared Jest/Vitest configs before changing their type entries.
 
-With `vitest@5.0.1`, loading browser declarations first can also make TypeScript reject valid Node jest-dom assertions: `toHaveTextContent(/pattern/)` and CSS custom properties in `toHaveStyle()`. We reproduced this conflict with upstream imports and with Vite+ imports. Both `@testing-library/jest-dom@6.9.1` and `7.0.1` reproduce it. Check the declarations loaded by each test `tsconfig.json`; adding the jest-dom type entry alone might not resolve the conflict. Keep the affected project on the v4-based release until its Node and browser matcher types pass separate checks.
+With `vitest@5.0.2`, loading browser declarations first can also make TypeScript reject valid Node jest-dom assertions: `toHaveTextContent(/pattern/)` and CSS custom properties in `toHaveStyle()`. We reproduced this conflict with upstream imports and with Vite+ imports. Both `@testing-library/jest-dom@6.9.1` and `7.0.1` reproduce it. Check the declarations loaded by each test `tsconfig.json`; adding the jest-dom type entry alone might not resolve the conflict. Keep the affected project on the v4-based release until its Node and browser matcher types pass separate checks.
 
 | Area                  | Required review                                                                                                                                                                            |
 | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

packages/cli/README.md

@@ -203,7 +203,7 @@ Add package-manager overrides so that other packages use the Vite+ versions. Ali
 ```json
 "overrides": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 
@@ -212,15 +212,15 @@ If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
 ```yaml
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 5.0.1
+  vitest: 5.0.2
 ```
 
 Or, if you are using Yarn:
 
 ```json
 "resolutions": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "5.0.1"
+  "vitest": "5.0.2"
 }
 ```
 

packages/cli/src/utils/constants.ts

@@ -15,7 +15,7 @@ export const VITE_CONFIG_FILES = [
   'vite.config.cts',
 ] as const;
 
-export const VITEST_VERSION = '5.0.1';
+export const VITEST_VERSION = '5.0.2';
 
 // Exact action release used by generated workflows and the @v1 migration.
 // The Renovate custom manager keeps this value current.