vite-plus 0.2.9 → 0.3.0

package/dist/terminal-MKGAuy-p.js

@@ -0,0 +1,39 @@
+import { shouldPrintVitePlusHeader, vitePlusHeader } from "../binding/index.js";
+import { styleText } from "node:util";
+//#region src/utils/terminal.ts
+function log(message) {
+	console.log(message);
+}
+/**
+* Emit the Vite+ banner (header line + trailing blank line) to stdout.
+* Gating (non-TTY, git hooks) lives in `shouldPrintVitePlusHeader` on the
+* Rust side so both CLIs stay in sync.
+*/
+function printHeader() {
+	if (!shouldPrintVitePlusHeader()) return;
+	log(vitePlusHeader());
+	log("");
+}
+function accent(text) {
+	return styleText("blue", text);
+}
+function muted(text) {
+	return styleText("gray", text);
+}
+function success(text) {
+	return styleText("green", text);
+}
+function formatDuration(durationMs) {
+	if (durationMs < 1e3) return `${Math.max(1, durationMs)}ms`;
+	const durationSeconds = durationMs / 1e3;
+	if (durationSeconds < 10) return `${durationSeconds.toFixed(1)}s`;
+	return `${Math.round(durationSeconds)}s`;
+}
+function warnMsg(msg) {
+	console.error(styleText(["yellow", "bold"], "warn:"), msg);
+}
+function errorMsg(msg) {
+	console.error(styleText(["red", "bold"], "error:"), msg);
+}
+//#endregion
+export { muted as a, warnMsg as c, log as i, errorMsg as n, printHeader as o, formatDuration as r, success as s, accent as t };

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "0.2.9",
+      "version": "0.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "0.2.9",
+      "version": "0.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@ export const toolchain = {
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.2.1",
+      "version": "8.2.2",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.3",
+      "version": "1.2.5",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@ export const toolchain = {
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "4.1.10",
+      "version": "4.1.11",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.77.0",
+      "version": "1.79.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.62.0",
+      "version": "0.64.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -100,7 +100,7 @@ export const toolchain = {
       "id": "vite-task",
       "name": "vite-task",
       "revision": "d05b1dcdbaabaa69643ee0b89cebe3cd390957e9",
-      "builtAt": "2026-08-12T02:51:52Z",
+      "builtAt": "2026-08-24T03:41:26Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.143.0",
+      "version": "0.146.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "0.2.9",
+      "version": "0.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "0.2.9",
+      "version": "0.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.2.1",
+      "version": "8.2.2",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.3",
+      "version": "1.2.5",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "4.1.10",
+      "version": "4.1.11",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.77.0",
+      "version": "1.79.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.62.0",
+      "version": "0.64.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -100,7 +100,7 @@
       "id": "vite-task",
       "name": "vite-task",
       "revision": "d05b1dcdbaabaa69643ee0b89cebe3cd390957e9",
-      "builtAt": "2026-08-12T02:51:52Z",
+      "builtAt": "2026-08-24T03:41:26Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.143.0",
+      "version": "0.146.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/tsconfig-BVHG3DpR.js

@@ -0,0 +1,2 @@
+import { a as hasBaseUrlInTsconfig, i as fixBaseUrlInTsconfig } from "./tsconfig-LD2QhQ0O.js";
+export { fixBaseUrlInTsconfig, hasBaseUrlInTsconfig };

package/dist/{tsconfig-7v_BHagU.js → tsconfig-LD2QhQ0O.js}

@@ -1,6 +1,7 @@
-import { d as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-CG513DRa.js";
-import { A as isCancel, C as log, M as runCommandSilently, t as cancelAndExit, x as confirm } from "./prompts-CHz_98bJ.js";
-import { c as parse, o as applyEdits, s as modify } from "./json-qlK6UH0r.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-Bn-U8o4v.js";
+import { A as isCancel, C as log, t as cancelAndExit, x as confirm } from "./prompts-DF3yU-eU.js";
+import { c as parse, o as applyEdits, s as modify } from "./json-cULBl7Pi.js";
+import { n as runCommandSilently } from "./command-CguLh2KL.js";
 import path from "node:path";
 import { styleText } from "node:util";
 import fs from "node:fs";
@@ -148,4 +149,4 @@ function rewriteTypesInTsconfig(filePath) {
 	return true;
 }
 //#endregion
-export { hasTypesToRewriteInTsconfig as a, rewriteTypesInTsconfig as c, hasBaseUrlInTsconfig as i, findTsconfigFiles as n, hasVitestTypesInTsconfig as o, fixBaseUrlInTsconfig as r, removeDeprecatedTsconfigFalseOption as s, confirmBaseUrlFix as t };
+export { hasBaseUrlInTsconfig as a, hasVitestTypesInTsconfig as c, fixBaseUrlInTsconfig as i, removeDeprecatedTsconfigFalseOption as l, findTsconfigFiles as n, hasBaseUrlInTsconfigFile as o, findTsconfigFilesWithBaseUrl as r, hasTypesToRewriteInTsconfig as s, confirmBaseUrlFix as t, rewriteTypesInTsconfig as u };

package/dist/version.js

@@ -1,6 +1,7 @@
-import { i as log, l as renderCliDoc, o as printHeader, t as accent } from "./terminal-Bz-ps6rJ.js";
-import { h as version } from "./constants-CG513DRa.js";
-import { i as hasVitePlusDependency, n as detectPackageMetadata } from "./package-B4T8RGMG.js";
+import { t as renderCliDoc } from "./help-BmKpeOP9.js";
+import { i as log, o as printHeader, t as accent } from "./terminal-MKGAuy-p.js";
+import { _ as version } from "./constants-Bn-U8o4v.js";
+import { i as hasVitePlusDependency, n as detectPackageMetadata } from "./package-CBe9EWPY.js";
 import path from "node:path";
 import fs from "node:fs";
 //#region src/version.ts

package/dist/versions.js

@@ -1,9 +1,9 @@
 export const versions = {
-  "vite": "8.2.1",
-  "rolldown": "1.2.3",
-  "vitest": "4.1.10",
-  "oxfmt": "0.62.0",
-  "oxlint": "1.77.0",
+  "vite": "8.2.2",
+  "rolldown": "1.2.5",
+  "vitest": "4.1.11",
+  "oxfmt": "0.64.0",
+  "oxlint": "1.79.0",
   "oxlint-tsgolint": "7.0.2001",
   "tsdown": "0.22.14"
 };

package/docs/guide/env.md

@@ -21,7 +21,12 @@ latest LTS.
 
 When a project declares `packageManager` (or `devEngines.packageManager`) in `package.json`, matching package-manager shims also use that package-manager version. For example, `packageManager: "npm@10.9.4"` makes both `npm` and `npx` run through npm 10.9.4. Alias pairs follow the installed package-manager shims: `npm`/`npx`, `pnpm`/`pnpx`, `yarn`/`yarnpkg`, and `bun`/`bunx`. Vite+ does not translate mismatched commands, so a project pinned to `pnpm` still lets `npm` fall back to the npm that comes with the resolved Node.js runtime.
 
-By default, Vite+ stores its managed runtime and related files in `~/.vite-plus`. If needed, you can override that location with `VP_HOME`.
+A fresh install uses the split platform layout by default. On Unix, Vite+
+stores managed runtimes and related files in `~/.local/share/vite-plus`. It
+stores executables in the Vite+-owned `~/.local/share/vite-plus/bin` directory.
+On Windows, Vite+ uses `%LOCALAPPDATA%\vite-plus\data` for data and
+`%LOCALAPPDATA%\vite-plus\bin` for executables. Vite+ does not move an existing
+`~/.vite-plus` install. `VP_HOME` puts all categories under one custom root.
 
 If you want to keep that behavior, run:
 
@@ -43,7 +48,7 @@ This switches to system-first mode, where the shims prefer your system Node.js a
 
 ### Setup
 
-- `vp env setup` creates or updates shims in `VP_HOME/bin` (and writes the per-shell setup scripts under `VP_HOME`)
+- `vp env setup` creates or updates shims in the resolved bin directory. It writes shell setup scripts in the config directory.
 - `vp env on` enables managed mode so shims always use Vite+-managed Node.js
 - `vp env off` enables system-first mode so shims prefer system Node.js first
 - `vp env print` prints the shell snippet for the current session
@@ -51,9 +56,12 @@ This switches to system-first mode, where the shims prefer your system Node.js a
 PowerShell needs to dot-source the generated setup script in the current shell before `vp env use` can affect only that shell session:
 
 ```powershell
-. "$env:USERPROFILE\.vite-plus\env.ps1"
+. "$env:APPDATA\vite-plus\env.ps1"
 ```
 
+If an older Vite+ install uses `%USERPROFILE%\.vite-plus`, source the `env.ps1`
+file in that directory instead.
+
 Add that line to the end of your PowerShell `$PROFILE` to apply it automatically in new shells. It does not require elevated privileges.
 
 Create the profile file if it does not already exist:
@@ -76,9 +84,11 @@ node --version
 vp-use --unset
 ```
 
-Only `vp env use` needs this alternate command. Other `vp env` commands work normally in Command Prompt. `vp env setup` creates `vp-use.cmd` under `VP_HOME/bin` on Windows.
+Only `vp env use` needs this alternate command. Other `vp env` commands work normally in Command Prompt. `vp env setup` creates `vp-use.cmd` in the bin directory on Windows.
 
-In CI, `vp env use` can still run without shell initialization. It writes a temporary session file under `VP_HOME` so later shim calls in the same job can resolve the selected Node.js version.
+In CI, `vp env use` can run without shell initialization. It writes a temporary
+session file in the resolved state directory. Later shim calls in the same job
+use this file to select the Node.js version.
 
 ### Manage
 
@@ -144,7 +154,11 @@ Vite+ creates a `corepack` shim by default, so corepack works without a system N
 - On Node.js 25 and later, where corepack is no longer bundled, Vite+ installs corepack as a managed global package on first use. Only the `corepack` binary is linked; run `vp install -g corepack` yourself if you also want the package's pnpm/yarn launchers exposed directly.
 - If you install corepack explicitly with `vp install -g corepack`, that installation is always preferred.
 
-`corepack enable` normally creates `pnpm`/`yarn` launchers next to the corepack binary, which under Vite+ would not be on `PATH`. The shim fixes this by defaulting `--install-directory` to `VP_HOME/bin`, so after `corepack enable` the launchers are available everywhere and still resolve the project's Node.js and package-manager versions:
+`corepack enable` normally creates `pnpm` and `yarn` launchers next to the
+corepack binary. Vite+ does not add that location to `PATH`. The shim sets
+`--install-directory` to the resolved bin directory by default. The launchers
+are then available on `PATH`. They still use the Node.js and package-manager
+versions for the project:
 
 ```bash
 corepack enable               # pnpm and yarn now resolve via corepack

package/docs/guide/install.md

@@ -81,7 +81,8 @@ Updates keep the version spec a package was installed with: a package installed
 ::: warning
 These commands do **NOT** interact with the underlying package manager's global installation directory.
 
-Instead, Vite+ manages its own global packages under `VP_HOME/packages`, allowing them to remain available across different Node.js versions.
+Instead, Vite+ stores its global packages in `packages/` under the resolved data
+directory. These packages remain available across different Node.js versions.
 
 As a result, commands such as `vp link` do not affect Vite+'s global packages and will not appear in `vp list -g`.
 :::

package/docs/guide/installer-env-vars.md

@@ -11,6 +11,10 @@ These variables control the installer scripts and the standalone Windows install
 - **Purpose**: Version to install
 - **Default**: `latest`
 - **CLI equivalent**: `--version`
+- **Note**: Vite+ 0.2.x and earlier do not support the split directory layout.
+  The installer always puts these releases in the monolithic root (`VP_HOME` or
+  `~/.vite-plus`). This rule also applies to a fresh machine. The installer
+  checks the downloaded binary and prints a notice.
 - **Example**:
 
   ```bash
@@ -25,9 +29,15 @@ These variables control the installer scripts and the standalone Windows install
 
 ### `VP_HOME`
 
-- **Purpose**: Installation directory; the installed CLI reads the same variable as the Vite+ home directory (see [Environment](/guide/env))
-- **Default**: `~/.vite-plus` (Unix) or `%USERPROFILE%\.vite-plus` (Windows)
-- **CLI equivalent**: `--install-dir`
+- **Purpose**: Optional pin for the single-root layout. Set it to an absolute
+  path. Vite+ then puts bin, data, cache, config, and state under that directory.
+  The installed CLI reads the same variable. See [Environment](/guide/env).
+- **Default**: unset. Vite+ reuses an existing install in `~/.vite-plus` on
+  Unix or `%USERPROFILE%\.vite-plus` on Windows. The directory must contain a
+  `current` link. Otherwise, a fresh install uses the split platform layout. On
+  Unix, it uses `~/.local/share/vite-plus` and its Vite+-owned `bin`
+  subdirectory. On Windows, it uses `%LOCALAPPDATA%\vite-plus\data` and
+  `%LOCALAPPDATA%\vite-plus\bin`.
 - **Example**:
 
   ```bash
@@ -40,6 +50,25 @@ These variables control the installer scripts and the standalone Windows install
   $env:VP_HOME = "D:\vite-plus"; irm https://vite.plus/ps1 | iex
   ```
 
+### `VP_BIN_DIR` / `VP_DATA_DIR` / `VP_CACHE_DIR`
+
+- **Purpose**: Internal absolute directory overrides for integrations that
+  must pin a split install. Set all three variables together. The installer
+  rejects an incomplete group. Vite+ ignores the group when `VP_HOME` is set
+  or when it reuses an existing `~/.vite-plus` install.
+- **Default**: unset (XDG / platform defaults)
+- **Persistence**: The generated environment file does not export these
+  variables. An integration that uses them must provide the complete group to
+  each Vite+ process.
+- **Example**:
+
+  ```bash
+  export VP_DATA_DIR=$HOME/vite-plus-data
+  export VP_BIN_DIR=$VP_DATA_DIR/bin
+  export VP_CACHE_DIR=$HOME/.cache/vite-plus
+  curl -fsSL https://vite.plus | bash
+  ```
+
 ### `NPM_CONFIG_REGISTRY`
 
 - **Purpose**: Custom npm registry URL
@@ -71,7 +100,12 @@ These variables control the installer scripts and the standalone Windows install
 
 ### Development variables
 
-When developing Vite+ itself, `VP_LOCAL_TGZ` (path to a local `vite-plus.tgz`) and `VP_LOCAL_BINARY` (path to a local `vp` binary) feed the installer a local build. The installers also set `VP_INSTALL_STOP` themselves; do not set it manually.
+Use `VP_LOCAL_TGZ` and `VP_LOCAL_BINARY` when you develop Vite+ itself.
+`VP_LOCAL_TGZ` specifies a local `vite-plus.tgz` file. `VP_LOCAL_BINARY`
+specifies a local `vp` binary. The installers use these files for the local
+build. They use `VP_DUMP_DIRS=1` to get the layout mode and all five `EnvConfig`
+category roots from the selected binary. They do not resolve the directory
+variables. The installers set `VP_INSTALL_STOP`; do not set it manually.
 
 ## Runtime Variables
 
@@ -161,6 +195,8 @@ Vite+ sets additional `VP_*` variables during shim dispatch and shell integratio
 ### `VP_LOG`
 
 - **Purpose**: Log filter string for `tracing_subscriber`
+- **Installer behavior**: When `CI=true`, `install.sh` hides shell file errors.
+  Set `VP_LOG=trace` to show these errors.
 - **Default**: None
 - **Example**:
   ```bash
@@ -195,7 +231,7 @@ Vite+ also respects these standard environment variables:
 ### `HOME` / `USERPROFILE`
 
 - **Purpose**: User home directory
-- **Effect**: Base for the default `~/.vite-plus` path
+- **Effect**: Base for the existing-install probe (`~/.vite-plus`) and for split platform defaults
 
 ## Precedence
 

package/docs/guide/migrate-rules.md

@@ -82,6 +82,14 @@ Related rules:
 - A direct `vite` declaration is never removed merely because a root override
   exists.
 - Plain or stale aliases are normalized; named catalog references are kept.
+- Under pnpm the managed override keys use an explicit `@*` range (`vite@*`,
+  `vitest@*`). pnpm applies an override by replacing the declared spec on every
+  manifest, importer manifests included. A bare key matches any spec, including
+  `catalog:`, and `vp up` then rewrites that reference to a concrete version.
+  The `@*` range keeps the override on the semver ranges that transitive and
+  peer declarations use. It leaves `catalog:` references to the catalog, which
+  already resolves them to Vite+ core. Migration re-keys a project that still
+  holds the bare key, and keeps its named-catalog choice.
 - The direct-entry rule above is pnpm-specific. Bun mirrors its core alias as
   a direct dependency for its peer resolver, and npm browser-provider layouts
   may need a top-level `vite` edge so nested Vitest packages can resolve
@@ -228,6 +236,7 @@ scripts while preserving their arguments:
 | `lint-staged` | `vp staged`                                 |
 | `eslint`      | `vp lint`, when its optional migration runs |
 | `prettier`    | `vp fmt`, when its optional migration runs  |
+| `tsup`        | `vp pack`, when its optional migration runs |
 
 For commands launched through `bunx`, migration preserves `bunx` and its
 `--bun` flag (keeping the user's chosen runtime) and rewrites only the managed

package/docs/guide/migrate.md

@@ -4,7 +4,7 @@
 
 ## Overview
 
-This command is the starting point for consolidating separate Vite, Vitest, Oxlint, Oxfmt, ESLint, and Prettier setups into Vite+.
+This command is the starting point for consolidating separate Vite, Vitest, Oxlint, Oxfmt, ESLint, Prettier, and tsup setups into Vite+.
 
 Use it when you want to take an existing project and move it onto the Vite+ defaults instead of wiring each tool by hand.
 
@@ -70,7 +70,7 @@ After running the migration:
 - Run `vp install`
 - Run `vp check`
 - Run `vp test`
-- Run `vp build`
+- Run `vp build` (or `vp pack` if you are building a library)
 
 ## Manual Installation & Migration
 
@@ -85,7 +85,7 @@ You need to add overrides to your package manager so that other packages resolve
 ```json
 "overrides": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "4.1.10"
+  "vitest": "4.1.11"
 }
 ```
 
@@ -94,7 +94,7 @@ If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
 ```yaml
 overrides:
   vite: npm:@voidzero-dev/vite-plus-core@latest
-  vitest: 4.1.10
+  vitest: 4.1.11
 ```
 
 Or, if you are using Yarn:
@@ -102,7 +102,7 @@ Or, if you are using Yarn:
 ```json
 "resolutions": {
   "vite": "npm:@voidzero-dev/vite-plus-core@latest",
-  "vitest": "4.1.10"
+  "vitest": "4.1.11"
 }
 ```
 

package/docs/guide/test.md

@@ -6,6 +6,14 @@
 
 `vp test` is built on [Vitest](https://vitest.dev/), so you get a Vite-native test runner that reuses your Vite config and plugins, supports Jest-style expectations, snapshots, and coverage, and handles modern ESM, TypeScript, and JSX projects cleanly.
 
+Vitest APIs are available from `vite-plus/test`, so a single `vite-plus` install is enough — you do not need to install `vitest` directly:
+
+```ts [src/example.test.ts]
+import { describe, expect, it, vi } from 'vite-plus/test';
+```
+
+For the browser mode subpaths (`vite-plus/test/browser*`), see [Migrating Vitest](/guide/migrate#vitest).
+
 ::: info
 `vp test` always runs the built-in Vitest command. If your project also has a `test` script in `package.json`, run `vp run test` when you want to run that script instead. See [Built-in Commands vs Scripts](/guide/run#built-in-commands-vs-scripts).
 :::

package/docs/guide/upgrade.md

@@ -43,6 +43,51 @@ vp upgrade <version>              # install a specific version
 vp upgrade --registry <registry>  # use a custom npm registry
 ```
 
+### Move an Existing Install to the Split Directory Layout
+
+Vite+ 0.3.0 is the first release that supports the split directory layout.
+Vite+ 0.2.x and earlier use the single-root layout for fresh installs and
+upgrades.
+
+`vp upgrade` keeps an existing default install in `~/.vite-plus` on Unix or
+`%USERPROFILE%\.vite-plus` on Windows. The command upgrades the CLI in that
+directory. It does not move the install to the split platform directories. You
+can continue to use the existing layout.
+
+To use the split layout now, remove the existing install. Then install Vite+
+again. Run `vp implode` in a shell that uses the current install. The command
+removes the generated environment file and shell profile entries. It does not
+unset directory variables in the current shell. Unset all Vite+ directory
+variables before you run the installer. This can include values from an earlier
+preview environment file. Alternatively, start a new shell after `vp implode`.
+Then run the installer in the new shell.
+
+::: warning
+`vp implode` removes all Vite+-managed Node.js runtimes, global packages,
+configuration, and caches. Keep the existing layout if you do not want to
+recreate that data.
+:::
+
+```bash
+vp implode
+unset VP_HOME VP_DATA_DIR VP_BIN_DIR VP_CACHE_DIR
+curl -fsSL https://vite.plus | bash
+```
+
+On Windows:
+
+```powershell
+vp implode
+Remove-Item Env:\VP_HOME, Env:\VP_DATA_DIR, Env:\VP_BIN_DIR, Env:\VP_CACHE_DIR -ErrorAction SilentlyContinue
+irm https://vite.plus/ps1 | iex
+```
+
+Also remove persistent definitions of `VP_HOME`, `VP_DATA_DIR`, `VP_BIN_DIR`,
+and `VP_CACHE_DIR` from your shell profile or system environment. A fresh
+install uses `VP_HOME` or a complete `VP_*_DIR` group that remains set.
+`VP_HOME` selects the single-root layout. If you install Vite+ 0.2.x or earlier,
+the installer also uses this layout. The installer prints a notice.
+
 ### Rollback
 
 Vite+ keeps the **3 most recent** versions installed so you can revert quickly:
@@ -69,7 +114,9 @@ If you migrated with `vp migrate`, your project pins `vitest` to an exact versio
 
 - **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`)
+- **pnpm:** a `vitest@*` entry under `overrides` in `pnpm-workspace.yaml`. If your `package.json` already has a `pnpm` field, the entry lives under `pnpm.overrides` in `package.json` instead. pnpm ignores `pnpm-workspace.yaml` overrides when `package.json` defines `pnpm.overrides`.
+
+Under pnpm the managed keys use an explicit `@*` range (`vite@*`, `vitest@*`). pnpm applies an override by replacing the declared spec on every manifest, importer manifests included. A bare key matches any spec, including `catalog:`. The `@*` range keeps the override on the semver ranges that transitive and peer declarations use, and leaves `catalog:` references intact. `vp up` therefore no longer rewrites them to a concrete version.
 
 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.