vite-plus 1.5.1 → 1.6.0

package/dist/{constants-D5f7inVN.js → package-Cc9gI1u1.js}

@@ -1,6 +1,5 @@
-import { createRequire } from "node:module";
 // package.json
-var version = "1.5.1";
+var version = "1.6.0";
 var exports = {
 	".": {
 		"types": "./dist/index.d.ts",
@@ -281,78 +280,4 @@ var exports = {
 	}
 };
 var engines = { "node": "^22.18.0 || ^24.11.0 || >=26.0.0" };
-// src/utils/constants.ts
-const VITE_PLUS_NAME = "vite-plus";
-const VITE_PLUS_VERSION = process.env.VP_VERSION || version;
-const VITE_CONFIG_FILES = [
-	"vite.config.js",
-	"vite.config.mjs",
-	"vite.config.ts",
-	"vite.config.cjs",
-	"vite.config.mts",
-	"vite.config.cts"
-];
-const VITEST_VERSION = "5.1.0";
-const SETUP_VP_VERSION = "v1.21.2";
-const TSDOWN_MIGRATION_SKILL_URL = "https://github.com/rolldown/tsdown/blob/main/skills/tsdown-migrate/SKILL.md";
-const VITE_PLUS_OVERRIDE_PACKAGES = process.env.VP_OVERRIDE_PACKAGES ? JSON.parse(process.env.VP_OVERRIDE_PACKAGES) : {
-	vite: `npm:@voidzero-dev/vite-plus-core@${VITE_PLUS_VERSION}`,
-	vitest: VITEST_VERSION
-};
-/**
-* Package-name patterns the migrator exempts from a package manager's
-* "minimum release age" gate (pnpm `minimumReleaseAgeExclude` / Yarn
-* `npmPreapprovedPackages`).
-*
-* Vite+ pins `vitest` to an exact, sometimes freshly published version, and the
-* in-tree `@vitest/*` siblings install transitively at that same version, so an
-* age gate would otherwise quarantine the Vite+-managed family and break
-* `vp install`. The `@vitest/*` glob also covers the optional `@vitest/browser-*`
-* peers the migrator pins for browser projects. This does NOT pin or manage any
-* package — it only lets the chosen versions through the user's gate, including
-* the `@vitest/coverage-*` version the coverage guard asks the user to align to
-* the bundled vitest.
-*/
-const VITEST_AGE_GATE_EXEMPT_PACKAGES = ["vitest", "@vitest/*"];
-/**
-* When VP_FORCE_MIGRATE is set, force full dependency rewriting
-* even for projects already using vite-plus. Used by ecosystem CI to
-* override dependencies with locally built tgz packages.
-*/
-function isForceOverrideMode() {
-	return process.env.VP_FORCE_MIGRATE === "1";
-}
-const require = createRequire(import.meta.url);
-function resolve(path) {
-	return require.resolve(path, { paths: [process.cwd(), import.meta.dirname] });
-}
-/**
-* Like {@link resolve}, but prefers the copy shipped with the CLI
-* (`import.meta.dirname`) over the project's (`process.cwd()`).
-*
-* Use this for runtime modules that MUST match what `vite-plus/test*`
-* imports resolve to — chiefly the Vitest runner binary. The `vite-plus/test`
-* shims `export * from 'vitest'`, which Node resolves to vite-plus's own
-* bundled (pinned) Vitest. If `vp test` instead spawned a project-local
-* Vitest (a different physical copy/version), the runner and the imported
-* `vi`/`expect`/runner internals would come from two distinct Vitest
-* modules — a classic source of Vitest internal-state and mock-hoisting
-* mismatches. `process.cwd()` stays as a fallback for layouts where the
-* bundled copy is somehow unreachable, so this is never worse than {@link resolve}.
-*/
-function resolveBundled(path) {
-	return require.resolve(path, { paths: [import.meta.dirname, process.cwd()] });
-}
-const BASEURL_TSCONFIG_WARNING = "Skipped typeAware/typeCheck: a tsconfig file contains baseUrl which is not yet supported by the oxlint type checker.\n  Run `vp dlx @andrewbranch/ts5to6 --fixBaseUrl <tsconfig path>` to remove baseUrl from your tsconfig.";
-const BASEURL_TSCONFIG_FIX_PACKAGE = "@andrewbranch/ts5to6";
-const BASEURL_TSCONFIG_FIX_FLAG = "--fixBaseUrl";
-function createBaseUrlTsconfigFixArgs(target = ".") {
-	return [BASEURL_TSCONFIG_FIX_FLAG, target];
-}
-const DEFAULT_ENVS = {
-	JS_RUNTIME_VERSION: process.versions.node,
-	JS_RUNTIME_NAME: process.release.name,
-	NODE_PACKAGE_MANAGER: "vite-plus"
-};
-const CONFIG_METADATA_ENV = "VP_RESOLVING_CONFIG_METADATA";
-export { engines as _, SETUP_VP_VERSION as a, VITEST_VERSION as c, VITE_PLUS_OVERRIDE_PACKAGES as d, VITE_PLUS_VERSION as f, resolveBundled as g, resolve as h, DEFAULT_ENVS as i, VITE_CONFIG_FILES as l, isForceOverrideMode as m, BASEURL_TSCONFIG_WARNING as n, TSDOWN_MIGRATION_SKILL_URL as o, createBaseUrlTsconfigFixArgs as p, CONFIG_METADATA_ENV as r, VITEST_AGE_GATE_EXEMPT_PACKAGES as s, BASEURL_TSCONFIG_FIX_PACKAGE as t, VITE_PLUS_NAME as u, exports as v, version as y };
+export { exports as n, version as r, engines as t };

package/dist/{package-overrides-Ci8GXouY.js → package-overrides-nw4zcITi.js}

@@ -1,4 +1,4 @@
-import { a as GREATER_LESS_THAN, b as safeRegex, c as LOOSE_PLAIN, d as XRANGE_PLAIN, f as XRANGE_PLAIN_LOOSE, g as formatComparableVersion, i as FULL_PLAIN, m as compareParsed, o as LONE_CARET, s as LONE_TILDE, t as BUILD, x as tryParse, y as parse } from "./comparison-CmVirWIW-UlEf2maz.js";
+import { S as tryParse, a as GREATER_LESS_THAN, b as parse, c as LOOSE_PLAIN, d as XRANGE_PLAIN, f as XRANGE_PLAIN_LOOSE, g as formatComparableVersion, i as FULL_PLAIN, m as compareParsed, o as LONE_CARET, s as LONE_TILDE, t as BUILD, x as safeRegex } from "./comparison-CmVirWIW-Z8p6CfWL.js";
 // ../../node_modules/.pnpm/verkit@0.5.0/node_modules/verkit/dist/set-BGFWKKE8.js
 const STRICT_COMPARATOR = safeRegex(String.raw`^${GREATER_LESS_THAN}\s*(${FULL_PLAIN})$|^$`);
 const LOOSE_COMPARATOR$1 = safeRegex(String.raw`^${GREATER_LESS_THAN}\s*(${LOOSE_PLAIN})$|^$`);

package/dist/{prompts-DLpJGhfK.js → prompts-JkuWOV60.js}

@@ -1,10 +1,10 @@
 import { r as __toESM, t as __commonJSMin } from "./rolldown-runtime-DegdyBIC.js";
-import { _ as isGreaterThanOrEqual, b as safeRegex, g as formatComparableVersion, l as PRERELEASE, n as COERCE, r as COERCE_FULL, u as PRERELEASE_LOOSE, x as tryParse, y as parse } from "./comparison-CmVirWIW-UlEf2maz.js";
+import { S as tryParse, _ as isGreaterThanOrEqual, b as parse, g as formatComparableVersion, l as PRERELEASE, n as COERCE, r as COERCE_FULL, u as PRERELEASE_LOOSE, x as safeRegex } from "./comparison-CmVirWIW-Z8p6CfWL.js";
 import { i as runCommandSilently, n as getVpCommand } from "./command-rY79K5NI.js";
 import { a as writeJsonFile, i as readJsonFile } from "./json-kl84kDyH.js";
 import { t as accent } from "./terminal-BcuPUy-j.js";
 import { t as require_dist } from "./dist-Bs0SObNC.js";
-import { f as VITE_PLUS_VERSION } from "./constants-D5f7inVN.js";
+import { f as VITE_PLUS_VERSION } from "./constants-DXqV1vWL.js";
 import path from "node:path";
 import { downloadPackageManager } from "../binding/index.js";
 import { stripVTControlCharacters, styleText } from "node:util";
@@ -2504,13 +2504,14 @@ async function selectPackageManager(interactive, silent = false) {
 		return PackageManager.pnpm;
 	}
 }
