vite-plus 1.5.0 → 1.5.1

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

@@ -0,0 +1,62 @@
+# vp update
+
+Update project dependencies using the selected manager's update rules. Alias: `vp up`.
+
+```bash
+vp update
+vp update react
+vp update --latest
+vp update -g
+```
+
+## Options
+
+| Option                      | Description                                                                      | Notes                                                                        |
+| --------------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
+| `-L, --latest`              | Update to latest version (ignore semver range).                                  | Global mode clears recorded version ranges.                                  |
+| `-g, --global`              | Update global packages.                                                          | Requires the global CLI. Uses the [global package store](./global-packages). |
+| `--concurrency <number>`    | Number of global package updates to run in parallel.                             | Requires --global. Must be a positive integer.                               |
+| `--reinstall-node-mismatch` | Reinstall up-to-date global packages installed with a different Node.js version. | Requires --global.                                                           |
+| `--ignore-node-mismatch`    | Skip up-to-date global packages installed with a different Node.js version.      | Requires --global.                                                           |
+| `-r, --recursive`           | Update recursively in all workspace packages.                                    |                                                                              |
+| `--filter <pattern>`        | Select workspaces by pattern.                                                    | Can be repeated.                                                             |
+| `-w, --workspace-root`      | Include workspace root.                                                          |                                                                              |
+| `-D, --dev`                 | Select development dependencies.                                                 |                                                                              |
+| `-P, --prod`                | Select production dependencies.                                                  |                                                                              |
+| `-i, --interactive`         | Interactive mode.                                                                |                                                                              |
+| `--no-optional`             | Exclude optionalDependencies.                                                    |                                                                              |
+| `--no-save`                 | Request native no-save behavior.                                                 |                                                                              |
+| `--workspace`               | Update only dependencies available in the workspace.                             |                                                                              |
+
+## Compatibility
+
+The commands below describe project operations. Global mode is described under [Options](#options).
+
+- **npm:** `npm update`.
+- **pnpm:** `pnpm update`.
+- **Yarn Classic:** `yarn upgrade` or `yarn upgrade-interactive`.
+- **Yarn Modern:** `yarn up`.
+- **Bun:** `bun update`.
+
+| Option                      | npm              | pnpm | Yarn Classic | Yarn Modern                  | Bun          | Notes |
+| --------------------------- | ---------------- | ---- | ------------ | ---------------------------- | ------------ | ----- |
+| `-L, --latest`              | Global mode only | Yes  | Yes          | Yes                          | Yes          |       |
+| `-g, --global`              | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--concurrency <number>`    | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--reinstall-node-mismatch` | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `--ignore-node-mismatch`    | Yes              | Yes  | Yes          | Yes                          | Yes          |       |
+| `-r, --recursive`           | 8.1.0 or later   | Yes  | No           | Yes                          | 1.4 or later |       |
+| `--filter <pattern>`        | 7.14.0 or later  | Yes  | One filter   | No                           | 1.4 or later |       |
+| `-w, --workspace-root`      | 8.1.0 or later   | Yes  | No           | No                           | No           |       |
+| `-D, --dev`                 | Yes              | Yes  | No           | No                           | 1.4 or later |       |
+| `-P, --prod`                | 7 or later       | Yes  | Yes          | No                           | 1.4 or later |       |
+| `-i, --interactive`         | No               | Yes  | Yes          | Yes                          | Yes          |       |
+| `--no-optional`             | Yes              | Yes  | Yes          | No                           | 1.4 or later |       |
+| `--no-save`                 | Yes              | Yes  | No           | --recursive without --latest | Yes          |       |
+| `--workspace`               | No               | Yes  | No           | No                           | No           |       |
+
+To change a dependency's declared range on npm, use [add](./add) with a new version specification. Yarn Modern follows project-wide update semantics. Recursive mode without `--latest` re-resolves existing ranges without rewriting manifests; combining it with `--latest` uses ordinary `yarn up`.
+
+## Native Options
+
+For native options, see [npm update](https://docs.npmjs.com/cli/v11/commands/npm-update), [pnpm update](https://pnpm.io/cli/update), [Yarn up](https://yarnpkg.com/cli/up), [Yarn Classic upgrade](https://classic.yarnpkg.com/en/docs/cli/upgrade), [Yarn Classic upgrade-interactive](https://classic.yarnpkg.com/en/docs/cli/upgrade-interactive), and [Bun update](https://bun.com/docs/pm/cli/update). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

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

@@ -0,0 +1,36 @@
+# vp pm version
+
+Run the package manager's version command. This manages package versions, not the Vite+ version displayed by `vp --version`.
+
+```bash
+vp pm version patch
+vp pm version 2.0.0
+```
+
+## Options
+
+Supply a version or increment strategy such as `major`, `minor`, or `patch`. Omitting it retains the manager's native behavior, which may display information, prompt, or require a strategy.
+
+| Option   | Description                 | Notes                             |
+| -------- | --------------------------- | --------------------------------- |
+| `--json` | Request native JSON output. | Output retains the native schema. |
+
+## Compatibility
+
+- **npm:** `npm version`.
+- **pnpm:** `pnpm version`.
+- **Yarn Classic:** `yarn version`.
+- **Yarn Modern:** `yarn version`.
+- **Bun:** 1.2.18 or later: `bun pm version`. Earlier versions warn before the command is invoked.
+
+| Option   | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes |
+| -------- | --- | ---- | ------------ | ----------- | --- | ----- |
+| `--json` | Yes | Yes  | Yes          | No          | No  |       |
+
+Yarn Classic converts increment strategies to flags such as `--patch`. An explicit version becomes `--new-version <version>`. Other managers retain their native operand syntax.
+
+Version commands can modify manifests and lockfiles and may create Git commits or tags. Vite+ preserves the selected manager's behavior.
+
+## Native Options
+
+For native options, see [npm version](https://docs.npmjs.com/cli/v11/commands/npm-version), [pnpm version](https://pnpm.io/cli/version), [Yarn version](https://yarnpkg.com/cli/version), [Yarn Classic version](https://classic.yarnpkg.com/en/docs/cli/version), and [Bun pm version](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

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

@@ -0,0 +1,30 @@
+# vp pm whoami
+
+Show the account authenticated with the registry.
+
+```bash
+vp pm whoami
+vp pm whoami --registry https://registry.npmjs.org
+```
+
+## Options
+
+| Option             | Description          | Notes |
+| ------------------ | -------------------- | ----- |
+| `--registry <url>` | Select the registry. |       |
+
+## Compatibility
+
+- **npm:** `npm whoami`.
+- **pnpm:** 11 or later: `pnpm whoami`. Earlier versions use `npm whoami` as a fallback.
+- **Yarn Classic:** No command. Warns and exits successfully without performing the operation.
+- **Yarn Modern:** `yarn npm whoami`.
+- **Bun:** `bun pm whoami`.
+
+| Option             | npm | pnpm | Yarn Classic | Yarn Modern | Bun | Notes                                           |
+| ------------------ | --- | ---- | ------------ | ----------- | --- | ----------------------------------------------- |
+| `--registry <url>` | Yes | Yes  | No           | No          | Yes | Configure the registry in Yarn Modern settings. |
+
+## Native Options
+
+For native options, see [npm whoami](https://docs.npmjs.com/cli/v11/commands/npm-whoami), [pnpm whoami](https://pnpm.io/cli/whoami), [Yarn npm whoami](https://yarnpkg.com/cli/npm/whoami), and [Bun pm whoami](https://bun.com/docs/pm/cli/pm). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

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

@@ -0,0 +1,55 @@
+# vp why
+
+Explain why a dependency is installed. Alias: `vp explain`.
+
+```bash
+vp why react
+vp why react --json
+vp why react --filter web
+```
+
+## Options
+
+| Option                    | Description                                     | Notes                             |
+| ------------------------- | ----------------------------------------------- | --------------------------------- |
+| `--json`                  | Request native JSON output.                     | Output retains the native schema. |
+| `--long`                  | Show extended information.                      |                                   |
+| `--parseable`             | Show parseable output.                          |                                   |
+| `-r, --recursive`         | Check recursively across all workspaces.        |                                   |
+| `--filter <pattern>`      | Select workspaces by pattern.                   | Can be repeated.                  |
+| `-w, --workspace-root`    | Check in workspace root.                        |                                   |
+| `-P, --prod`              | Only production dependencies.                   |                                   |
+| `-D, --dev`               | Only dev dependencies.                          |                                   |
+| `--depth <depth>`         | Limit tree depth.                               |                                   |
+| `--no-optional`           | Exclude optional dependencies.                  |                                   |
+| `--exclude-peers`         | Exclude peer dependencies.                      |                                   |
+| `--find-by <finder_name>` | Use a finder function defined in .pnpmfile.cjs. |                                   |
+
+## Compatibility
+
+- **npm:** `npm explain`.
+- **pnpm:** `pnpm why`.
+- **Yarn Classic:** `yarn why`. With multiple package names, warns and checks only the first.
+- **Yarn Modern:** `yarn why`. With multiple package names, warns and checks only the first.
+- **Bun:** `bun why`.
+
+| Option                    | npm             | pnpm             | Yarn Classic | Yarn Modern | Bun | Notes                                  |
+| ------------------------- | --------------- | ---------------- | ------------ | ----------- | --- | -------------------------------------- |
+| `--json`                  | Yes             | Yes              | Yes          | Yes         | No  |                                        |
+| `--long`                  | No              | Yes              | No           | No          | No  |                                        |
+| `--parseable`             | No              | Yes              | No           | No          | No  |                                        |
+| `-r, --recursive`         | 7.14.0 or later | Yes              | No           | Yes         | No  |                                        |
+| `--filter <pattern>`      | 7.14.0 or later | Yes              | No           | No          | No  |                                        |
+| `-w, --workspace-root`    | No              | Yes              | No           | No          | No  |                                        |
+| `-P, --prod`              | No              | Yes              | No           | No          | No  |                                        |
+| `-D, --dev`               | No              | Yes              | No           | No          | No  |                                        |
+| `--depth <depth>`         | No              | Yes              | No           | No          | Yes |                                        |
+| `--no-optional`           | No              | Yes              | No           | No          | No  |                                        |
+| `--exclude-peers`         | No              | Yes              | No           | Yes         | No  | Yarn Modern includes peers by default. |
+| `--find-by <finder_name>` | No              | 10.16.0 or later | No           | No          | No  |                                        |
+
+The dependency graph does not include tools Vite+ bundles or compiles. For readable output, Vite+ shows a hint when it also provides the requested package. Use `vp toolchain [tool]` to inspect bundled tools.
+
+## Native Options
+
+For native options, see [npm explain](https://docs.npmjs.com/cli/v11/commands/npm-explain), [pnpm why](https://pnpm.io/cli/why), [Yarn why](https://yarnpkg.com/cli/why), [Yarn Classic why](https://classic.yarnpkg.com/en/docs/cli/why), and [Bun why](https://bun.com/docs/pm/cli/why). To pass these options through Vite+, see [Native Arguments](./#native-arguments).

package/docs/guide/vpx.md

@@ -253,7 +253,7 @@ vp exec tsc --noEmit
 
 ## `vp dlx`
 
-Use `vp dlx` for one-off package execution without adding the package to your project dependencies.
+Use `vp dlx` for one-off package execution without adding the package to your project dependencies. See the [dlx command reference](/guide/package-management/dlx) for options and package-manager compatibility.
 
 ```bash
 vp dlx <package> [args...]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -358,19 +358,19 @@
     "oxfmt": "=0.76.0",
     "oxlint": "=1.91.0",
     "oxlint-tsgolint": "=7.0.2005",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.5.0",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.5.1",
     "vitest": "5.1.0"
   },
   "devDependencies": {
     "@emnapi/core": "2.0.0-beta.2",
     "@emnapi/runtime": "2.0.0-beta.2",
-    "@napi-rs/cli": "^3.10.0",
+    "@napi-rs/cli": "^3.10.12",
     "@nkzw/safe-word-list": "^3.1.0",
     "@types/cross-spawn": "^6.0.6",
     "@types/validate-npm-package-name": "^4.0.2",
     "@vitest/browser-playwright": "5.1.0",
     "@vitest/browser-webdriverio": "5.0.0",
-    "@voidzero-dev/vite-plus-prompts": "1.5.0",
+    "@voidzero-dev/vite-plus-prompts": "1.5.1",
     "@voidzero-dev/vite-task-client": "0.2.0",
     "bingo": "^0.13.2",
     "cac": "^7.1.0",
@@ -424,14 +424,14 @@
     "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "1.5.0",
-    "@voidzero-dev/vite-plus-darwin-x64": "1.5.0",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.5.0",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.5.0",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.5.0",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "1.5.0",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.5.0",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.5.0"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.5.1",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.5.1",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.5.1",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.5.1",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.5.1"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/docs/guide/package-management.md

@@ -1,269 +0,0 @@
-# Package Management
-
-`vp` detects and runs the current workspace's package manager. These commands are available from both the [global CLI](/guide/global-cli) and the [project-local CLI](/guide/local-cli).
-
-## Overview
-
-Use Vite+ to manage dependencies across pnpm, npm, Yarn, and Bun. Instead of switching between `pnpm install`, `npm install`, `yarn install`, and `bun install`, you can keep using `vp install`, `vp add`, `vp remove`, and the rest of the Vite+ package-management commands.
-
-Vite+ detects the package manager from the workspace root in this order:
-
-1. `packageManager` in `package.json`
-2. `devEngines.packageManager` in `package.json`
-3. `pnpm-workspace.yaml`
-4. `pnpm-lock.yaml`
-5. `yarn.lock` or `.yarnrc.yml`
-6. `package-lock.json`
-7. `bun.lock` or `bun.lockb`
-8. `.pnpmfile.cjs` or `pnpmfile.cjs`
-9. `bunfig.toml`
-10. `yarn.config.cjs`
-
-If none of those files are present, `vp` falls back to `pnpm` by default. Vite+ automatically downloads the matching package manager and uses it for the command you ran, but package-manager detection never rewrites `package.json`. Use `vp env pin <package-manager>@<version>` when the project should declare an exact version explicitly.
-
-The [`devEngines.packageManager`](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines) field accepts a single object or an array of objects, and its `version` may be a semver range:
-
-```json
-{
-  "devEngines": {
-    "packageManager": {
-      "name": "pnpm",
-      "version": "^11.0.0",
-      "onFail": "download"
-    }
-  }
-}
-```
-
-A range resolves to an already-downloaded satisfying version when possible, otherwise to the latest satisfying version from the npm registry. The range itself stays the source of truth; Vite+ never freezes it into an exact `packageManager` pin. When both `packageManager` and `devEngines.packageManager` are declared, the `packageManager` field drives selection and Vite+ warns when it does not satisfy the devEngines constraint (`vp env doctor` shows details).
-
-Vite+ currently downloads the declared package manager (the `onFail: "download"` behavior); the other `onFail` values are accepted but not yet differentiated.
-
-The explicit `packageManager` field (or the `devEngines.packageManager` declaration) also affects matching package-manager shims. If a project has `packageManager: "npm@10.9.4"`, `npm` and `npx` use npm 10.9.4. Other generated aliases behave the same way: `pnpm`/`pnpx`/`pn`/`pnx`, `yarn`/`yarnpkg`, and `bun`/`bunx`. Mismatched tools are not translated; `npm` in a `pnpm` project still resolves as npm.
-
-## Usage
-
-```bash
-vp install
-```
-
-Common install flows:
-
-```bash
-vp install
-vp install --frozen-lockfile
-vp install --lockfile-only
-vp install --filter web
-vp install -w
-```
-
-`vp install` maps to the correct underlying install behavior for the detected package manager, including the right lockfile flags for pnpm, npm, Yarn, and Bun.
-
-## Global Packages
-
-::: info
-Global package operations with `-g` require the [global CLI](/guide/global-cli).
-:::
-
-Use the `-g` flag for installing, updating or removing globally installed packages:
-
-- `vp install -g <pkg>` installs a package globally
-- `vp install -g --node <version> <pkg>` installs a package globally with a specific Node.js version
-- `vp uninstall -g <pkg>` removes a global package
-- `vp update -g [pkg]` updates one global package or all of them
-- `vp list -g [pkg]` lists global packages
-- `vp outdated -g [pkg]` prints outdated packages
-
-Without `--node`, `vp install -g` uses the Node.js version resolved for the current directory, so a project's pin takes precedence over `vp env default`. See [Node.js Selection](/guide/env#node-js-selection).
-
-Updates keep the version spec a package was installed with: a package installed from a dist-tag (e.g. `vp install -g some-pkg@nightly`) updates to the newest version of that tag, and a version range stays within the range. Reinstall with a different spec (e.g. `vp update -g some-pkg@latest`) to switch, or pass `--latest` to `vp update -g` to move packages to the `latest` tag and clear their recorded specs. `vp outdated -g` reports both the newest version matching the recorded spec (`Wanted`) and the newest version on the `latest` tag.
-
-::: warning
-These commands do **NOT** interact with the underlying package manager's global installation directory.
-
-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`.
-:::
-
-## Managing Dependencies
-
-Vite+ provides all the familiar package management commands:
-
-- `vp install` installs the current dependency graph for the project
-- `vp add <pkg>` adds packages to `dependencies`, use `-D` for `devDependencies`
-- `vp remove <pkg>` removes packages
-- `vp update` updates dependencies
-- `vp dedupe` reduces duplicate dependency entries where the package manager supports it
-- `vp outdated` shows available updates
-- `vp list` shows installed packages
-- `vp why <pkg>` explains why a package is present
-- `vp info <pkg>` shows registry metadata for a package
-- `vp rebuild` rebuilds native modules (e.g. after switching Node.js versions)
-- `vp link` and `vp unlink` manage local package links
-- `vp dlx <pkg>` runs a package binary without adding it to the project
-- `vp pm <command>` provides additional package-management commands adapted to the detected package manager
-
-::: info
-The `vp list` and `vp rebuild` shortcuts are available only in the global CLI. With the [project-local CLI](/guide/local-cli), use `vp pm list` and `vp pm rebuild`.
-:::
-
-### Command Guide
-
-#### Install
-
-Use `vp install` when you want to install exactly what the current `package.json` and lockfile describe.
-
-- `vp install` is the standard install command
-- `vp install --frozen-lockfile` fails if the lockfile would need changes
-- `vp install --no-frozen-lockfile` allows lockfile updates explicitly
-- `vp install --lockfile-only` updates the lockfile without performing a full install
-- `vp install --prefer-offline` and `vp install --offline` prefer or require cached packages
-- `vp install --ignore-scripts` skips lifecycle scripts
-- `vp install --filter <pattern>` scopes install work in monorepos
-- `vp install -w` installs in the workspace root
-
-::: info
-Option support depends on the detected package manager and its version. Unsupported options cause `vp` to exit with an error before running the package-manager command.
-:::
-
-##### Git and remote tarball dependencies (npm v12+)
-
-npm v12 stops resolving git dependencies (`github:`, `git+https:`) and remote tarball URLs by default; such installs fail with `EALLOWGIT` / `EALLOWREMOTE`. Opt back in per project with npm's `allow-git` / `allow-remote` config.
-
-#### Global Install
-
-Use these commands when you want package-manager-managed tools available outside a single project.
-
-- `vp install -g typescript`
-- `vp uninstall -g typescript`
-- `vp update -g`
-- `vp list -g`
-- `vp outdated -g`
-
-#### Add and Remove
-
-Use `vp add` and `vp remove` for day-to-day dependency edits instead of editing `package.json` by hand.
-
-- `vp add react`
-- `vp add -D typescript vitest`
-- `vp add -O fsevents`
-- `vp add --save-peer react`
-- `vp add react --ignore-scripts`
-- `vp remove react`
-- `vp remove --filter web react`
-
-#### Update, Dedupe, and Outdated
-
-Use these commands to maintain the dependency graph over time.
-
-- `vp update` refreshes packages to newer versions
-- `vp outdated` shows which packages have newer versions available
-- `vp dedupe` asks the package manager to collapse duplicates where possible
-
-#### Inspect
-
-Use these when you need to understand the current state of dependencies.
-
-- `vp list` shows installed packages
-- `vp why react` explains why `react` is installed
-- `vp info react` shows registry metadata such as versions and dist-tags
-
-These commands show the packages that the package manager installed. They do not show tools that Vite+ bundles or compiles. Run `vp toolchain [tool]` to show these tools, including Vite, Rolldown, and Oxc. For readable output, `vp why` shows a hint when Vite+ also provides the package.
-
-#### Rebuild
-
-Use `vp rebuild` when native modules need to be recompiled, for example after switching Node.js versions or when a C/C++ addon fails to load.
-
-- `vp rebuild` rebuilds all native modules
-- `vp rebuild <package...>` rebuilds the listed packages only
-- `vp rebuild -- <args>` passes extra arguments to the underlying package manager
-
-```bash
-vp rebuild
-vp rebuild better-sqlite3 sharp
-vp rebuild -- --update-binary
-```
-
-`vp rebuild` is a shorthand for `vp pm rebuild`.
-
-With pnpm v10+, bare `vp rebuild` only rebuilds packages whose build scripts are listed in `onlyBuiltDependencies` (or approved via `pnpm approve-builds`); name the package explicitly to force a rebuild that bypasses the approval gate.
-
-#### Dependency build scripts (npm v12+)
-
-npm v12 skips dependency install scripts (`preinstall` / `install` / `postinstall`, including implicit `node-gyp` builds) unless the `allowScripts` field in package.json covers them; the install succeeds and npm warns about what it skipped. `vp pm approve-builds` manages that allowlist:
-
-- `vp pm approve-builds <pkg...>` approves the named packages (`npm approve-scripts`)
-- `vp pm approve-builds !<pkg...>` denies them (`npm deny-scripts`)
-- `vp pm approve-builds --all` approves everything currently pending
-- `vp pm approve-builds` lists the packages whose scripts are not yet covered
-
-Approval only records the allowlist: scripts an earlier install skipped do not run until you run `vp rebuild <pkg>`. With npm 11.16 - 11.x the same commands work, but npm treats the allowlist as advisory and still runs scripts.
-
-#### Advanced
-
-Use these when you need lower-level package-manager behavior.
-
-- `vp link` and `vp unlink` manage local development links
-- `vp dlx create-vite` runs a package binary without saving it as a dependency
-- `vp pm <command>` provides additional package-management commands adapted to the detected package manager.
-
-  - **Dependencies**: `ci`, `prune`, `list`, `rebuild`, `approve-builds`
-  - **Patching**: `patch`, `patch-commit`
-  - **Packaging and publishing**: `pack`, `version`, `publish`, `stage`, `dist-tag`, `deprecate`
-  - **Inspection**: `view`, `search`, `licenses`, `audit`, `fund`, `ping`
-  - **Authentication and access**: `login`, `logout`, `whoami`, `token`, `owner`, `team`
-  - **Configuration**: `config`, `cache`
-  - **Package manifest**: `pkg get`, `pkg set`, `pkg delete`, `pkg fix`
-
-  Command support depends on the package manager and its version. Run `vp pm --help` to list commands or `vp pm <command> --help` for available options.
-
-Examples:
-
-```bash
-vp pm config get registry
-vp pm cache clean -- --force
-vp pm audit --json
-```
-
-#### Package manifest
-
-`vp pm pkg` reads and updates fields in `package.json` using the detected package manager.
-
-```bash
-vp pm pkg get name
-vp pm pkg set scripts.build="vite build"
-vp pm pkg set private=true --json
-vp pm pkg delete scripts.build
-vp pm pkg fix
-```
-
-npm supports `get`, `set`, and `delete` from 7.20.0 and `fix` from 9.8.0. pnpm supports all four commands from 11.3.0, and Bun supports them through `bun pm pkg` from 1.2.19. Yarn and unsupported versions print a warning and exit successfully without changing the manifest, matching `vp pm patch`.
-
-Native behavior is preserved. For example, npm returns JSON from `get`, while pnpm prints a single string value without quotes by default. Use `--json` to request JSON output or to parse values passed to `set` as JSON. Additional native options can be passed after `--`. The corrections made by `fix` depend on the package manager.
-
-#### Staged publishing
-
-`vp pm stage` exposes [npm's staged publishing](https://docs.npmjs.com/staged-publishing) workflow: a build is uploaded to a staging area (no 2FA, CI-friendly), then a maintainer approves or rejects it from a trusted device (2FA). It adapts to the detected package manager.
-
-```bash
-vp pm stage publish              # upload the package to staging (no 2FA)
-vp pm stage list                 # list staged versions
-vp pm stage view <stage-id>      # inspect a staged version
-vp pm stage download <stage-id>  # download the staged tarball
-vp pm stage approve <stage-id>   # promote to the live registry (2FA)
-vp pm stage reject <stage-id>    # discard a staged version (2FA)
-```
-
-- pnpm (`pnpm stage`, requires pnpm ≥ 11.3) and npm (`npm stage`, requires npm ≥ 11.15 and Node ≥ 22.14) pass through directly.
-- Yarn 4.16.0 and later uses its npm plugin (`yarn npm publish --staged`, `yarn npm stage …`). The `view` and `download` subcommands, and `publish` with an explicit tarball or folder target, fall back to `npm stage`.
-- Yarn versions earlier than 4.16.0 and Bun fall back to `npm stage`.
-
-## Package-Manager Integrity Verification
-
-A `packageManager` pin can carry an integrity hash (`yarn@4.17.1+sha512.…`). `corepack use` writes that hash. Vite+ hashes the same artifact as Corepack:
-
-- the extracted CLI binary (`bin/yarn.js`) for Yarn 2 and later
-- the npm package tarball for npm, pnpm, and Yarn Classic
-
-Vite+ hashes the CLI once, when it installs Yarn, and records the pin it verified. A later command compares its own pin against that record. A pin that does not match the record fails the check, and the command stops. Corepack keeps the same kind of record for its own cache.