vite-plus 0.2.9 → 0.3.1

package/docs/guide/env.md

@@ -1,10 +1,23 @@
 # Environment
 
-`vp env` manages Node.js versions globally and per project.
+`vp env` manages the complete JavaScript environment: one Node.js runtime and one selected package manager. npm, pnpm, Yarn, and Bun are peer package-manager families.
 
 ## Overview
 
-Managed mode is on by default, so `node`, `npm`, and related shims resolve through Vite+ and pick the right Node.js version for the current project.
+Managed mode is on by default, so Node.js and configured package-manager shims resolve through Vite+ and pick the right versions for the current project. Fresh installers record managed mode for npm, pnpm, Yarn, and Bun after the user enables environment management.
+
+When an upgrade adds a package-manager shim that has no recorded mode, its first interactive invocation asks what to do only when the corresponding system binary is already on PATH. The current family defaults to managed mode; choosing a system tool or applying a choice to every family remains explicit. Non-interactive invocations use managed mode without recording a choice.
+
+Most commands operate on both components when no selector is given. Add `node`, `pm`, `npm`, `pnpm`, `yarn`, or `bun` to narrow the command. `pm` means all four families for listing and cleanup, but the single selected package manager for project operations.
+
+Unqualified versions remain Node.js versions for compatibility:
+
+```bash
+vp env pin 22.0.0               # Node.js only
+vp env pin pnpm@10.18.0         # pnpm only
+vp env pin node@24 pnpm@12      # Both components
+vp env pin 22.0.0 pnpm@10.18.0  # Also both components
+```
 
 Vite+ checks the current directory first, then walks up through its parents. The nearest directory
 with a supported declaration wins. Within each directory, sources are checked in this order:
@@ -19,9 +32,36 @@ latest LTS.
 
 `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.
 
-When a project declares `packageManager` (or `devEngines.packageManager`) in `package.json`, matching package-manager shims also use that package-manager version. For example, `packageManager: "npm@10.9.4"` makes both `npm` and `npx` run through npm 10.9.4. Alias pairs follow the installed package-manager shims: `npm`/`npx`, `pnpm`/`pnpx`, `yarn`/`yarnpkg`, and `bun`/`bunx`. Vite+ does not translate mismatched commands, so a project pinned to `pnpm` still lets `npm` fall back to the npm that comes with the resolved Node.js runtime.
+::: tip Using pnpm with Vite+ runtime management
+pnpm can also manage the runtime declared in `devEngines.runtime`. When both pnpm and Vite+ manage Node.js, they can download the same version separately or select different versions, causing inconsistent behavior between commands.
+
+If you want Vite+ to manage Node.js, pnpm 11+ supports disabling pnpm's automatic runtime management globally with [`runtimeOnFail`](https://pnpm.io/settings/cli#runtimeonfail):
+
+```bash
+pnpm config set --global runtimeOnFail ignore
+```
+
+This setting also disables pnpm's automatic management of other declared runtimes, including Bun and Deno. Consider whether any of your projects rely on that behavior before setting it globally.
+:::
+
+Package-manager selection uses this priority:
+
+1. Explicit command override
+2. `VP_PACKAGE_MANAGER` or the shell-session override
+3. Top-level `packageManager`
+4. `devEngines.packageManager`
+5. Lockfile or manager-specific configuration
+6. The named package manager's global default version
+7. The named shim's latest release
 
-By default, Vite+ stores its managed runtime and related files in `~/.vite-plus`. If needed, you can override that location with `VP_HOME`.
+A selected manager controls only its named shims. For example, pnpm controls `pnpm` and `pnpx`; invoking `npm` still resolves npm independently. Alias pairs are `npm`/`npx`, `pnpm`/`pnpx`, `yarn`/`yarnpkg`, and `bun`/`bunx`. Without a matching project selection, a named shim uses its configured default version and otherwise uses the latest release without prompting. The resolved version is cached for one hour and an expired cache remains available when the registry cannot be reached. The directly invoked npm shim keeps its Node-bundled fallback, while an explicit `vp env ... npm` family scope uses standalone npm's latest release.
+
+A fresh install uses the split platform layout by default. On Unix, Vite+
+stores managed runtimes and related files in `~/.local/share/vite-plus`. It
+stores executables in the Vite+-owned `~/.local/share/vite-plus/bin` directory.
+On Windows, Vite+ uses `%LOCALAPPDATA%\vite-plus\data` for data and
+`%LOCALAPPDATA%\vite-plus\bin` for executables. Vite+ does not move an existing
+`~/.vite-plus` install. `VP_HOME` puts all categories under one custom root.
 
 If you want to keep that behavior, run:
 
@@ -29,7 +69,14 @@ If you want to keep that behavior, run:
 vp env on
 ```
 