-async function downloadPackageManager$1(packageManager, version, interactive, silent = false, cwd) {
+async function downloadPackageManager$1(packageManager, version, interactive, silent = false, cwd, expectedHash) {
 	const spinner = silent ? getSilentSpinner() : getSpinner(interactive);
 	spinner.start(`${packageManager}@${version} installing...`);
 	const downloadResult = await downloadPackageManager({
 		name: packageManager,
 		version,
-		cwd
+		cwd,
+		expectedHash
 	});
 	spinner.stop(`${packageManager}@${downloadResult.version} installed`);
 	return downloadResult;
@@ -2530,7 +2531,10 @@ async function runViteInstall(cwd, interactive, extraArgs, options) {
 	const { exitCode, stderr, stdout } = await runCommandSilently({
 		...getVpCommand(["install", ...installArgs]),
 		cwd,
-		envs: process.env
+		envs: options?.packageManagerOverride ? {
+			...process.env,
+			VP_PACKAGE_MANAGER: options.packageManagerOverride
+		} : process.env
 	});
 	const combinedOutput = `${stdout.toString()}\n${stderr.toString()}`;
 	const pendingBuilds = detectIgnoredBuilds ? parseInstallGatedBuilds(combinedOutput, options?.packageManager) : void 0;

package/dist/{resolve-vite-config-D7IUZYKq.js → resolve-vite-config-CfUvxuCo.js}

@@ -1 +1 @@
-export { i as resolveUniversalViteConfig } from "./resolve-vite-config-D-JtjGRa.js";
+export { i as resolveUniversalViteConfig } from "./resolve-vite-config-x5QVnaf4.js";

package/dist/{resolve-vite-config-D-JtjGRa.js → resolve-vite-config-x5QVnaf4.js}

@@ -1,5 +1,5 @@
-import { d as withConfigMetadataResolution } from "./define-config-XKYhw0xH.js";
-import { l as VITE_CONFIG_FILES } from "./constants-D5f7inVN.js";
+import { d as withConfigMetadataResolution } from "./define-config-CeYkQCqG.js";
+import { l as VITE_CONFIG_FILES } from "./constants-DXqV1vWL.js";
 import path from "node:path";
 import { findMonorepoRoot } from "../binding/index.js";
 import fs from "node:fs";

package/dist/staged/bin.js

@@ -1,6 +1,6 @@
 import { r as __toESM } from "../rolldown-runtime-DegdyBIC.js";
 import { t as require_picomatch } from "../picomatch-DEUoj81q.js";
-import { a as resolveViteConfig } from "../resolve-vite-config-D-JtjGRa.js";
+import { a as resolveViteConfig } from "../resolve-vite-config-x5QVnaf4.js";
 import { t as unwrapCliParseOutcome } from "../cli-parse-aeUeFDlC.js";
 import { i as log, n as errorMsg, o as printHeader } from "../terminal-BcuPUy-j.js";
 import { createRequire } from "node:module";

package/dist/sync-versions/bin.js

@@ -1,5 +1,5 @@
 import { c as modify, l as parse$1, o as applyEdits, t as detectFormattingOptions } from "../json-kl84kDyH.js";
-import { i as normalizeRange, t as extractOverrideTargetName } from "../package-overrides-Ci8GXouY.js";
+import { i as normalizeRange, t as extractOverrideTargetName } from "../package-overrides-nw4zcITi.js";
 import { t as require_dist } from "../dist-Bs0SObNC.js";
 import { n as isAlignableVitestEcosystemPackage } from "../vitest-ecosystem-BeEYz-qF.js";
 import path from "node:path";

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.5.1",
+      "version": "1.6.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.5.1",
+      "version": "1.6.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.91.0",
+      "version": "1.93.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.76.0",
+      "version": "0.78.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@ export const toolchain = {
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2005",
+      "version": "7.0.2006",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -99,8 +99,8 @@ export const toolchain = {
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "40cb9cac46bddbf8aa5ce5373df1a6a1980acc38",
-      "builtAt": "2026-11-09T12:28:42Z",
+      "revision": "cb1ea8d214b26a0f3ca2b2ef3b6bc471b18ffacb",
+      "builtAt": "2026-11-11T03:47:01Z",
       "kind": "tool",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.5.1",
+      "version": "1.6.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.5.1",
+      "version": "1.6.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.91.0",
+      "version": "1.93.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.76.0",
+      "version": "0.78.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2005",
+      "version": "7.0.2006",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -99,8 +99,8 @@
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "40cb9cac46bddbf8aa5ce5373df1a6a1980acc38",
-      "builtAt": "2026-11-09T12:28:42Z",
+      "revision": "cb1ea8d214b26a0f3ca2b2ef3b6bc471b18ffacb",
+      "builtAt": "2026-11-11T03:47:01Z",
       "kind": "tool",
       "delivery": [
         "compiled"

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

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

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

@@ -1,8 +1,8 @@
-import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-DLpJGhfK.js";
+import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-JkuWOV60.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 { 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 { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-DXqV1vWL.js";
 import path from "node:path";
 import { styleText } from "node:util";
 import fs from "node:fs";

package/dist/user-agent-CpEaSTwI.js

@@ -0,0 +1,6 @@
+import { r as version } from "./package-Cc9gI1u1.js";
+// src/utils/user-agent.ts
+function setUserAgent() {
+	process.env.VP_USER_AGENT = `vp/${version}`;
+}
+export { setUserAgent as t };

package/dist/version.js

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

package/dist/versions.js

@@ -2,8 +2,8 @@ export const versions = {
   "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",
+  "oxfmt": "0.78.0",
+  "oxlint": "1.93.0",
+  "oxlint-tsgolint": "7.0.2006",
   "tsdown": "0.23.4"
 };

package/dist/vpx-bin.js

@@ -1,5 +1,6 @@
 import { r as __toESM } from "./rolldown-runtime-DegdyBIC.js";
 import { a as require_cross_spawn, t as exitCodeFromClose } from "./command-rY79K5NI.js";
+import { t as setUserAgent } from "./user-agent-CpEaSTwI.js";
 import { a as canExecDirectly, c as nodeModulesBinPaths, l as packageInvocation, o as detectScript, r as ScriptError, s as isFile, u as parseVpxArgs } from "./vpx-script-EXgV5QOf.js";
 import { createRequire } from "node:module";
 import path from "node:path";
@@ -8,6 +9,7 @@ import { styleText } from "node:util";
 import { statSync } from "node:fs";
 // src/vpx-bin.ts
 var import_cross_spawn = /* @__PURE__ */ __toESM(require_cross_spawn(), 1);
+setUserAgent();
 function errorMsg(message) {
 	console.error(styleText(["red", "bold"], "error:"), message);
 }

package/docs/config/run.md

@@ -265,11 +265,12 @@ Vite Task automatically detects which files a command uses. See [Automatic Data
 
 ```ts [vite.config.ts]
 tasks: {
-  build: {
-    command: 'vp build',
+  lint: {
+    command: 'vp lint',
     cache: {
       // Use `{ auto: true }` to use automatic fingerprinting (default).
-      input: [{ auto: true }, '!**/*.tsbuildinfo', '!dist/**'],
+      // Keep the build task's `dist` folder from affecting this task.
+      input: [{ auto: true }, '!dist/**'],
     },
   },
 }
@@ -348,14 +349,14 @@ tasks: {
 
 Use `{ auto: true }` to keep automatic write tracking while adding explicit output globs.
 
-This is useful when a task writes files that should not be restored from the cache. For example, exclude TypeScript `.tsbuildinfo` files:
+This is useful when a task writes files that should not be restored from the cache, such as a debug log:
 
 ```ts [vite.config.ts]
 tasks: {
-  typecheck: {
-    command: 'tsc --build',
+  build: {
+    command: 'node build.mjs',
     cache: {
-      output: [{ auto: true }, '!*.tsbuildinfo'],
+      output: [{ auto: true }, '!build.log'],
     },
   },
 }

package/docs/guide/automatic-data-tracking.md

@@ -39,6 +39,144 @@ For this task, Vite Task records source files, config files, missing files the c
 
 File system tracking also tracks outputs. If you omit [`cache.output`](/config/run#cache-output), Vite Task archives files the command writes after a successful run and restores them on a cache hit.
 
+### Rebuildable Inputs
+
+Some tools read files they also write:
+
+- With [`exports`](https://tsdown.dev/options/package-exports) enabled, tsdown reads `package.json` and writes the generated `exports` field back into it.
+- Many build tools list `dist` to delete the old build before they write a new one there.
+- Tools with their own cache read it and write it back, as `tsc --incremental` does with `tsconfig.tsbuildinfo`.
+
+This section explains how Vite Task handles files and folders that a task both reads and writes.
+
+Vite Task calls these files and folders **rebuildable**: the task produces them itself, so they don't have to exist before it runs. A task can rebuild:
+
+- Files it writes, such as `dist/index.mjs` or the `package.json` that tsdown updates.
+- Folders where the task wrote everything inside, such as `dist`.
+
+::: warning
+Rebuildable inputs assume that a task doesn't keep changing its outputs when its inputs stay the same.
+
+For example, a script that appends data to a file on every run breaks this assumption, and Vite Task can't detect it. Vite Task caches the file as the script left it, so the next run is a cache hit that restores the file without appending anything.
+:::
+
+After the task finishes, Vite Task fingerprints its inputs as the task left them. On the next run:
+
+- A rebuildable input may be missing, as on a fresh clone or after you delete it. The cache still hits and restores it with the task's outputs.
+- A rebuildable file that exists must match what the task left. If something else changed it, the cache misses.
+- Inputs that aren't rebuildable, such as your source files, are still checked strictly. Deleting or editing one causes a cache miss.
+
+#### Example: A Task Rewriting Sources
+
+```ts [vite.config.ts]
+tasks: {
+  build: {
+    // `--exports` makes tsdown write the generated `exports` field into package.json.
+    command: 'tsdown --exports',
+  },
+}
+```
+
+```
+my-lib/
+├── src/
+│   └── index.ts             # input: tsdown reads it
+└── package.json             # rebuildable: tsdown reads it, then writes "exports" into it
+```
+
+On the next run, Vite Task compares `package.json` with the file tsdown wrote, so the `exports` field that tsdown added doesn't cause a cache miss:
+
+```bash
+$ vp run build               # first run: tsdown adds "exports" to package.json
+$ vp run build               # cache hit
+```
+
+Editing `package.json` yourself still causes a cache miss, as it should, because tsdown has to run again with your changes:
+
+```bash
+$ vp pm pkg set version=1.1.0
+$ vp run build               # cache miss: 'package.json' modified
+```
+
+#### Example: A Task Listing Its Output Folder For Deletion
+
+```ts [vite.config.ts]
+tasks: {
+  build: {
+    // `--clean` deletes the old build in `dist` before tsdown writes a new one.
+    command: 'tsdown --clean',
+  },
+}
+```
+
+```
+my-lib/
+├── src/
+│   └── index.ts             # input
+├── package.json             # input
+└── dist/                    # rebuildable: the task wrote everything inside
+    └── index.mjs            # rebuildable: the task writes it
+```
+
+Listing `dist` makes it an input. Since the task wrote everything inside `dist`, the whole folder is rebuildable:
+
+```bash
+$ vp run build               # first run: tsdown writes dist/
+$ rm -rf dist                # as on a fresh clone
+$ vp run build               # cache hit: dist/ is restored
+```
+
+You don't need `'!dist/**'` in `cache.input` to keep `dist` out of the task's inputs, even though the task lists `dist` to delete the old build and then writes a new one.
+
+#### Example: A Task Reading And Writing Its Own Cache
+
+```ts [vite.config.ts]
+tasks: {
+  typecheck: {
+    command: 'tsc --incremental --noEmit',
+  },
+}
+```
+
+```
+my-app/
+├── src/
+│   └── main.ts              # input: tsc reads it
+├── tsconfig.json            # input: tsc reads it
+└── tsconfig.tsbuildinfo     # rebuildable: tsc reads its cache from it, then writes it back
+```
+
+Vite Task compares `tsconfig.tsbuildinfo` with the file tsc wrote, so tsc's updates to it don't cause a cache miss. If the file is missing, as on a fresh clone, a cache hit restores it:
+
+```bash
+$ vp run typecheck           # first run: tsc writes tsconfig.tsbuildinfo
+$ vp run typecheck           # cache hit
+$ rm tsconfig.tsbuildinfo    # as on a fresh clone
+$ vp run typecheck           # cache hit: tsconfig.tsbuildinfo is restored
+```
+
+#### Avoid Caching Tasks That Modify Files In Place
+
+A task that rewrites your source files makes them rebuildable. If a cached `vp fmt` rewrites every file in `src/utils`, the whole folder becomes rebuildable:
+
+```
+src/
+└── utils/                   # rebuildable: vp fmt rewrote everything inside
+    ├── a.ts                 # rebuildable: vp fmt rewrote it
+    └── b.ts                 # rebuildable: vp fmt rewrote it
+```
+
+Deleting `src/utils` is then a cache hit that writes the folder back.
+
+Turn off auto-fix in the lint and format tasks you cache:
+
+```ts [vite.config.ts]
+tasks: {
+  lint: 'vp lint', // instead of `vp lint --fix`
+  format: 'vp fmt --check', // instead of `vp fmt`
+}
+```
+
 ### Limitations
 
 Vite Task cannot track environment variable reads, and it cannot always tell which tracked paths are stable inputs, generated outputs, or tool-managed cache paths that should not become inputs or outputs.

package/docs/guide/check.md

@@ -15,6 +15,7 @@ We recommend turning both `typeAware` and `typeCheck` on so `vp check` becomes t
 ```bash
 vp check
 vp check --fix              # Format and run autofixers.
+vp check --continue-on-error # Report all enabled checks, even if formatting fails.
 vp check --quiet            # Hide lint warnings; still report and fail on errors.
 vp check --deny-warnings    # Treat lint warnings as errors.
 vp check --no-fmt           # Skip format; run lint (and type-check if enabled).
@@ -24,6 +25,18 @@ vp check --no-fmt --no-lint # Type-check only (requires both `typeAware` and `ty
 
 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`.
 
+Use `vp check --continue-on-error` to run all enabled checks and report formatting, lint,
+and type errors in one invocation without modifying files. Type checks still
+require the existing `lint.options.typeAware` and `lint.options.typeCheck` settings.
+The command exits with a non-zero status if any check fails, even when later
+checks pass. Without `--continue-on-error`, the existing fail-fast behavior is preserved.
+
+`--continue-on-error` also works with `--fix`: checks continue after a tool reports a
+failure, and formatting runs again after lint fixes. The first failing exit status
+is preserved. Options such as `--no-fmt`, `--no-lint`, `--quiet`, and
+`--deny-warnings` retain their usual behavior. Configuration loading or command
+startup errors still abort the command.
+
 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

package/docs/guide/global-cli.md

@@ -83,9 +83,9 @@ vp help
 
 When you enable environment management during installation, Vite+ records managed mode for Node.js and the npm, pnpm, Yarn, and Bun shims. Run `vp env off` to prefer system tools, or scope the change with `vp env off node` or `vp env off pm`.
 
-::: details Installer Environment Variables & Options
+::: details Environment Variables & Options
 
-The Vite+ installers (`vp-setup.exe`, `install.ps1`, and `install.sh`) and the installed `vp` CLI read the environment variables below.
+The Vite+ installers (`vp-setup.exe`, `install.ps1`, and `install.sh`) and the CLI use the environment variables below for installation, runtime configuration, and child tools.
 
 ### Installation Variables
 
@@ -331,6 +331,16 @@ These variables configure the installed Vite+ CLI. `VP_HOME` (above) also applie
 
 Vite+ sets additional `VP_*` variables during shim dispatch and shell integration (recursion guards, active-version records, wrapper flags); do not set them manually.
 
+### Child Process Variables
+
+These variables are set by Vite+ for tools it starts.
+
+#### `VP_USER_AGENT`
+
+`vp`, `vpr`, and `vpx` set `VP_USER_AGENT=vp/<version>` for their child processes. This works with both the global CLI and the project-local `vite-plus` package. Each invocation reports its own version; when the global CLI delegates to a local CLI, the local version takes over.
+
+Use this variable to detect Vite+ even when an underlying package manager replaces `npm_config_user_agent`. Read the first space-separated product token (`vp/<version>`) so consumers can tolerate additional fields in future versions. The value identifies the CLI, not the command or its arguments. Ordinary tool shims, such as `node`, `npm`, and `npx`, preserve an inherited value without creating one.
+
 ### TLS/CA Configuration
 
 #### `SSL_CERT_FILE` / `NODE_EXTRA_CA_CERTS`

package/docs/guide/migrate-rules.md

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

package/docs/guide/migrate.md

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