vite-plus 1.4.0 → 1.5.1

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.4.0",
+      "version": "1.5.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.4.0",
+      "version": "1.5.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@ export const toolchain = {
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.5",
+      "version": "8.3.7",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.15",
+      "version": "1.2.18",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@ export const toolchain = {
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.5",
+      "version": "5.1.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.89.0",
+      "version": "1.91.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.74.0",
+      "version": "0.76.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@ export const toolchain = {
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2004",
+      "version": "7.0.2005",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@ export const toolchain = {
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.23.1",
+      "version": "0.23.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -99,8 +99,8 @@ export const toolchain = {
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "a3c087a771a116f7c60220fc72738703eb45ac2e",
-      "builtAt": "2026-10-23T02:30:38Z",
+      "revision": "40cb9cac46bddbf8aa5ce5373df1a6a1980acc38",
+      "builtAt": "2026-11-09T12:28:42Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.155.0",
+      "version": "0.156.0",
       "kind": "engine",
       "delivery": [
         "compiled"
@@ -130,8 +130,8 @@ export const toolchain = {
     {
       "id": "oxc-node",
       "name": "oxc-node",
-      "version": "1.0.0",
-      "revision": "4759cedbda87f67ca646d3277166884cfcd62f81",
+      "version": "1.0.1",
+      "revision": "7ff14c3b1d15e2ef12310ee209d0b72b58fa880e",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.4.0",
+      "version": "1.5.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.4.0",
+      "version": "1.5.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.5",
+      "version": "8.3.7",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.15",
+      "version": "1.2.18",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.5",
+      "version": "5.1.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.89.0",
+      "version": "1.91.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.74.0",
+      "version": "0.76.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2004",
+      "version": "7.0.2005",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.23.1",
+      "version": "0.23.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -99,8 +99,8 @@
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "a3c087a771a116f7c60220fc72738703eb45ac2e",
-      "builtAt": "2026-10-23T02:30:38Z",
+      "revision": "40cb9cac46bddbf8aa5ce5373df1a6a1980acc38",
+      "builtAt": "2026-11-09T12:28:42Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.155.0",
+      "version": "0.156.0",
       "kind": "engine",
       "delivery": [
         "compiled"
@@ -130,8 +130,8 @@
     {
       "id": "oxc-node",
       "name": "oxc-node",
-      "version": "1.0.0",
-      "revision": "4759cedbda87f67ca646d3277166884cfcd62f81",
+      "version": "1.0.1",
+      "revision": "7ff14c3b1d15e2ef12310ee209d0b72b58fa880e",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/{tsconfig-LE_mAwe_.js → tsconfig-D3DiCiW6.js}

@@ -1,8 +1,8 @@
-import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-DRUnJ_Dz.js";
+import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-DLpJGhfK.js";
 import { c as modify, l as parse, o as applyEdits } from "./json-kl84kDyH.js";
 import { t as vitest_v5_entry_points_default } from "./vitest-v5-entry-points-NyJsFeux.js";
-import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-GL1vj0wk.js";
 import { i as runCommandSilently, n as getVpCommand } from "./command-rY79K5NI.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-D5f7inVN.js";
 import path from "node:path";
 import { styleText } from "node:util";
 import fs from "node:fs";

package/dist/{tsconfig-Do6MAG_f.js → tsconfig-DLERIAbF.js}

@@ -1 +1 @@
-export { i as fixBaseUrlInTsconfig, a as hasBaseUrlInTsconfig } from "./tsconfig-LE_mAwe_.js";
+export { i as fixBaseUrlInTsconfig, a as hasBaseUrlInTsconfig } from "./tsconfig-D3DiCiW6.js";

package/dist/version.js

@@ -1,7 +1,7 @@
+import { y as version } from "./constants-D5f7inVN.js";
 import { t as renderCliDoc } from "./help-B03t_iQ4.js";
+import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-DLUCo6L_.js";
 import { i as log, o as printHeader, t as accent } from "./terminal-BcuPUy-j.js";
-import { y as version } from "./constants-DRUnJ_Dz.js";
-import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-DzsomcUD.js";
 import path from "node:path";
 import { pathToFileURL } from "node:url";
 import fs from "node:fs";

package/dist/versions.js

@@ -1,9 +1,9 @@
 export const versions = {
-  "vite": "8.3.5",
-  "rolldown": "1.2.15",
-  "vitest": "5.0.5",
-  "oxfmt": "0.74.0",
-  "oxlint": "1.89.0",
-  "oxlint-tsgolint": "7.0.2004",
-  "tsdown": "0.23.1"
+  "vite": "8.3.7",
+  "rolldown": "1.2.18",
+  "vitest": "5.1.0",
+  "oxfmt": "0.76.0",
+  "oxlint": "1.91.0",
+  "oxlint-tsgolint": "7.0.2005",
+  "tsdown": "0.23.4"
 };

package/docs/config/check.md

@@ -2,6 +2,8 @@
 
 `vp check` runs format, lint, and type checks together. The `check` block in `vite.config.ts` sets defaults for the composite command, mirroring the `--no-fmt` and `--no-lint` CLI flags.
 
+See [Check usage](/guide/check#usage) for the execution order and how to skip formatting after a failure.
+
 This is useful when a project wants to keep most of the toolchain but skip one step by default. For example, a team that lints but does not format can disable `check.fmt` so a plain `vp check` (the command agents and contributors run most) only lints, without anyone needing to remember `--no-fmt`.
 
 ## Example

package/docs/config/fmt.md

@@ -21,4 +21,4 @@ export default defineConfig({
 
 For file- or package-specific formatting settings, use [`fmt.overrides`](/guide/monorepo#format-overrides) from the root `vite.config.ts`.
 
-Oxfmt disables nested configs in Vite+ mode, so nested format configs do not override settings for individual files. See [troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details.
+Oxfmt disables nested configs in Vite+ mode, so nested format configs do not override settings for individual files. See [Troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details.

package/docs/config/lint.md

@@ -27,4 +27,4 @@ We recommend enabling both `options.typeAware` and `options.typeCheck` so `vp li
 
 For file- or package-specific lint rules, use [`lint.overrides`](/guide/monorepo#root-config-with-overrides) from the root `vite.config.ts`.
 
-Oxlint disables nested configs in Vite+ mode, so nested lint configs do not override settings for individual files. See [troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details.
+Oxlint disables nested configs in Vite+ mode, so nested lint configs do not override settings for individual files. See [Troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details.

package/docs/config/run.md

@@ -90,7 +90,11 @@ Use the object form when a task needs other fields like `cache`, `dependsOn`, or
 
 - **Type:** `string | string[]`
 
-Defines the shell command to run for the task. The string is interpreted by a shell, so spaces, quoting, `&&`, pipes, and redirects all work as written on the command line.
+Defines the command to run for the task.
+
+::: info
+Vite Task parses simple commands and `&&` chains itself instead of passing them to a shell, so they behave the same on every platform. Other shell syntax, such as pipes or redirects, may behave differently across platforms.
+:::
 
 ```ts [vite.config.ts]
 tasks: {
@@ -117,7 +121,7 @@ tasks: {
 
 Each task defined in `vite.config.ts` must include its own `command`. You cannot define a task in both `vite.config.ts` and `package.json` with the same task name.
 
-Commands joined with `&&` (or supplied as an array) are automatically split into independently cached sub-tasks. See [Compound Commands](/guide/run#compound-commands).
+Array entries, and `&&` chains without other shell syntax, are automatically split into independently cached sub-tasks. See [Compound Commands](/guide/run#compound-commands).
 
 ### `dependsOn`
 

package/docs/config/staged.md

@@ -1,6 +1,6 @@
 # Staged Config
 
-`vp staged` reads staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit hooks guide](/guide/commit-hooks).
+`vp staged` reads staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit Hooks](/guide/commit-hooks).
 
 ## Example
 

package/docs/guide/check.md

@@ -22,6 +22,10 @@ vp check --no-lint          # Skip lint rules; keep type-check when enabled.
 vp check --no-fmt --no-lint # Type-check only (requires both `typeAware` and `typeCheck` enabled).
 ```
 
+If formatting fails, `vp check` stops before lint and type checks run. To fix formatting and apply available lint fixes, run `vp check --fix`. This command changes files. To skip formatting and run the remaining enabled checks, run `vp check --no-fmt`.
+
+Put `vp check` flags before file paths. For example, use `vp check --fix src/index.ts`. Arguments after the first path go to the format and lint tools instead of `vp check`.
+
 ## Configuration
 
 `vp check` uses the same configuration you already define for linting and formatting:
@@ -61,4 +65,4 @@ export default defineConfig({
 });
 ```
 
-These options only affect `vp check`; standalone `vp fmt` and `vp lint` still run normally. A step is skipped if it is disabled in config or the matching `--no-fmt` / `--no-lint` flag is passed. Because the defaults apply to every `vp check` run, a pre-commit hook that calls `vp check` will skip the disabled step too. See [Check config](/config/check) for the full reference.
+These options only affect `vp check`; standalone `vp fmt` and `vp lint` still run normally. A step is skipped if it is disabled in config or the matching `--no-fmt` / `--no-lint` flag is passed. Because the defaults apply to every `vp check` run, a pre-commit hook that calls `vp check` will skip the disabled step too. See [Check Config](/config/check) for the full reference.

package/docs/guide/ci.md

@@ -14,11 +14,11 @@ Run `vp migrate` to replace exact `voidzero-dev/setup-vp@v1` references in GitHu
 
 ## Node.js During Installation
 
-The Vite+ installer uses the latest Node.js LTS by default. With versions that support [`VP_SETUP_NODE_VERSION`](/guide/global-cli#vp-setup-node-version), `setup-vp` can use the project's version for installation too. This avoids a second Node.js download when that version supports both the global CLI and its pinned `pnpm`.
+The Vite+ installer uses the Node.js version pinned in the repository's [`.node-version`](https://github.com/voidzero-dev/vite-plus/blob/main/.node-version) by default. Each Vite+ release embeds this version at build time. The dependency-upgrade workflow keeps this pin up to date. With versions that support [`VP_SETUP_NODE_VERSION`](/guide/global-cli#vp-setup-node-version), `setup-vp` can use the project's version for installation too. This avoids a second Node.js download when that version supports both the global CLI and its pinned `pnpm`.
 
 `setup-vp` selects the version before it starts the installer. An explicit Node.js version takes precedence over a version-file input. Without either input, it checks the working directory and its parents using the [project declaration order](/guide/env#node-js-selection). The integration passes the selection through `VP_SETUP_NODE_VERSION`; the installer itself does not read project declarations.
 
-Without a selection, with Node.js management disabled, or when the selected version is incompatible, installation uses LTS. Older installers keep their existing behavior. Automatic project discovery does not create a session override, so later commands retain normal directory-based version selection.
+Without a selection, with Node.js management disabled, or when the selected version is incompatible, installation uses the embedded default. Older installers keep their existing behavior. Automatic project discovery does not create a session override, so later commands retain normal directory-based version selection.
 
 The integration handles these installer variables automatically. Configure `node-version` or `node-version-file` in GitHub Actions and GitLab CI/CD, or `nodeVersion` or `nodeVersionFile` in Azure Pipelines. See the [`setup-vp` documentation](https://github.com/voidzero-dev/setup-vp#inputs) for the complete input reference.
 

package/docs/guide/create.md

@@ -95,7 +95,7 @@ Run `vp create --list` to see the built-in templates and the common shorthand te
 `--git` and `--no-git` are not available when adding a package to an existing monorepo.
 :::
 
-After create, manage the dispatcher with `vp hooks status`, `vp hooks disable`, and `vp hooks enable`. See the [Commit hooks guide](/guide/commit-hooks).
+After create, manage the dispatcher with `vp hooks status`, `vp hooks disable`, and `vp hooks enable`. See the [Commit Hooks](/guide/commit-hooks).
 
 ### Dependency build scripts
 

package/docs/guide/env.md

@@ -41,7 +41,7 @@ To select the project's Node.js version, Vite+ checks the current directory firs
 
 If no directory declares a version, Vite+ uses the global default (`vp env default`) and then the latest LTS.
 
-These rules select Node.js for project commands. The installer uses the latest LTS by default. Only [`VP_SETUP_NODE_VERSION`](/guide/global-cli#vp-setup-node-version) changes its dependency-installation runtime; [`setup-vp`](/guide/ci#node-js-during-installation) supplies this override from the CI inputs or project declarations.
+The `lts` alias selects the newest LTS release. The `latest` alias selects the newest stable release, LTS or not, and skips pre-releases such as `27.0.0-alpha.0.0.0`. To use a pre-release, specify its exact version.
 
 `devEngines.runtime` ranks above `engines.node` because it declares the development-environment requirement, while `engines.node` is a consumer-facing support range. `vp env doctor` warns when declared sources conflict.
 

package/docs/guide/global-cli.md

@@ -71,7 +71,9 @@ irm https://vite.plus/ps1 | iex
 
 On Windows, you can instead download and run [`vp-setup.exe`](https://setup.viteplus.dev).
 
-The installer uses the latest Node.js LTS to install its JavaScript dependencies. CI integrations can select another compatible version through [`VP_SETUP_NODE_VERSION`](#vp-setup-node-version).
+For macOS and Linux, see the [Homebrew tap guide](/guide/homebrew) for installation instructions.
+
+The installer uses the Node.js version pinned in the Vite+ repository's [`.node-version`](https://github.com/voidzero-dev/vite-plus/blob/main/.node-version) to install its JavaScript dependencies. Each Vite+ release embeds this version at build time. Development and CI use the same file, which the dependency-upgrade workflow keeps up to date. CI integrations can select another compatible version through [`VP_SETUP_NODE_VERSION`](#vp-setup-node-version).
 
 After installation, open a new shell and run:
 
@@ -111,14 +113,14 @@ These variables control the installer scripts and the standalone Windows install
 
 - **Purpose**: Select the Node.js version used to install the global CLI's JavaScript dependencies. CI integrations such as [`setup-vp`](/guide/ci#node-js-during-installation) set this variable to reuse the project's runtime.
 - **Values**: An exact version, a version range, or an alias such as `22.23.1`, `22`, `^22.18.0`, `lts`, or `latest`. The installer resolves the value once to an exact version.
-- **Default**: Unset or empty (use the latest Node.js LTS). Project files, `VP_NODE_VERSION`, session overrides, and the user-level default do not change this default.
-- **Compatibility**: The resolved version must meet the Node.js requirements of both the global CLI and its pinned `pnpm`. Otherwise, the installer uses LTS. An invalid or unresolvable value causes an error.
-- **Scope**: Initial dependency installation only. This variable does not set a project pin, session override, or global default. `vp upgrade` and legacy installers continue to use LTS.
+- **Default**: Unset or empty (use the embedded Node.js default). Project files, `VP_NODE_VERSION`, session overrides, and the user-level default do not change this default.
+- **Compatibility**: The resolved version must meet the Node.js requirements of both the global CLI and its pinned `pnpm`. Otherwise, the installer uses the embedded default. An invalid or unresolvable value causes an error.
+- **Scope**: Initial dependency installation only. This variable does not set a project pin, session override, or global default. [`vp upgrade`](/guide/upgrade#global-vp) does not use this variable.
 
 #### `VP_SETUP_NODE_VERSION_FILE`
 
 - **Purpose**: Optional output file for integrations that need the exact version resolved from `VP_SETUP_NODE_VERSION`.
-- **Contents**: The resolved version, such as `22.23.1`, written after successful dependency installation. If compatibility requires LTS for installation, the file still contains the requested version's resolution.
+- **Contents**: The resolved version, such as `22.23.1`, written after successful dependency installation. If compatibility requires the embedded default for installation, the file still contains the requested version's resolution.
 - **Default**: Unset (write no file). The installer also writes no file when `VP_SETUP_NODE_VERSION` is unset or empty, or when dependency installation is skipped.
 
 `setup-vp` manages this file automatically. Use its Node.js inputs to configure CI jobs.
@@ -426,7 +428,7 @@ For example, `VP_VERSION=1.0.0 vp-setup.exe --version 2.0.0` installs version 2.
 
 ### Homebrew
 
-For a Homebrew installation, the first `vp` command sets up your shell, shims, and environment-management preferences. It reuses Homebrew's binary and bundled JavaScript. Setup stores its completion state in your user directories and does not need write access to the Homebrew prefix.
+The [official Homebrew tap](/guide/homebrew) installs the native CLI. The first `vp` command installs matching JavaScript dependencies in your data directory and sets up your shell, shims, and environment-management preferences. Setup stores its state in your directories without writing to the Homebrew prefix.
 
 Later commands reuse that setup while the installed binary remains unchanged. Generated shims follow Homebrew's public `vp` entrypoint when Homebrew replaces a version. Setup preserves your saved management preferences during this replacement.
 
@@ -436,11 +438,13 @@ To prefer your existing Node.js and package managers during the first run, use:
 VP_NODE_MANAGER=no VP_PM_MANAGER=no vp help
 ```
 
-After setup, use `vp env off` to change this preference. Commands that need missing runtimes or project dependencies can still download them.
+After setup, use `vp env off` to change this preference. The tap still prepares its pinned Node.js and pnpm to install CLI dependencies. Commands that need missing runtimes or project dependencies can also download them.
 
 Use Homebrew to [upgrade](/guide/upgrade#homebrew) or [remove](/guide/implode#homebrew) its package.
 
-`vp env doctor` identifies the Homebrew installation and its binary path. It checks the `vp` command and the user shim directory on `PATH` separately. If only the shim directory is missing, follow its shell setup instructions to enable the shims.
+`vp env doctor` identifies the Homebrew source, formula name, and binary path. It checks the `vp` command and the user shim directory on `PATH` separately. If only the shim directory is missing, follow its shell setup instructions to enable the shims.
+
+See the [official tap guide](/guide/homebrew) for registry configuration and migration instructions.
 
 ## Use It Without a Local Package
 
@@ -481,7 +485,7 @@ To see which toolchain is selected for your current project, run `vp toolchain`.
 ## Next Steps
 
 - [Environment](/guide/env) covers Node.js and package-manager selection, pinning, shims, and managed installations.
-- [Package Management](/guide/package-management) covers pnpm, npm, Yarn, and Bun workflows.
+- [Package Management](/guide/package-management/) covers pnpm, npm, Yarn, and Bun workflows.
 - [Run](/guide/run) covers package scripts and cached workspace tasks.
 - [Upgrading Vite+](/guide/upgrade) explains global CLI upgrades. See [Update Vite+](/guide/upgrade-project) for project-local upgrades.
 - [Removing Vite+](/guide/implode) removes the global binary and its managed data.

package/docs/guide/homebrew.md

@@ -0,0 +1,127 @@
+# Homebrew tap
+
+The official tap supports macOS and glibc Linux on ARM64 and x64. Homebrew manages the native `vp` executable; `vp` manages its JavaScript dependencies, downloaded Node.js versions, package managers, and settings in your user directories.
+Stable installation downloads the executable and its dependency lockfile from GitHub Releases. This step needs no existing Node.js or package manager installation, or npm registry access.
+
+## Install
+
+Install the tap:
+
+```bash
+brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
+brew install voidzero-dev/vite-plus/vp
+vp
+```
+
+The explicit repository URL is required because the formula is part of the Vite+ repository.
+If you already use Vite+, follow the [migration steps](#switch-an-existing-installation).
+
+## First use
+
+On first use, `vp` installs its matching CLI dependencies and configures your shell and tool-management preferences. This step needs access to Node.js downloads and your npm registry.
+Setup uses the release's pinned Node.js and pnpm versions, even if you choose to prefer system tools. A compatible [`VP_SETUP_NODE_VERSION`](/guide/global-cli#vp-setup-node-version) can override the installation runtime without changing Node.js selection for your projects.
+`vp` stores dependencies in `<DATA>/cli-packages/<version>/<platform>`.
+`<DATA>` comes from the [Vite+ directory configuration](/guide/global-cli#installation-variables).
+
+Open a new terminal after setup so the shims are available on `PATH`. Later invocations reuse the completed setup.
+Use [`vp env on` and `vp env off`](/guide/env) to change which tools `vp` manages.
+
+## Custom npm registry
+
+First-run setup reads `~/.npmrc`, including npm-compatible authentication:
+
+```ini
+registry=https://registry.example.com/repository/npm/
+//registry.example.com/repository/npm/:_authToken=${NPM_TOKEN}
+```
+
+Export `NPM_TOKEN` before running `vp`. The native pnpm downloader and pnpm dependency installation both use this configuration.
+You can select another file with `NPM_CONFIG_USERCONFIG` or override the registry with `NPM_CONFIG_REGISTRY`.
+Relative user-config paths resolve from your current directory. No Homebrew-specific npm variables are required.
+
+Authentication failures stop setup. Fix the configuration and run `vp` again; setup preserves your management choices.
+
+## Recover from failed setup
+
+Run `vp env doctor` to inspect the executable, dependency directory, and shims. Its CLI dependency check reads local files and does not install or repair dependencies. Other checks can fetch Node.js version metadata.
+
+Fix the reported configuration, access, or disk-space problem, then run `vp --help` to retry setup.
+For a lockfile error, the [installer recovery option](/guide/global-cli#vp-setup-skip-install-lockfile) also works with Homebrew:
+
+```bash
+VP_SETUP_SKIP_INSTALL_LOCKFILE=1 vp --help
+```
+
+This resolves dependencies without the published lockfile. A later invocation without the override restores the normal lockfile checks and can reinstall those dependencies.
+If pnpm fails, the reported log contains its exit code and recognized error codes, without raw package-manager output.
+Configured tool shims can run cached Node.js, package managers, and global packages independently of CLI dependency repair.
+
+## Switch an existing installation
+
+Keep your existing directory settings. Migration preserves your preferences, runtimes, and global packages, and updates their shims to Homebrew's public `vp` command.
+Do not run `vp implode`: it removes that user data. Open a new terminal after switching.
+
+### Switch from the script installer
+
+Run the `brew tap` and `brew install` commands above. Then invoke Homebrew's executable directly, so an existing script-install shim cannot take precedence:
+
+```bash
+"$(brew --prefix)/bin/vp" env setup --refresh
+```
+
+### Switch from Homebrew Core
+
+The `vite-plus` formula provides the same commands and must be removed before installing the tap:
+
+```bash
+brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
+brew uninstall vite-plus
+brew install voidzero-dev/vite-plus/vp
+"$(brew --prefix)/bin/vp" env setup --refresh
+```
+
+## Upgrade or remove
+
+```bash
+brew upgrade voidzero-dev/vite-plus/vp
+```
+
+Run `vp` after upgrading to prepare its matching dependencies. Setup preserves your preferences.
+`vp upgrade` identifies the official tap and directs you to `brew upgrade voidzero-dev/vite-plus/vp`.
+
+For complete removal, remove your user data before uninstalling the executable:
+
+```bash
+vp implode
+brew uninstall voidzero-dev/vite-plus/vp
+```
+
+`brew uninstall` alone keeps user data. On a shared machine, each operating-system account can remove its own data with `vp implode` before the executable is removed.
+
+## Test a preview build
+
+Set `HOMEBREW_VP_PR_VERSION` to a PR number or full commit SHA. The PR must have a published `preview-build` that includes Homebrew tap support. Use a full SHA to keep installation and verification on the same commit:
+
+```bash
+brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
+HOMEBREW_VP_PR_VERSION="<full-commit-sha>" brew install voidzero-dev/vite-plus/vp
+HOMEBREW_VP_PR_VERSION="<full-commit-sha>" brew test voidzero-dev/vite-plus/vp
+```
+
+Use `brew reinstall` instead of `brew install` to replace an installed tap build. If the `vite-plus` formula is installed, run `brew uninstall vite-plus` first; this keeps your user data.
+`brew test` uses temporary user data and does not change your shell configuration. Run `vp` afterward to set up the preview for your account. If switching from the script installer, [refresh its shims](#switch-from-the-script-installer) to use the Homebrew executable.
+
+Homebrew downloads only the native preview package from the registry bridge and verifies its checksum. It resolves PR numbers to the latest published commit, which can differ from the current PR head.
+First launch installs the matching dependencies from the bridge. An explicit `NPM_CONFIG_REGISTRY` must point to a registry that also serves those preview packages.
+
+The selector is specific to this tap. It does not change other Homebrew formulae, and no npm client is needed during `brew install`.
+To test changes to the formula itself, first check out the PR in the tap repository. Set `HOMEBREW_NO_AUTO_UPDATE=1` for these commands to keep that checkout.
+
+To return to a stable release, clear the overrides, restore the tap's `main` branch if you changed its checkout, and update it before reinstalling:
+
+```bash
+unset HOMEBREW_VP_PR_VERSION HOMEBREW_NO_AUTO_UPDATE
+git -C "$(brew --repository voidzero-dev/vite-plus)" switch main
+brew update
+brew reinstall voidzero-dev/vite-plus/vp
+```

package/docs/guide/ide-integration.md

@@ -63,9 +63,7 @@ You can also manually set up the Zed config:
       "initialization_options": {
         "settings": {
           "run": "onType",
-          "fixKind": "safe_fix",
-          "typeAware": true,
-          "unusedDisableDirectives": "deny"
+          "fixKind": "safe_fix"
         }
       }
     },

package/docs/guide/implode.md

@@ -26,13 +26,15 @@ vp implode --yes
 
 ## Homebrew
 
-Run `vp implode` first to remove Vite+-managed runtimes, global packages, configuration, shims, and shell entries. Then remove the Homebrew package:
+For the [official Homebrew tap](/guide/homebrew), run `vp implode` first to remove Vite+-managed runtimes, global packages, configuration, shims, and shell entries. Then remove the Homebrew package:
 
 ```bash
 vp implode
-brew uninstall vite-plus
+brew uninstall voidzero-dev/vite-plus/vp
 ```
 
-The confirmation prompt explains that the Homebrew package will remain installed. After cleanup, `vp implode` directs you to `brew uninstall vite-plus`.
+The confirmation prompt explains that the Homebrew package will remain installed. After cleanup, `vp implode` shows the uninstall command for the owning formula.
+
+To keep your data when switching installations, follow the [migration steps](/guide/homebrew#switch-an-existing-installation) instead of running `vp implode`.
 
 Restart your terminal before you run `vp` again. In Bash, you can run `hash -r` instead to clear cached command paths. If the Homebrew package is still installed, the next `vp` command starts first-run setup again.

package/docs/guide/index.md

@@ -100,9 +100,9 @@ Vite+ covers the full frontend development cycle, from starting a project throug
 
 - [`vp create`](/guide/create) creates new apps, packages, and monorepos.
 - [`vp migrate`](/guide/migrate) moves existing projects onto Vite+.
-- [`vp install`](/guide/package-management) installs dependencies with the right package manager.
-- [`vp add`](/guide/package-management), [`vp remove`](/guide/package-management), [`vp update`](/guide/package-management), [`vp dedupe`](/guide/package-management), [`vp outdated`](/guide/package-management), [`vp list`](/guide/package-management), [`vp why`](/guide/package-management), and [`vp info`](/guide/package-management) cover the rest of the package-management workflow.
-- [`vp link`](/guide/package-management), [`vp unlink`](/guide/package-management), [`vp rebuild`](/guide/package-management), and [`vp pm <command>`](/guide/package-management) provide lower-level package-manager operations.
+- [`vp install`](/guide/package-management/install) installs dependencies with the right package manager.
+- [`vp add`](/guide/package-management/add), [`vp remove`](/guide/package-management/remove), [`vp update`](/guide/package-management/update), [`vp dedupe`](/guide/package-management/dedupe), [`vp outdated`](/guide/package-management/outdated), [`vp list`](/guide/package-management/list), [`vp why`](/guide/package-management/why), and [`vp info`](/guide/package-management/info) cover the rest of the package-management workflow.
+- [`vp link`](/guide/package-management/link), [`vp unlink`](/guide/package-management/unlink), [`vp rebuild`](/guide/package-management/rebuild), and [`vp pm <command>`](/guide/package-management/) provide lower-level package-manager operations.
 
 ### Project Toolchain
 
@@ -115,7 +115,7 @@ Vite+ covers the full frontend development cycle, from starting a project throug
 - [`vp toolchain`](/guide/upgrade#show-the-toolchain) shows the active project toolchain; use `--global` to inspect the global installation instead.
 - [`vp run`](/guide/run) runs tasks across workspaces with caching.
 - [`vp cache clean`](/guide/cache) clears task cache entries.
-- [`vp exec`](/guide/vpx) runs local project binaries, while [`vp dlx`](/guide/vpx) and [`vpx`](/guide/vpx) download and run package binaries.
+- [`vp exec`](/guide/vpx) runs local project binaries, while [`vp dlx`](/guide/package-management/dlx) and [`vpx`](/guide/vpx) download and run package binaries.
 - [`vp config`](/guide/commit-hooks) installs the Git hook dispatcher and configures agent integration.
 - [`vp hooks`](/guide/commit-hooks) manages the Git hook dispatcher, and [`vp staged`](/guide/commit-hooks) runs checks on staged files.
 - [Monorepo Guide](/guide/monorepo) covers multi-package project structure and commands.