-This enables managed mode, where the shims always use the Vite+-managed Node.js installation.
+This enables managed mode for both components. Their modes can also be changed independently, including one package-manager family:
+
+```bash
+vp env on node
+vp env off pm
+vp env off pnpm
+vp env on bun
+```
 
 If you do not want Vite+ to manage Node.js first, run:
 
@@ -37,23 +84,27 @@ If you do not want Vite+ to manage Node.js first, run:
 vp env off
 ```
 
-This switches to system-first mode, where the shims prefer your system Node.js and only fall back to the Vite+-managed runtime when needed.
+This switches both components to system-first mode. Vite+ prefers system tools and falls back to managed installations. Mixed configurations compose: a system package-manager launcher receives the Node.js selected by the Node mode.
+
+Using `pm` records the selected mode for all currently supported package managers and replaces their individual choices. An unscoped `on` or `off` does the same while also changing Node.js. A family without a recorded mode remains undecided until its shim is first used or an `on` / `off` command configures it.
 
 ## Commands
 
 ### Setup
 
-- `vp env setup` creates or updates shims in `VP_HOME/bin` (and writes the per-shell setup scripts under `VP_HOME`)
-- `vp env on` enables managed mode so shims always use Vite+-managed Node.js
-- `vp env off` enables system-first mode so shims prefer system Node.js first
-- `vp env print` prints the shell snippet for the current session
+- `vp env setup` creates or updates the `node`, `npm`, `npx`, `pnpm`, `pnpx`, `yarn`, `yarnpkg`, `bun`, `bunx`, `vpx`, and `vpr` shims in the resolved bin directory. It writes shell setup scripts in the config directory.
+- `vp env on` / `vp env off` changes both modes; append `node`, `pm`, `npm`, `pnpm`, `yarn`, or `bun` to narrow the change
+- `vp env print` prints PATH setup for both components; append a selector to print one
 
 PowerShell needs to dot-source the generated setup script in the current shell before `vp env use` can affect only that shell session:
 
 ```powershell
-. "$env:USERPROFILE\.vite-plus\env.ps1"
+. "$env:APPDATA\vite-plus\env.ps1"
 ```
 
+If an older Vite+ install uses `%USERPROFILE%\.vite-plus`, source the `env.ps1`
+file in that directory instead.
+
 Add that line to the end of your PowerShell `$PROFILE` to apply it automatically in new shells. It does not require elevated privileges.
 
 Create the profile file if it does not already exist:
@@ -76,29 +127,31 @@ node --version
 vp-use --unset
 ```
 
-Only `vp env use` needs this alternate command. Other `vp env` commands work normally in Command Prompt. `vp env setup` creates `vp-use.cmd` under `VP_HOME/bin` on Windows.
+Only `vp env use` needs this alternate command. Other `vp env` commands work normally in Command Prompt. `vp env setup` creates `vp-use.cmd` in the bin directory on Windows.
 
-In CI, `vp env use` can still run without shell initialization. It writes a temporary session file under `VP_HOME` so later shim calls in the same job can resolve the selected Node.js version.
+In CI, `vp env use` can run without shell initialization. It writes a temporary
+Node.js or package-manager session file in the resolved state directory. Later
+shim calls in the same job use these files to resolve the same environment.
 
 ### Manage
 
