vite-plus 0.3.0 → 0.3.1

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "0.3.0",
+      "version": "0.3.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "0.3.0",
+      "version": "0.3.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.5",
+      "version": "1.2.7",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.79.0",
+      "version": "1.81.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.64.0",
+      "version": "0.66.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@ export const toolchain = {
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.22.14",
+      "version": "0.23.0",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -100,7 +100,7 @@ export const toolchain = {
       "id": "vite-task",
       "name": "vite-task",
       "revision": "d05b1dcdbaabaa69643ee0b89cebe3cd390957e9",
-      "builtAt": "2026-08-24T03:41:26Z",
+      "builtAt": "2026-09-08T13:14:20Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.146.0",
+      "version": "0.148.0",
       "kind": "engine",
       "delivery": [
         "compiled"
@@ -120,7 +120,7 @@ export const toolchain = {
     {
       "id": "oxc-resolver",
       "name": "oxc-resolver",
-      "version": "11.24.2",
+      "version": "11.24.3",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "0.3.0",
+      "version": "0.3.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "0.3.0",
+      "version": "0.3.1",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.5",
+      "version": "1.2.7",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.79.0",
+      "version": "1.81.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.64.0",
+      "version": "0.66.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.22.14",
+      "version": "0.23.0",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -100,7 +100,7 @@
       "id": "vite-task",
       "name": "vite-task",
       "revision": "d05b1dcdbaabaa69643ee0b89cebe3cd390957e9",
-      "builtAt": "2026-08-24T03:41:26Z",
+      "builtAt": "2026-09-08T13:14:20Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.146.0",
+      "version": "0.148.0",
       "kind": "engine",
       "delivery": [
         "compiled"
@@ -120,7 +120,7 @@
     {
       "id": "oxc-resolver",
       "name": "oxc-resolver",
-      "version": "11.24.2",
+      "version": "11.24.3",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/{tsconfig-LD2QhQ0O.js → tsconfig-CUggNuJR.js}

@@ -1,6 +1,6 @@
-import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-Bn-U8o4v.js";
-import { A as isCancel, C as log, t as cancelAndExit, x as confirm } from "./prompts-DF3yU-eU.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-0IAVgpox.js";
 import { c as parse, o as applyEdits, s as modify } from "./json-cULBl7Pi.js";
+import { S as log, b as confirm, k as isCancel, t as cancelAndExit } from "./prompts-CtzEgFY-.js";
 import { n as runCommandSilently } from "./command-CguLh2KL.js";
 import path from "node:path";
 import { styleText } from "node:util";

package/dist/{tsconfig-BVHG3DpR.js → tsconfig-VAbm4ZzJ.js}

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

package/dist/tsgolint-path.d.ts

@@ -1,8 +1,7 @@
 //#region src/utils/tsgolint-path.d.ts
-declare function resolveWindowsTsgolintExecutable(pathCandidates: string[], options: {
+export declare function resolveWindowsTsgolintExecutable(pathCandidates: string[], options: {
   exists: (path: string) => boolean;
   getRealpathCandidates?: () => string[];
 }): string;
-declare function resolveTsgolintExecutable(tsgolintBinPath: string, scriptUrl: string): string;
-//#endregion
-export { resolveTsgolintExecutable, resolveWindowsTsgolintExecutable };
+export declare function resolveTsgolintExecutable(tsgolintBinPath: string, scriptUrl: string): string;
+//#endregion

package/dist/types/customEvent.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/customEvent.d.ts';
+export type * from 'vite/types/customEvent.d.ts';

package/dist/types/hmrPayload.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/hmrPayload.d.ts';
+export type * from 'vite/types/hmrPayload.d.ts';

package/dist/types/hot.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/hot.d.ts';
+export type * from 'vite/types/hot.d.ts';

package/dist/types/import-meta.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/import-meta.d.ts';
+export type * from 'vite/types/import-meta.d.ts';

package/dist/types/importGlob.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/importGlob.d.ts';
+export type * from 'vite/types/importGlob.d.ts';

package/dist/types/importMeta.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/importMeta.d.ts';
+export type * from 'vite/types/importMeta.d.ts';

package/dist/types/metadata.d.ts

@@ -1 +1 @@
-export type * from '@voidzero-dev/vite-plus-core/types/metadata.d.ts';
+export type * from 'vite/types/metadata.d.ts';

package/dist/version.d.ts

@@ -2,6 +2,5 @@
 /**
  * Print version information
  */
-declare function printVersion(cwd: string): Promise<void>;
-//#endregion
-export { printVersion };
+export declare function printVersion(cwd: string): Promise<void>;
+//#endregion

package/dist/version.js

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

package/dist/versions.js

@@ -1,9 +1,9 @@
 export const versions = {
   "vite": "8.2.2",
-  "rolldown": "1.2.5",
+  "rolldown": "1.2.7",
   "vitest": "4.1.11",
-  "oxfmt": "0.64.0",
-  "oxlint": "1.79.0",
+  "oxfmt": "0.66.0",
+  "oxlint": "1.81.0",
   "oxlint-tsgolint": "7.0.2001",
-  "tsdown": "0.22.14"
+  "tsdown": "0.23.0"
 };

package/dist/vitest-ecosystem-BiRqcaRI.js

@@ -0,0 +1,23 @@
+//#region src/utils/package-overrides.ts
+function extractOverrideTargetName(key) {
+	let target = key.trim();
+	for (let delimiter = target.search(/[^ |@]>/); delimiter !== -1; delimiter = target.search(/[^ |@]>/)) target = target.slice(delimiter + 2).trim();
+	if (!target) return target;
+	if (target.includes("/")) {
+		const segments = target.split("/");
+		const last = segments[segments.length - 1];
+		const scope = segments[segments.length - 2];
+		target = scope?.startsWith("@") ? `${scope}/${last}` : last;
+	}
+	const nameStart = target.startsWith("@") ? target.indexOf("/") + 1 : 0;
+	const versionAt = target.indexOf("@", nameStart);
+	return versionAt > 0 ? target.slice(0, versionAt) : target;
+}
+//#endregion
+//#region src/utils/vitest-ecosystem.ts
+const VITEST_ALIGN_EXCLUDED = /* @__PURE__ */ new Set(["@vitest/eslint-plugin", "@vitest/coverage-c8"]);
+function isAlignableVitestEcosystemPackage(name) {
+	return name.startsWith("@vitest/") && !VITEST_ALIGN_EXCLUDED.has(name);
+}
+//#endregion
+export { extractOverrideTargetName as n, isAlignableVitestEcosystemPackage as t };

package/docs/guide/check.md

@@ -15,6 +15,7 @@ We recommend turning `typeCheck` on so `vp check` becomes the single command for
 ```bash
 vp check
 vp check --fix             # Format and run autofixers.
+vp check --quiet           # Hide lint warnings; still report and fail on errors.
 vp check --no-fmt          # Skip format; run lint (and type-check if enabled).
 vp check --no-lint         # Skip lint rules; keep type-check when enabled.
 vp check --no-fmt --no-lint # Type-check only (requires `typeCheck` enabled).

package/docs/guide/ci.md

@@ -4,12 +4,17 @@ You can use `voidzero-dev/setup-vp` to use Vite+ in CI environments.
 
 ## Overview
 
-[`voidzero-dev/setup-vp`](https://github.com/voidzero-dev/setup-vp) provides integrations for GitHub Actions and GitLab CI/CD. Both install Vite+ and can install project dependencies. The GitHub Action can also set up Node.js and cache package manager data automatically, while the GitLab CI/CD template uses the Node.js runtime and cache configuration provided by the job.
+[`voidzero-dev/setup-vp`](https://github.com/voidzero-dev/setup-vp) provides integrations for GitHub Actions, GitLab CI/CD, and Azure Pipelines. All three install Vite+ and can install project dependencies. The GitHub Action and Azure Pipelines template can also set up Node.js and cache package manager data automatically, while the GitLab CI/CD template uses the Node.js runtime and cache configuration provided by the job.
 
 ## setup-vp Versioning
 
 Set `<setup-vp-version>` in each example to an exact version from the [`setup-vp` releases page](https://github.com/voidzero-dev/setup-vp/releases). You can use a commit SHA instead. Do not use the `v1` tag. The `v1` tag no longer receives updates.
 
+Run `vp migrate` to replace exact `voidzero-dev/setup-vp@v1` references in
+GitHub Actions workflows and composite actions under `.github` with the latest
+exact release known to your Vite+ version. Existing exact versions and commit
+SHAs remain unchanged.
+
 ### Automatic Version Updates
 
 Dependabot and Renovate can update exact versions in GitHub Actions workflows.
@@ -35,7 +40,7 @@ When you use a commit SHA, add the exact release tag in a comment. Renovate uses
 - uses: voidzero-dev/setup-vp@<commit-sha> # <setup-vp-version>
 ```
 
-These settings apply only to GitHub Actions workflows. For GitLab CI/CD, update both version values together.
+These settings apply only to GitHub Actions workflows. For GitLab CI/CD and Azure Pipelines, update both version values together.
 
 ## GitHub Actions
 
@@ -85,6 +90,41 @@ The GitLab CI/CD integration differs from the GitHub Action in a few ways:
 
 For advanced configuration and the complete input reference, see the [`setup-vp` GitLab CI/CD documentation](https://github.com/voidzero-dev/setup-vp#gitlab-cicd).
 
+## Azure Pipelines
+
+Use the reusable `setup-vp` step template in your Azure Pipelines configuration. Create a GitHub service connection named `github`, then reference the template from the `setup-vp` repository:
+
+```yaml [azure-pipelines.yml]
+resources:
+  repositories:
+    - repository: setupVp
+      type: github
+      endpoint: github
+      name: voidzero-dev/setup-vp
+      ref: refs/tags/<setup-vp-version>
+
+pool:
+  vmImage: ubuntu-latest
+
+steps:
+  - checkout: self
+  - template: azure/setup-vp.yml@setupVp
+    parameters:
+      setupRef: '<setup-vp-version>'
+      nodeVersion: 24.x
+      cache: true
+      runInstall: true
+  - script: vp check
+  - script: vp test
+  - script: vp build
+```
+
+Pin `ref` and `setupRef` to the same tag or commit SHA for strict reproducibility.
+
+The Azure Pipelines template supports Microsoft-hosted Linux, macOS, and Windows agents. It uses Azure's native `UseNode@1` and `Cache@2` tasks to set up Node.js and cache package-manager data.
+
+For advanced configuration and the complete parameter reference, see the [`setup-vp` Azure Pipelines documentation](https://github.com/voidzero-dev/setup-vp#azure-pipelines).
+
 ## Simplifying Existing Workflows
 
 If you are migrating an existing GitHub Actions workflow, you can often replace large blocks of Node, package-manager, and cache setup with a single `setup-vp` step.

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,7 +32,29 @@ 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
+
+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
@@ -34,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:
 
@@ -42,16 +84,17 @@ 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 the resolved bin directory. It writes shell setup scripts in the config directory.
-- `vp env on` enables managed mode so shims always use Vite+-managed Node.js
-- `vp env off` enables system-first mode so shims prefer system Node.js first
-- `vp env print` prints the shell snippet for the current session
+- `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:
 
@@ -87,28 +130,28 @@ 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` in the bin directory on Windows.
 
 In CI, `vp env use` can run without shell initialization. It writes a temporary
-session file in the resolved state directory. Later shim calls in the same job
-use this file to select the Node.js version.
+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
 
@@ -120,54 +163,83 @@ use this file to select the Node.js version.
 
 ```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` and `yarn` launchers next to the
-corepack binary. Vite+ does not add that location to `PATH`. The shim sets
-`--install-directory` to the resolved bin directory by default. The launchers
-are then available on `PATH`. They still use the Node.js and package-manager
-versions for the project:
-
-```bash
-corepack enable               # pnpm and yarn now resolve via corepack
-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