vite-plus 0.1.24 → 0.2.0

package/docs/guide/upgrade.md

@@ -14,8 +14,10 @@ You can upgrade both of them independently.
 ## Global `vp`
 
 ```bash
-vp upgrade              # upgrade to the latest version
-vp upgrade --check      # check for updates without installing
+vp upgrade                        # upgrade to the latest version
+vp upgrade --check                # check for updates without installing
+vp upgrade <version>              # install a specific version
+vp upgrade --registry <registry>  # use a custom npm registry
 ```
 
 ### Rollback
@@ -40,21 +42,38 @@ You can also use `vp add vite-plus@latest` if you want to move the dependency ex
 
 ### Updating Aliased Packages
 
-Vite+ sets up npm aliases for its core packages during installation:
+Vite+ sets up an npm alias for its core package during installation:
 
 - `vite` is aliased to `npm:@voidzero-dev/vite-plus-core@latest`
-- `vitest` is aliased to `npm:@voidzero-dev/vite-plus-test@latest`
 
-`vp update vite-plus` does not re-resolve these aliases in the lockfile. To fully upgrade, update them separately:
+`vp update vite-plus` does not re-resolve this alias in the lockfile. To fully upgrade, update it separately:
 
 ```bash
-vp update @voidzero-dev/vite-plus-core @voidzero-dev/vite-plus-test
+vp update @voidzero-dev/vite-plus-core
 ```
 
 Or update everything at once:
 
 ```bash
-vp update vite-plus @voidzero-dev/vite-plus-core @voidzero-dev/vite-plus-test
+vp update vite-plus @voidzero-dev/vite-plus-core
 ```
 
 You can verify with `vp outdated` that no Vite+ packages remain outdated.
+
+### Updating the Vitest Pin
+
+If you migrated with `vp migrate`, your project pins `vitest` to an exact version so the whole project shares a single Vitest copy with the bundled `vp test` runner. The pin lives in your package manager's override block:
+
+- **npm / Bun:** a `vitest` entry under `overrides` in `package.json`
+- **Yarn:** a `vitest` entry under `resolutions` in `package.json`
+- **pnpm:** a `vitest` entry under `overrides` in `pnpm-workspace.yaml` — unless your `package.json` already had a `pnpm` field, in which case it lives under `pnpm.overrides` in `package.json` instead (pnpm ignores `pnpm-workspace.yaml` overrides when `package.json` defines `pnpm.overrides`)
+
+A Vite+ release can bump the bundled Vitest. Because that pin also applies to `vite-plus`'s own `vitest` dependency, an out-of-date pin keeps installing the previous runner even after you upgrade `vite-plus` — splitting Vitest's internals (mocks, `expect`, runner state) between the pinned copy and the one `vp test` loads.
+
+After upgrading `vite-plus`, re-pin `vitest` to the version Vite+ now bundles. Check that version with:
+
+```bash
+vp --version
+```
+
+Then set the `vitest` override to that exact version, or rerun `vp migrate` to update the pin for you.

package/docs/package.json

@@ -17,13 +17,13 @@
     "vitepress-plugin-llms": "^1.12.2",
     "vitepress-plugin-mermaid": "^2.0.17",
     "vue": "^3.5.27",
-    "vue3-carousel": "^0.16.0"
+    "vue3-carousel": "^0.17.0"
   },
   "devDependencies": {
-    "@voidzero-dev/vitepress-theme": "4.8.3",
+    "@voidzero-dev/vitepress-theme": "4.8.4",
     "oxc-minify": "^0.120.0",
     "tailwindcss": "^4.1.18",
-    "vitepress": "2.0.0-alpha.15"
+    "vitepress": "2.0.0-alpha.17"
   },
   "packageManager": "pnpm@10.33.2"
 }