-- `vp env default` sets or shows the global default Node.js version
-- `vp env pin` pins a Node.js version in the current directory: an existing `.node-version` keeps being updated; otherwise the pin is written to `package.json#devEngines.runtime`; `.node-version` is only created when the directory has no `package.json`. Use `--target node-version` or `--target dev-engines` to choose explicitly. An existing `engines.node` is never modified.
-- `vp env unpin` removes the pin from the same source `vp env pin` would write
-- `vp env use` sets a Node.js version for the current shell session
-- `vp env install` installs a Node.js version
-- `vp env uninstall` removes an installed Node.js version
-- `vp env clean` removes unused managed Node.js runtimes, all downloaded package managers, and the Corepack cache.
-- `vp env exec` runs a command with a specific Node.js version
-- `vp node` runs a Node.js script — shorthand for `vp env exec node`
+- `vp env default` shows the global Node.js default and each configured package-manager version. Bare versions set Node.js; qualified specs such as `pnpm@10.18.0` set that package manager's shim default without replacing the defaults for Bun, Yarn, or npm. `--unset` clears all defaults unless scoped.
+- `vp env pin` shows or writes project pins. Existing `.node-version` and top-level `packageManager` fields keep being updated for compatibility; otherwise Vite+ writes the matching `devEngines` entry. Use `--target node-version`, `--target dev-engines`, or `--target package-manager` to choose explicitly.
+- `vp env unpin` removes both effective pins by default; append a selector to remove one. Lower-priority declarations are not deleted.
+- `vp env use` activates the complete project environment. Explicit specs override selected components; `--unset` clears both unless scoped.
+- `vp env install` installs the complete resolved environment, a selected component, or explicit specs.
+- `vp env uninstall` removes explicit exact Node.js or qualified package-manager versions.
+- `vp env clean` removes unused installs. Use `clean node`, `clean pm`, or a concrete manager. Current and configured-default versions are preserved.
+- `vp env exec` runs a command in the resolved environment. Use `--node` and `--package-manager`; `--npm` is an alias for `--package-manager npm@…`.
+- `vp node` uses the resolved Node.js runtime and exposes the selected package-manager path to child processes.
 
 ### Inspect
 
 - `vp env current` shows the current resolved environment
 - `vp env doctor` runs environment diagnostics
 - `vp env which` shows which tool path will be used
-- `vp env list` shows locally installed Node.js versions
-- `vp env list-remote` shows available Node.js versions from the registry
+- `vp env list` shows separate Node.js, npm, pnpm, Yarn, and Bun sections; selectors narrow output
+- `vp env list-remote` fetches Node.js and all four PM registries concurrently; selectors narrow network work. `--lts` implicitly selects Node.js.
 
 ## Project Setup
 
@@ -110,50 +163,83 @@ In CI, `vp env use` can still run without shell initialization. It writes a temp
 
 ```bash
 # Setup
-vp env setup                  # Create shims for node, npm, npx, corepack
-vp env on                     # Use Vite+ managed Node.js
-vp env print                  # Print shell snippet for this session
+vp env setup                  # Create Node.js and package-manager shims
+vp env on                     # Manage Node.js and package managers
+vp env off pm                 # Prefer system package managers only
+vp env off pnpm               # Prefer system pnpm only
+vp env print                  # Print PATH setup for both components
 
 # Manage
-vp env pin lts                # Pin the project to the latest LTS release
-vp env install                # Install the version from .node-version, package.json, or .nvmrc
-vp env default lts            # Set the global default version
-vp env use 20                 # Use Node.js 20 for the current shell session
-vp env use --unset            # Remove the session override
-vp env clean                  # Remove unused managed caches
+vp env pin lts pnpm@10        # Pin both project components to exact versions
+vp env install                # Install the complete resolved environment
+vp env default node@24        # Set the global Node.js default
+vp env default pnpm@10        # Set pnpm's global default version
+vp env use 20 pnpm@10         # Override both components for this shell
+vp env use --unset pm         # Remove only the PM session override
+vp env clean                  # Remove unused managed Node.js and package manager versions
 
 # Inspect
 vp env current                # Show current resolved environment
 vp env current --json         # JSON output for automation
 vp env which node             # Show which node binary will be used
 vp env which npx              # Show pinned package-manager alias when packageManager matches
-vp env list-remote --lts      # List only LTS versions
+vp env list                   # Show every locally installed component
+vp env list node              # Show only Node.js installations
+vp env list-remote --lts      # List only Node.js LTS versions
 
 # Execute
-vp env exec --node lts npm i  # Execute npm with latest LTS
+vp env exec --node lts --package-manager pnpm@10 pnpm install
 vp env exec node -v           # Use shim mode with automatic version resolution
 vp node script.js             # Shorthand: run a Node.js script with the resolved version
 vp node -e "console.log(1+1)" # Shorthand: forward any node flag or argument
 ```
 
