vite-plus 1.5.0 → 1.6.0

package/docs/guide/local-cli.md

@@ -148,7 +148,7 @@ The project-local CLI can be used independently for:
 - [`vp pack`](/guide/pack) with tsdown
 - [`vp toolchain`](/guide/upgrade#show-the-toolchain) for inspecting the versions bundled with the project-local package
 - [`vp run`](/guide/run) and task caching across workspaces
-- [package-manager commands](/guide/package-management) using the Node.js runtime already active in your shell
+- [package-manager commands](/guide/package-management/) using the Node.js runtime already active in your shell
 - [`vp create`](/guide/create), [`vp migrate`](/guide/migrate), and project configuration commands
 
 The local package cannot manage the machine-level Vite+ installation. The `vp env`, `vp upgrade`, and `vp implode` commands require the [global CLI](/guide/global-cli). Upgrade or remove a local-only installation through your package manager.

package/docs/guide/migrate-rules.md

@@ -398,7 +398,9 @@ Migration converts the Volta `volta.node` pin to `.node-version`, because Vite+
 
 ### Bun
 
-- Bun catalogs only resolve inside a workspace (a root `package.json` with a non-empty `workspaces`). In a bun workspace, existing top-level or workspace catalog locations and named catalog references are preserved. A standalone (single-package) bun project keeps concrete specs and gets no catalog field, because `bun install` cannot resolve `catalog:` outside a workspace.
+- Bun catalogs only resolve inside a workspace, which is a root `package.json` with a `workspaces` field. An empty `workspaces` field also counts. In a bun workspace, existing top-level or workspace catalog locations and named catalog references are preserved. A standalone bun project without `workspaces` keeps concrete specs and gets no catalog field, because `bun install` cannot resolve `catalog:` outside a workspace.
+- Bun before 1.2.21 reads only catalogs under `workspaces`. On those versions, migration uses catalogs only when the project already has one under `workspaces`, and keeps concrete specs otherwise.
+- When an existing named catalog already owns `vite-plus`, `vite`, or `vitest`, migration adds missing toolchain entries to that catalog instead of creating a default catalog beside it.
 - The core alias is mirrored as a direct `vite` dependency so Bun sees the peer provider before applying overrides.
 
 ## After the Migration

package/docs/guide/migrate.md

@@ -95,21 +95,21 @@ Upgrade the [global CLI](./upgrade.md#global-vp) to your target 1.0 release, the
 
 ### Without the Global CLI
 
-Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.5.0` release:
+Use an existing Node.js runtime that satisfies `^22.18.0 || ^24.11.0 || >=26.0.0`. Run the target migrator through your package manager without adding it to the project first. For the `1.6.0` release:
 
 ::: code-group
 
 ```bash [pnpm]
-pnpm dlx --package=vite-plus@1.5.0 vp migrate --no-interactive
+pnpm dlx --package=vite-plus@1.6.0 vp migrate --no-interactive
 ```
 
 ```bash [npm]
-npx --package=vite-plus@1.5.0 vp migrate --no-interactive
+npx --package=vite-plus@1.6.0 vp migrate --no-interactive
 ```
 
 :::
 
-Replace `1.5.0` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
+Replace `1.6.0` with your target release. For a preview, use the version from the PR and pass `--registry=https://registry-bridge.viteplus.dev` to `pnpm` or `npx` before the `vp` command. Keep the version in `--package` explicit so you run the target migrator rather than the old local CLI.
 
 After migration, finish dependency installation and validate with the updated local CLI:
 

package/docs/guide/package-management/add.md

@@ -0,0 +1,84 @@
+# vp add
+
+Add packages to the project and update its manifest and lockfile.
+
+```bash
+vp add react
+vp add -D typescript
+vp add --save-peer react
+vp add --filter web react
+```
+
+## Options
+
+Choose one dependency target at a time. Peer dependencies follow the native manager's behavior, including whether it also records a development dependency.
+
+| Option                       | Description                                            | Notes                                                                          |
+| ---------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------ |
+| `-P, --save-prod`            | Save to dependencies, the default target.              | Choose one dependency target.                                                  |
+| `-D, --save-dev`             | Save to devDependencies.                               | Choose one dependency target.                                                  |
+| `--save-peer`                | Request the manager's peer-dependency save behavior.   | Choose one dependency target.                                                  |
+| `-O, --save-optional`        | Save to optionalDependencies.                          | Choose one dependency target.                                                  |
+| `-E, --save-exact`           | Save an exact dependency version.                      |                                                                                |
+| `--save-catalog-name <name>` | Save the dependency to a named catalog.                |                                                                                |
+| `--save-catalog`             | Save the dependency to the default catalog.            |                                                                                |
+| `--allow-build <names>`      | Allow the named packages to run postinstall scripts.   |                                                                                |
+| `--ignore-scripts`           | Do not run lifecycle scripts.                          |                                                                                |
+| `--no-optional`              | Do not install optionalDependencies.                   | Cannot be combined with --global.                                              |
+| `--frozen-lockfile`          | Prevent lockfile changes.                              | Cannot be combined with --global. Overrides an earlier `--no-frozen-lockfile`. |
+| `--no-frozen-lockfile`       | Explicitly allow lockfile updates.                     | Cannot be combined with --global. Overrides an earlier `--frozen-lockfile`.    |
+| `--lockfile-only`            | Update the lockfile without a full install.            | Cannot be combined with --global.                                              |
+| `--prefer-offline`           | Use cached packages when available.                    | Cannot be combined with --global.                                              |
+| `--offline`                  | Only use packages already in cache.                    | Cannot be combined with --global.                                              |
+| `-f, --force`                | Request a forced reinstall.                            | Cannot be combined with --global.                                              |
+| `--no-lockfile`              | Skip reading or generating a lockfile.                 | Cannot be combined with --global.                                              |
+| `--shamefully-hoist`         | Create a flat `node_modules` layout.                   | Cannot be combined with --global.                                              |
+| `--silent`                   | Suppress Vite+ output and request native quiet output. | Cannot be combined with --global.                                              |
+| `--filter <pattern>`         | Select workspaces by pattern.                          | Can be repeated.                                                               |
+| `-w, --workspace-root`       | Add to workspace root.                                 |                                                                                |
+| `--workspace`                | Require the dependency to exist in the workspace.      |                                                                                |
+| `-g, --global`               | Install globally.                                      | Requires the global CLI. Uses the [global package store](./global-packages).   |
+| `--node <version>`           | Node.js version to use for global installation.        | Requires --global.                                                             |
+| `--concurrency <number>`     | Number of global package installs to run in parallel.  | Requires --global. Must be a positive integer.                                 |
+
+## Compatibility
+
+The commands below describe project operations. Global mode is described under [Options](#options).
+
+- **npm:** `npm install`.
+- **pnpm:** `pnpm add`.
+- **Yarn Classic:** `yarn add`.
+- **Yarn Modern:** `yarn add`.
+- **Bun:** `bun add`.
+
+| Option                       | npm             | pnpm             | Yarn Classic | Yarn Modern | Bun            | Notes                                              |
+| ---------------------------- | --------------- | ---------------- | ------------ | ----------- | -------------- | -------------------------------------------------- |
+| `-P, --save-prod`            | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `-D, --save-dev`             | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `--save-peer`                | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `-O, --save-optional`        | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `-E, --save-exact`           | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `--save-catalog-name <name>` | No              | 10.12.0 or later | No           | No          | 1.4 or later   |                                                    |
+| `--save-catalog`             | No              | 10.12.0 or later | No           | No          | 1.4 or later   |                                                    |
+| `--allow-build <names>`      | No              | 10.4.0 or later  | No           | No          | No             |                                                    |
+| `--ignore-scripts`           | Yes             | Yes              | Yes          | 3 or later  | Yes            | On Yarn Modern, lockfile-only mode takes priority. |
+| `--no-optional`              | Yes             | Yes              | Yes          | No          | Yes            |                                                    |
+| `--frozen-lockfile`          | No              | No               | Yes          | No          | Yes            |                                                    |
+| `--no-frozen-lockfile`       | No              | No               | No           | No          | Yes            |                                                    |
+| `--lockfile-only`            | Yes             | Yes              | No           | 3 or later  | Yes            |                                                    |
+| `--prefer-offline`           | Yes             | Yes              | Yes          | No          | 1.4.1 or later |                                                    |
+| `--offline`                  | Yes             | Yes              | Yes          | No          | 1.4.1 or later |                                                    |
+| `-f, --force`                | Yes             | Yes              | Yes          | No          | Yes            |                                                    |
+| `--no-lockfile`              | Yes             | Yes              | Yes          | No          | No             |                                                    |
+| `--shamefully-hoist`         | No              | Yes              | No           | No          | No             |                                                    |
+| `--silent`                   | Yes             | Yes              | Yes          | No          | Yes            |                                                    |
+| `--filter <pattern>`         | 7.14.0 or later | Yes              | No           | Yes         | 1.4 or later   |                                                    |
+| `-w, --workspace-root`       | 8.1.0 or later  | Yes              | Yes          | No          | No             |                                                    |
+| `--workspace`                | No              | Yes              | No           | No          | No             |                                                    |
+| `-g, --global`               | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `--node <version>`           | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+| `--concurrency <number>`     | Yes             | Yes              | Yes          | Yes         | Yes            |                                                    |
+
+## Native Options
+
+For native options, see [npm install](https://docs.npmjs.com/cli/v11/commands/npm-install), [pnpm add](https://pnpm.io/cli/add), [Yarn add](https://yarnpkg.com/cli/add), [Yarn Classic add](https://classic.yarnpkg.com/en/docs/cli/add), and [Bun add](https://bun.com/docs/pm/cli/add). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/approve-builds.md

@@ -0,0 +1,48 @@
+# vp pm approve-builds
+
+Approve dependency lifecycle scripts using the selected manager's trust policy. Approve only packages whose install scripts you intend to execute.
+
+```bash
+vp pm approve-builds
+vp pm approve-builds sharp
+vp pm approve-builds '!untrusted-package'
+vp pm approve-builds --all
+```
+
+## Options
+
+Supply packages to approve, or prefix a name with `!` to request denial where supported. Quote denial arguments to avoid shell history expansion.
+
+| Option  | Description                                         | Notes                                                              |
+| ------- | --------------------------------------------------- | ------------------------------------------------------------------ |
+| `--all` | Approve all packages pending build-script approval. | Cannot be combined with package names, including names after `--`. |
+
+## Compatibility
+
+- **npm:** 11.16 or later: `npm approve-scripts`. Earlier versions warn and skip. Denials use `npm deny-scripts`.
+- **pnpm:** 10.1 or later: `pnpm approve-builds`. Earlier versions warn and skip.
+- **Yarn Classic:** No command. Warns and exits successfully without performing the operation.
+- **Yarn Modern:** No command. Warns and exits successfully without performing the operation.
+- **Bun:** `bun pm trust` for named packages or `--all`.
+
+| Option  | npm              | pnpm             | Yarn Classic | Yarn Modern | Bun | Notes |
+| ------- | ---------------- | ---------------- | ------------ | ----------- | --- | ----- |
+| `--all` | 11.16.0 or later | 10.32.0 or later | No           | No          | Yes |       |
+
+With no package names, pnpm opens its interactive flow and npm lists pending packages with `--allow-scripts-pending`. Bun does not open an interactive selector; inspect pending packages with `bun pm untrusted` and then name the packages to trust.
+
+Denial arguments prefixed with `!` require pnpm 11 or later or npm 11.16 or later. npm requires separate approval and denial invocations. Bun skips denial entries with a warning because it uses `trustedDependencies` rather than a denylist.
+
+For Yarn Modern, configure `enableScripts: false` and explicitly allow trusted packages through `dependenciesMeta`.
+
+### npm Build-Script Policy
+
+npm 12 enforces `allowScripts` in `package.json`. Dependency install scripts not covered by the policy are skipped, including implicit native builds. Approval updates policy but does not run scripts skipped earlier. Follow it with [`vp pm rebuild <package>`](./rebuild).
+
+In npm 11.16 through 11.x, this policy is advisory. Scripts still run and npm warns about unreviewed packages.
+
+## Native Options
+
+For native options, see [npm approve-scripts](https://docs.npmjs.com/cli/v11/commands/npm-approve-scripts), [npm deny-scripts](https://docs.npmjs.com/cli/v11/commands/npm-deny-scripts), [pnpm approve-builds](https://pnpm.io/cli/approve-builds), [Bun pm trust](https://bun.com/docs/pm/cli/pm), and [Bun pm untrusted](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).
+
+For script policy configuration, see [npm package.json](https://docs.npmjs.com/cli/v11/configuring-npm/package-json), [Yarn enableScripts](https://yarnpkg.com/configuration/yarnrc#enableScripts), and [Bun lifecycle scripts](https://bun.com/docs/pm/lifecycle).

package/docs/guide/package-management/audit.md

@@ -0,0 +1,39 @@
+# vp pm audit
+
+Audit dependencies for known vulnerabilities.
+
+```bash
+vp pm audit
+vp pm audit --json
+vp pm audit --production --level high
+```
+
+## Options
+
+| Option            | Description                                  | Notes                             |
+| ----------------- | -------------------------------------------- | --------------------------------- |
+| `--fix`           | Request automatic vulnerability remediation. |                                   |
+| `--json`          | Request native JSON output.                  | Output retains the native schema. |
+| `--level <level>` | Minimum vulnerability level to report.       |                                   |
+| `--production`    | Only audit production dependencies.          |                                   |
+
+## Compatibility
+
+- **npm:** `npm audit` or `npm audit fix`.
+- **pnpm:** `pnpm audit`.
+- **Yarn Classic:** `yarn audit`.
+- **Yarn Modern:** 2.4 or later: `yarn npm audit`. Earlier versions warn and skip.
+- **Bun:** `bun audit` or `bun audit fix`.
+
+| Option            | npm | pnpm | Yarn Classic | Yarn Modern | Bun             | Notes |
+| ----------------- | --- | ---- | ------------ | ----------- | --------------- | ----- |
+| `--fix`           | Yes | Yes  | No           | No          | 1.4 or later    |       |
+| `--json`          | Yes | Yes  | Yes          | Yes         | Yes             |       |
+| `--level <level>` | Yes | Yes  | Yes          | Yes         | Yes             |       |
+| `--production`    | Yes | Yes  | Yes          | Yes         | 1.2.21 or later |       |
+
+Vulnerability output and failure thresholds retain the native manager's semantics.
+
+## Native Options
+
+For native options, see [npm audit](https://docs.npmjs.com/cli/v11/commands/npm-audit), [pnpm audit](https://pnpm.io/cli/audit), [Yarn npm audit](https://yarnpkg.com/cli/npm/audit), [Yarn Classic audit](https://classic.yarnpkg.com/en/docs/cli/audit), and [Bun audit](https://bun.com/docs/pm/cli/audit). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/cache.md

@@ -0,0 +1,53 @@
+# vp pm cache
+
+Inspect or clean the package manager's download cache or store. This is distinct from [`vp cache`](/guide/cache), which manages task results.
+
+```bash
+vp pm cache dir
+vp pm cache clean
+```
+
+## Options
+
+- `dir` and `path` print the cache or store location.
+- `clean` requests native cache cleanup.
+
+Other subcommands warn and exit successfully without running a command. There are no additional Vite+ options.
+
+### `dir`
+
+Print the cache or store location. Alias: `path`. There are no command-specific options.
+
+### `clean`
+
+Request native cache cleanup. There are no command-specific options.
+
+## Compatibility
+
+### `dir`
+
+- **npm:** `npm config get cache`.
+- **pnpm:** `pnpm store path`.
+- **Yarn Classic:** `yarn cache dir`.
+- **Yarn Modern:** `yarn config get cacheFolder`.
+- **Bun:** `bun pm cache`.
+
+### `clean`
+
+- **npm:** `npm cache clean`.
+- **pnpm:** `pnpm store prune`. Prunes the store rather than deleting all content.
+- **Yarn Classic:** `yarn cache clean`.
+- **Yarn Modern:** `yarn cache clean`.
+- **Bun:** `bun pm cache rm`.
+
+npm normally requires an explicit native `--force` for cache deletion:
+
+```bash
+vp pm cache clean -- --force
+```
+
+That example is npm-specific. Vite+ does not expose a separate `vp pm store` command.
+
+## Native Options
+
+For native options, see [npm config](https://docs.npmjs.com/cli/v11/commands/npm-config), [npm cache](https://docs.npmjs.com/cli/v11/commands/npm-cache), [pnpm store](https://pnpm.io/cli/store), [Yarn config get](https://yarnpkg.com/cli/config/get), [Yarn cache clean](https://yarnpkg.com/cli/cache/clean), [Yarn Classic cache](https://classic.yarnpkg.com/en/docs/cli/cache), and [Bun pm cache](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/ci.md

@@ -0,0 +1,28 @@
+# vp pm ci
+
+Install dependencies with a frozen lockfile for CI.
+
+```bash
+vp pm ci
+vp pm ci -- --ignore-scripts
+```
+
+## Options
+
+This command has no additional Vite+ options. For translated Vite+ options, use [`vp install --frozen-lockfile`](./install).
+
+There are no command-specific options.
+
+## Compatibility
+
+- **npm:** `npm ci`.
+- **pnpm:** `pnpm install --frozen-lockfile`.
+- **Yarn Classic:** `yarn install --frozen-lockfile`.
+- **Yarn Modern:** `yarn install --immutable`.
+- **Bun:** `bun install --frozen-lockfile`.
+
+The native manager determines installation cleanup and lockfile validation. This command does not make all managers behave like `npm ci` beyond the frozen-lockfile request.
+
+## Native Options
+
+For native options, see [npm ci](https://docs.npmjs.com/cli/v11/commands/npm-ci), [pnpm install](https://pnpm.io/cli/install), [Yarn install](https://yarnpkg.com/cli/install), [Yarn Classic install](https://classic.yarnpkg.com/en/docs/cli/install), and [Bun install](https://bun.com/docs/pm/cli/install). To pass these options through Vite+, see [Native Arguments](./#native-arguments). For CI setup, see the [CI guide](/guide/ci).

package/docs/guide/package-management/config.md

@@ -0,0 +1,119 @@
+# vp pm config
+
+Read and write package-manager configuration. Alias: `vp pm c`. This is distinct from `vp config`, which configures project tooling.
+
+```bash
+vp pm config list
+vp pm config get registry
+vp pm config set registry https://registry.npmjs.org --location project
+vp pm config delete registry --location project
+```
+
+Configuration keys are manager-specific. The registry examples use npm or pnpm keys, not Yarn 2 configuration keys.
+
+## Options
+
+- `list` displays configuration.
+- `get <key>` reads a value.
+- `set <key> <value>` writes a value.
+- `delete <key>` removes a value.
+
+Here `--global` selects configuration scope, not Vite+'s global package store.
+
+These subcommands do not accept additional native arguments after `--`.
+
+### `list`
+
+| Option                               | Description                     | Notes                             |
+| ------------------------------------ | ------------------------------- | --------------------------------- |
+| `--json`                             | Request native JSON output.     | Output retains the native schema. |
+| `-g, --global`                       | Use global config.              | Overrides `--location`.           |
+| `--location <project\|user\|global>` | Choose the configuration scope. |                                   |
+
+### `get`
+
+| Option                               | Description                     | Notes                             |
+| ------------------------------------ | ------------------------------- | --------------------------------- |
+| `--json`                             | Request native JSON output.     | Output retains the native schema. |
+| `-g, --global`                       | Use global config.              | Overrides `--location`.           |
+| `--location <project\|user\|global>` | Choose the configuration scope. |                                   |
+
+### `set`
+
+| Option                               | Description                     | Notes                             |
+| ------------------------------------ | ------------------------------- | --------------------------------- |
+| `--json`                             | Request native JSON output.     | Output retains the native schema. |
+| `-g, --global`                       | Use global config.              | Overrides `--location`.           |
+| `--location <project\|user\|global>` | Choose the configuration scope. |                                   |
+
+### `delete`
+
+| Option                               | Description                     | Notes                   |
+| ------------------------------------ | ------------------------------- | ----------------------- |
+| `-g, --global`                       | Use global config.              | Overrides `--location`. |
+| `--location <project\|user\|global>` | Choose the configuration scope. |                         |
+
+## Compatibility
+
+### `list`
+
+- **npm:** `npm config list`.
+- **pnpm:** `pnpm config list`.
+- **Yarn Classic:** `yarn config list`.
+- **Yarn Modern:** `yarn config`.
+- **Bun:** Fallback: `npm config list`. Uses npm configuration, not `bunfig.toml`.
+
+| Option                               | npm                   | pnpm                  | Yarn Classic | Yarn Modern           | Bun                   | Notes                              |
+| ------------------------------------ | --------------------- | --------------------- | ------------ | --------------------- | --------------------- | ---------------------------------- |
+| `--json`                             | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |                                    |
+| `-g, --global`                       | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |                                    |
+| `--location <project\|user\|global>` | project, user, global | project, user, global | user, global | project, user, global | project, user, global | Reads retain merged configuration. |
+
+### `get`
+
+- **npm:** `npm config get`.
+- **pnpm:** `pnpm config get`.
+- **Yarn Classic:** `yarn config get`.
+- **Yarn Modern:** `yarn config get`.
+- **Bun:** Fallback: `npm config get`. Uses npm configuration, not `bunfig.toml`.
+
+| Option                               | npm                   | pnpm                  | Yarn Classic | Yarn Modern           | Bun                   | Notes                              |
+| ------------------------------------ | --------------------- | --------------------- | ------------ | --------------------- | --------------------- | ---------------------------------- |
+| `--json`                             | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |                                    |
+| `-g, --global`                       | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |                                    |
+| `--location <project\|user\|global>` | project, user, global | project, user, global | user, global | project, user, global | project, user, global | Reads retain merged configuration. |
+
+### `set`
+
+- **npm:** `npm config set`.
+- **pnpm:** `pnpm config set`.
+- **Yarn Classic:** `yarn config set`.
+- **Yarn Modern:** `yarn config set`.
+- **Bun:** Fallback: `npm config set`. Uses npm configuration, not `bunfig.toml`.
+
+| Option                               | npm                   | pnpm                  | Yarn Classic | Yarn Modern           | Bun                   | Notes |
+| ------------------------------------ | --------------------- | --------------------- | ------------ | --------------------- | --------------------- | ----- |
+| `--json`                             | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |       |
+| `-g, --global`                       | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |       |
+| `--location <project\|user\|global>` | project, user, global | project, user, global | user, global | project, user, global | project, user, global |       |
+
+### `delete`
+
+- **npm:** `npm config delete`.
+- **pnpm:** `pnpm config delete`.
+- **Yarn Classic:** `yarn config delete`.
+- **Yarn Modern:** `yarn config unset`.
+- **Bun:** Fallback: `npm config delete`. Uses npm configuration, not `bunfig.toml`.
+
+| Option                               | npm                   | pnpm                  | Yarn Classic | Yarn Modern           | Bun                   | Notes |
+| ------------------------------------ | --------------------- | --------------------- | ------------ | --------------------- | --------------------- | ----- |
+| `-g, --global`                       | Yes                   | Yes                   | Yes          | Yes                   | Yes                   |       |
+| `--location <project\|user\|global>` | project, user, global | project, user, global | user, global | project, user, global | project, user, global |       |
+
+Yarn Classic user writes use native defaults.
+
+## Native Options
+
+For native options, see [npm config](https://docs.npmjs.com/cli/v11/commands/npm-config), [pnpm config](https://pnpm.io/cli/config), [Yarn config](https://yarnpkg.com/cli/config), [Yarn config get](https://yarnpkg.com/cli/config/get), [Yarn config set](https://yarnpkg.com/cli/config/set), [Yarn config unset](https://yarnpkg.com/cli/config/unset), and [Yarn Classic config](https://classic.yarnpkg.com/en/docs/cli/config). Native options outside this interface require the native command.
+
+For `bunfig.toml` settings, see [Bun configuration](https://bun.com/docs/runtime/bunfig).

package/docs/guide/package-management/dedupe.md

@@ -0,0 +1,32 @@
+# vp dedupe
+
+Reduce duplicate dependency entries using the selected package manager.
+
+```bash
+vp dedupe
+vp dedupe --check
+```
+
+## Options
+
+| Option    | Description                                | Notes |
+| --------- | ------------------------------------------ | ----- |
+| `--check` | Check if deduplication would make changes. |       |
+
+## Compatibility
+
+- **npm:** `npm dedupe`.
+- **pnpm:** `pnpm dedupe`.
+- **Yarn Classic:** Fallback: `yarn install`.
+- **Yarn Modern:** `yarn dedupe`.
+- **Bun:** 1.4 or later: `bun dedupe`. Earlier versions use `bun install` as a fallback.
+
+| Option    | npm | pnpm | Yarn Classic | Yarn Modern | Bun          | Notes |
+| --------- | --- | ---- | ------------ | ----------- | ------------ | ----- |
+| `--check` | Yes | Yes  | No           | Yes         | 1.4 or later |       |
+
+A fallback install is not a read-only check. Unsupported `--check` requests fail before the fallback runs.
+
+## Native Options
+
+For native options, see [npm dedupe](https://docs.npmjs.com/cli/v11/commands/npm-dedupe), [pnpm dedupe](https://pnpm.io/cli/dedupe), [Yarn dedupe](https://yarnpkg.com/cli/dedupe), [Yarn Classic install](https://classic.yarnpkg.com/en/docs/cli/install), and [Bun dedupe](https://bun.com/docs/pm/cli/dedupe). For the Bun fallback, see [Bun install](https://bun.com/docs/pm/cli/install). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/deprecate.md

@@ -0,0 +1,39 @@
+# vp pm deprecate
+
+Set a deprecation message for a published package version or version range.
+
+```bash
+vp pm deprecate 'my-package@<2.0.0' 'Upgrade to version 2 or later'
+```
+
+## Options
+
+A package specification and a message are required.
+
+Deprecation warns consumers; it does not unpublish the package.
+
+| Option             | Description                 | Notes |
+| ------------------ | --------------------------- | ----- |
+| `--otp <otp>`      | Supply a one-time password. |       |
+| `--registry <url>` | Select the registry.        |       |
+
+## Compatibility
+
+- **npm:** `npm deprecate`.
+- **pnpm:** 11 or later: `pnpm deprecate`. Earlier versions use `npm deprecate` as a fallback.
+- **Yarn Classic:** Fallback: `npm deprecate`.
+- **Yarn Modern:** Fallback: `npm deprecate`.
+- **Bun:** Fallback: `npm deprecate`.
+
+| Option             | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes |
+| ------------------ | --- | ---- | ------------ | ----------- | --- | ----- |
+| `--otp <otp>`      | Yes | Yes  | Yes          | Yes         | Yes |       |
+| `--registry <url>` | Yes | Yes  | Yes          | Yes         | Yes |       |
+
+Bun emits a fallback warning. Registry configuration and authentication follow the command that runs.
+
+An empty message is forwarded unchanged. Native pnpm rejects it; Vite+ does not translate it to `undeprecate`.
+
+## Native Options
+
+For native options, see [npm deprecate](https://docs.npmjs.com/cli/v11/commands/npm-deprecate) and [pnpm deprecate](https://pnpm.io/cli/deprecate). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/dist-tag.md

@@ -0,0 +1,61 @@
+# vp pm dist-tag
+
+Manage the tags that map package names such as `my-package@next` to a published version.
+
+```bash
+vp pm dist-tag list my-package
+vp pm dist-tag add my-package@2.0.0 next
+vp pm dist-tag rm my-package next
+```
+
+## Options
+
+- `list [package]` lists tags. Alias: `ls`.
+- `add <package@version> <tag>` assigns a tag.
+- `rm <package> <tag>` removes a tag.
+
+There are no additional Vite+ options or native pass-through arguments on these subcommands. Changing a tag changes what future installs of that tag resolve to; it does not delete the published version.
+
+### `list`
+
+There are no command-specific options.
+
+### `add`
+
+There are no command-specific options.
+
+### `rm`
+
+There are no command-specific options.
+
+## Compatibility
+
+### `list`
+
+- **npm:** `npm dist-tag list`.
+- **pnpm:** 11 or later: `pnpm dist-tag list`. Earlier versions use `npm dist-tag list` as a fallback.
+- **Yarn Classic:** `yarn tag list`.
+- **Yarn Modern:** `yarn npm tag list`.
+- **Bun:** Fallback: `npm dist-tag list`.
+
+### `add`
+
+- **npm:** `npm dist-tag add`.
+- **pnpm:** 11 or later: `pnpm dist-tag add`. Earlier versions use `npm dist-tag add` as a fallback.
+- **Yarn Classic:** `yarn tag add`.
+- **Yarn Modern:** `yarn npm tag add`.
+- **Bun:** Fallback: `npm dist-tag add`.
+
+### `rm`
+
+- **npm:** `npm dist-tag rm`.
+- **pnpm:** 11 or later: `pnpm dist-tag rm`. Earlier versions use `npm dist-tag rm` as a fallback.
+- **Yarn Classic:** `yarn tag rm`.
+- **Yarn Modern:** `yarn npm tag rm`.
+- **Bun:** Fallback: `npm dist-tag rm`.
+
+On the native pnpm path, Vite+ does not fill in a missing package for `list`, resolve version ranges for `add`, or bypass restrictions on removing `latest`. pnpm validates these requests and returns its own errors.
+
+## Native Options
+
+For native options, see [npm dist-tag](https://docs.npmjs.com/cli/v11/commands/npm-dist-tag), [pnpm dist-tag](https://pnpm.io/cli/dist-tag), [Yarn npm tag list](https://yarnpkg.com/cli/npm/tag/list), [Yarn npm tag add](https://yarnpkg.com/cli/npm/tag/add), [Yarn npm tag remove](https://yarnpkg.com/cli/npm/tag/remove), and [Yarn Classic tag](https://classic.yarnpkg.com/en/docs/cli/tag). The upstream commands may expose additional options not accepted by this Vite+ interface.

package/docs/guide/package-management/dlx.md

@@ -0,0 +1,40 @@
+# vp dlx
+
+Download and run a package without adding it to the project's dependencies.
+
+```bash
+vp dlx create-vite my-app
+vp dlx --silent create-vite my-app
+```
+
+## Options
+
+Put Vite+ options before the package or command:
+
+Arguments after the command are passed to the executed program, not parsed as Vite+ options. Shell mode interprets shell syntax; use it only with trusted command strings.
+
+| Option                 | Description                                                            | Notes            |
+| ---------------------- | ---------------------------------------------------------------------- | ---------------- |
+| `-p, --package <name>` | Make the selected package available to the executed command.           | Can be repeated. |
+| `-c, --shell-mode`     | Execute within a shell environment.                                    |                  |
+| `-s, --silent`         | Suppress Vite+ output and request native quiet output where available. |                  |
+
+## Compatibility
+
+- **npm:** `npm exec --yes`.
+- **pnpm:** `pnpm dlx`.
+- **Yarn Classic:** Fallback: `npx --yes`.
+- **Yarn Modern:** `yarn dlx`.
+- **Bun:** `bun x`.
+
+| Option                 | npm | pnpm            | Yarn Classic | Yarn Modern | Bun | Notes                             |
+| ---------------------- | --- | --------------- | ------------ | ----------- | --- | --------------------------------- |
+| `-p, --package <name>` | Yes | Yes             | Yes          | Yes         | Yes |                                   |
+| `-c, --shell-mode`     | Yes | 7.21.0 or later | Yes          | No          | No  |                                   |
+| `-s, --silent`         | Yes | Yes             | Yes          | Yes         | Yes | Bun only suppresses Vite+ output. |
+
+For installed project binaries, use `vp exec` or `vpx` instead. See [Running Binaries](/guide/vpx) for those workflows.
+
+## Native Options
+
+For native options, see [npm exec](https://docs.npmjs.com/cli/v11/commands/npm-exec), [pnpm dlx](https://pnpm.io/cli/dlx), [Yarn dlx](https://yarnpkg.com/cli/dlx), and [Bun x](https://bun.com/docs/pm/bunx). For the Yarn Classic fallback, see [npx](https://docs.npmjs.com/cli/v11/commands/npx). For argument handling, see [Native Arguments](./#native-arguments).

package/docs/guide/package-management/fund.md

@@ -0,0 +1,32 @@
+# vp pm fund
+
+Show funding information for installed dependencies.
+
+```bash
+vp pm fund
+vp pm fund --json
+```
+
+## Options
+
+| Option   | Description                 | Notes                             |
+| -------- | --------------------------- | --------------------------------- |
+| `--json` | Request native JSON output. | Output retains the native schema. |
+
+## Compatibility
+
+- **npm:** `npm fund`.
+- **pnpm:** Fallback: `npm fund`.
+- **Yarn Classic:** Fallback: `npm fund`.
+- **Yarn Modern:** Fallback: `npm fund`.
+- **Bun:** Fallback: `npm fund`.
+
+| Option   | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes |
+| -------- | --- | ---- | ------------ | ----------- | --- | ----- |
+| `--json` | Yes | Yes  | Yes          | Yes         | Yes |       |
+
+Bun emits a fallback warning. Results follow npm's view of the installed dependencies.
+
+## Native Options
+
+For native options, see [npm fund](https://docs.npmjs.com/cli/v11/commands/npm-fund), which Vite+ uses for all package managers. To pass these options through Vite+, see [Native Arguments](./#native-arguments).