-## Corepack
-
-Vite+ creates a `corepack` shim by default, so corepack works without a system Node.js installation:
-
-- On Node.js 24 and earlier, the shim runs the corepack bundled with the resolved Node.js version.
-- On Node.js 25 and later, where corepack is no longer bundled, Vite+ installs corepack as a managed global package on first use. Only the `corepack` binary is linked; run `vp install -g corepack` yourself if you also want the package's pnpm/yarn launchers exposed directly.
-- If you install corepack explicitly with `vp install -g corepack`, that installation is always preferred.
-
-`corepack enable` normally creates `pnpm`/`yarn` launchers next to the corepack binary, which under Vite+ would not be on `PATH`. The shim fixes this by defaulting `--install-directory` to `VP_HOME/bin`, so after `corepack enable` the launchers are available everywhere and still resolve the project's Node.js and package-manager versions:
-
-```bash
-corepack enable               # pnpm and yarn now resolve via corepack
-corepack disable              # Remove the pnpm/yarn launchers again
+## JSON output
+
+The JSON output for `current`, `list`, and `list-remote` is organized by component. `current --json` returns sibling `node` and `package_manager` objects:
+
+```json
+{
+  "node": {
+    "version": "22.0.0",
+    "source": "devEngines.runtime",
+    "source_path": "/project/package.json",
+    "project_root": "/project",
+    "bin_path": "/home/.vite-plus/js_runtime/node/22.0.0/bin/node",
+    "installed": true,
+    "mode": "managed"
+  },
+  "package_manager": {
+    "name": "pnpm",
+    "version": "10.18.0",
+    "source": "packageManager",
+    "source_path": "/project/package.json",
+    "project_root": "/project",
+    "bin_paths": {
+      "pnpm": "/home/.vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpm",
+      "pnpx": "/home/.vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpx"
+    },
+    "installed": true,
+    "mode": "managed"
+  }
+}
 ```
 
-The launchers reference the corepack copy that created them. If that copy is later removed (for example by uninstalling the Node.js version it shipped with), rerun `corepack enable` to recreate them.
+`list --json` and `list-remote --json` group the component arrays:
+
+```json
+{
+  "node": [],
+  "package_managers": {
+    "npm": [],
+    "pnpm": [],
+    "yarn": [],
+    "bun": []
+  }
+}
+```
 
-Shims owned by Vite+ (`npm`, `npx`, and binaries installed with `vp install -g`) are protected: if corepack removes or replaces them, Vite+ restores them and prints a warning.
+Selectors omit unselected top-level fields or PM families. Registry listing is all-or-error: Vite+ prints no partial human or JSON result when any selected registry request fails.
 
 ## Custom Node.js Mirror
 

package/docs/guide/ide-integration.md

@@ -82,14 +82,26 @@ You can also manually set up the Zed config:
     "JavaScript": {
       "format_on_save": "on",
       "prettier": { "allowed": false },
-      "formatter": [{ "language_server": { "name": "oxfmt" } }],
-      "code_action": "source.fixAll.oxc"
+      "formatter": [
+        { "language_server": { "name": "oxfmt" } },
+        { "code_action": "source.fixAll.oxc" }
+      ]
+    },
+    "JSX": {
+      "format_on_save": "on",
+      "prettier": { "allowed": false },
+      "formatter": [{ "language_server": { "name": "oxfmt" } }]
     },
     "TypeScript": {
       "format_on_save": "on",
       "prettier": { "allowed": false },
       "formatter": [{ "language_server": { "name": "oxfmt" } }]
     },
+    "TSX": {
+      "format_on_save": "on",
+      "prettier": { "allowed": false },
+      "formatter": [{ "language_server": { "name": "oxfmt" } }]
+    },
     "Vue.js": {
       "format_on_save": "on",
       "prettier": { "allowed": false },

package/docs/guide/index.md

@@ -96,7 +96,7 @@ Vite+ can handle the entire local frontend development cycle from starting a pro
 - [`vp hooks`](/guide/commit-hooks) manages the Git hook dispatcher (`enable`, `disable`, `status`).
 - [`vp staged`](/guide/commit-hooks) runs checks on staged files.
 - [`vp install`](/guide/install) installs dependencies with the right package manager.
-- [`vp env`](/guide/env) manages Node.js versions.
+- [`vp env`](/guide/env) manages Node.js and package-manager environments.
 
 ### Develop
 

package/docs/guide/install.md

@@ -19,7 +19,9 @@ Vite+ detects the package manager from the workspace root in this order:
 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. When detection comes from lockfiles or config files, the resolved version is written to `devEngines.packageManager` so future runs are deterministic; projects that already declare `packageManager` or `devEngines.packageManager` are left as-is.
+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.
+
+After selecting the package manager, Vite+ forwards the command without separately validating whether `package.json` exists. Missing-manifest behavior therefore matches the selected package manager.
 
 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:
 
@@ -81,7 +83,8 @@ Updates keep the version spec a package was installed with: a package installed
 ::: warning
 These commands do **NOT** interact with the underlying package manager's global installation directory.
 
-Instead, Vite+ manages its own global packages under `VP_HOME/packages`, allowing them to remain available across different Node.js versions.
+Instead, Vite+ stores its global packages in `packages/` under the resolved data
+directory. These packages remain available across different Node.js versions.
 
 As a result, commands such as `vp link` do not affect Vite+'s global packages and will not appear in `vp list -g`.
 :::

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

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

package/docs/guide/migrate-rules.md

@@ -39,6 +39,52 @@ When a default upgrade skips setup actions that would apply, it prints a hint
 to run `vp migrate --full`. Fresh (non Vite+) projects always run the full
 migration.
 
+## Pack Configuration
+
+`vp migrate` updates static `pack` objects in `vite.config.*` and exported
+objects in `tsdown.config.*` for [tsdown 0.23](https://github.com/rolldown/tsdown/releases/tag/v0.23.0).
+This also runs on existing Vite+ projects without `--full`, including workspace
+packages. Arrays and direct objects returned by `defineConfig` callbacks are
+supported. JSON tsdown configs receive the same updates after they merge into
+`vite.config.ts`.
+
+| Previous option                                                    | Updated option                                                                        |
+| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------- |
+| `bundle: false`                                                    | `unbundle: true`                                                                      |
+| `bundle: true`                                                     | Removed; bundling remains the default                                                 |
+| `outExtension`                                                     | `outExtensions`                                                                       |
+| `publicDir`                                                        | `copy`                                                                                |
+| `removeNodeProtocol: true`                                         | `nodeProtocol: 'strip'`                                                               |
+| `injectStyle`                                                      | `css.inject`                                                                          |
+| `inlineOnly` / `deps.onlyAllowBundle`                              | `deps.onlyBundle`                                                                     |
+| `noExternal`                                                       | `deps.alwaysBundle`                                                                   |
+| `skipNodeModulesBundle: true` / `deps.skipNodeModulesBundle: true` | `deps.neverBundle: true`                                                              |
+| `dts.tsgo` / `dts.oxc`                                             | Select with `dts.generator`; retain generator option objects and remove boolean flags |
+| `dts.cjsReexport`                                                  | Removed; tsdown generates CJS declarations separately                                 |
+| `--public-dir` in `tsdown` or `vp pack` scripts                    | `--copy`                                                                              |
+
+Migration preserves the previous defaults by setting `deps.resolveDepSubpath`
+to `true` when absent. Enabled ATTW checks receive `profile: 'strict'` when
+no profile is set. Explicit values, including `false`, remain unchanged.
+
+`noExternal` moves to `deps.alwaysBundle`, preserving matcher expressions,
+references, and callback methods. Existing `deps.alwaysBundle` values remain
+unchanged.
+
+When `external` accompanies either `skipNodeModulesBundle` form, static matchers
+and references to local constants move to `inputOptions.external` before
+`deps.neverBundle` is set. Constant declarations and references stay intact.
+This preserves the original matching rules, including external file paths. Unsupported matchers,
+conflicting `inputOptions`, and declaration-specific dependency rules leave the
+pack object unchanged and produce a manual-migration warning.
+
+The transform does not evaluate configuration code. Objects with spreads,
+computed keys, or duplicate keys, and conflicting old and new options require
+manual review. Dynamic boolean selectors remain unchanged. Unrelated Vite and
+plugin options remain unchanged. Run `vp pack` after migration to check the
+result. Node.js requirements, TypeScript module resolution, and programmatic
+`build()` return values require separate review.
+
 ## Dependency Rules
 
 What happens to each toolchain dependency, at a glance:
@@ -82,6 +128,14 @@ Related rules:
 - A direct `vite` declaration is never removed merely because a root override
   exists.
 - Plain or stale aliases are normalized; named catalog references are kept.
+- Under pnpm the managed override keys use an explicit `@*` range (`vite@*`,
+  `vitest@*`). pnpm applies an override by replacing the declared spec on every
+  manifest, importer manifests included. A bare key matches any spec, including
+  `catalog:`, and `vp up` then rewrites that reference to a concrete version.
+  The `@*` range keeps the override on the semver ranges that transitive and
+  peer declarations use. It leaves `catalog:` references to the catalog, which
+  already resolves them to Vite+ core. Migration re-keys a project that still
+  holds the bare key, and keeps its named-catalog choice.
 - The direct-entry rule above is pnpm-specific. Bun mirrors its core alias as
   a direct dependency for its peer resolver, and npm browser-provider layouts
   may need a top-level `vite` edge so nested Vitest packages can resolve
@@ -228,6 +282,7 @@ scripts while preserving their arguments:
 | `lint-staged` | `vp staged`                                 |
 | `eslint`      | `vp lint`, when its optional migration runs |
 | `prettier`    | `vp fmt`, when its optional migration runs  |
+| `tsup`        | `vp pack`, when its optional migration runs |
 
 For commands launched through `bunx`, migration preserves `bunx` and its
 `--bun` flag (keeping the user's chosen runtime) and rewrites only the managed
@@ -243,6 +298,14 @@ as `run` or `--`:
 
 Unrelated `bunx` commands and other package-executor forms remain unchanged.
 
+## Continuous Integration Rules
+
+Migration replaces exact `voidzero-dev/setup-vp@v1` references in GitHub
+Actions workflows and composite actions under `.github` with the latest exact
+`setup-vp` release known to that Vite+ version. The frozen `v1` tag does not
+receive new releases. Existing exact versions and commit SHAs are left
+unchanged.
+
 ## Node.js Version Rules
 
 Migration converts legacy Node.js version-manager files to `.node-version`,
@@ -254,8 +317,9 @@ migrations run it unconditionally.
   existing `.node-version` is kept.
 - When `.nvmrc` is removed, any `actions/setup-node` `node-version-file:
 .nvmrc` reference in `.github/workflows/*.{yml,yaml}` and composite actions
-  (`.github/actions/**/action.{yml,yaml}`) is repointed to `.node-version` so
-  CI does not fail with "node version file ... does not exist".
+  under `.github` (`.github/**/action.{yml,yaml}`) is repointed to
+  `.node-version` so CI does not fail with "node version file ... does not
+  exist".
 
 ## Package-Manager Rules
 

package/docs/guide/migrate.md

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

package/docs/guide/test.md

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