vite-plus 1.1.0 → 1.3.0

package/dist/test/browser/providers/playwright.d.ts

@@ -2,7 +2,7 @@ import { CustomComparatorsRegistry } from '../../_at-vitest-browser.js';
 export { defineBrowserCommand } from '../../_at-vitest-browser.js';
 import { Page, Frame, FrameLocator, BrowserContext, CDPSession, Browser, LaunchOptions, ConnectOptions, BrowserContextOptions } from 'playwright';
 import { ScreenshotMatcherOptions, ScreenshotComparatorRegistry, Locator } from '../../browser.js';
-import { BrowserProvider, BrowserModuleMocker, TestProject, CDPSession as CDPSession$1, BrowserProviderOption } from '../../node.js';
+import { BrowserProvider, BrowserModuleMocker, TestProject, CDPSession as CDPSession$1, BrowserProviderCloseOptions, BrowserProviderOption } from '../../node.js';
 
 declare const playwrightBrowsers: readonly ["firefox", "webkit", "chromium"];
 type PlaywrightBrowser = (typeof playwrightBrowsers)[number];
@@ -57,13 +57,17 @@ declare class PlaywrightBrowserProvider implements BrowserProvider {
 	mocker: BrowserModuleMocker;
 	browserName: PlaywrightBrowser;
 	private browserPromise;
+	private launchOptionsJson;
 	private closing;
+	private armedContexts;
 	tracingContexts: Set<string>;
 	pendingTraces: Map<string, string>;
 	initScripts: string[];
 	constructor(project: TestProject, options: PlaywrightProviderOptions);
 	private onSIGTERM;
 	private openBrowser;
+	private armInterception;
+	private probeInterception;
 	private createMocker;
 	private createContext;
 	private getContextOptions;
@@ -80,7 +84,8 @@ declare class PlaywrightBrowserProvider implements BrowserProvider {
 	}): Promise<void>;
 	private _throwIfClosing;
 	getCDPSession(sessionid: string): Promise<CDPSession$1>;
-	close(): Promise<void>;
+	close(options?: BrowserProviderCloseOptions): Promise<void>;
+	private closeContexts;
 }
 declare module '../../node.js' {
 	interface BrowserCommandContext {

package/dist/test/browser-playwright.d.ts

@@ -2,7 +2,7 @@ import { CustomComparatorsRegistry } from './_at-vitest-browser.js';
 export { defineBrowserCommand } from './_at-vitest-browser.js';
 import { Page, Frame, FrameLocator, BrowserContext, CDPSession, Browser, LaunchOptions, ConnectOptions, BrowserContextOptions } from 'playwright';
 import { ScreenshotMatcherOptions, ScreenshotComparatorRegistry, Locator } from './browser.js';
-import { BrowserProvider, BrowserModuleMocker, TestProject, CDPSession as CDPSession$1, BrowserProviderOption } from './node.js';
+import { BrowserProvider, BrowserModuleMocker, TestProject, CDPSession as CDPSession$1, BrowserProviderCloseOptions, BrowserProviderOption } from './node.js';
 
 declare const playwrightBrowsers: readonly ["firefox", "webkit", "chromium"];
 type PlaywrightBrowser = (typeof playwrightBrowsers)[number];
@@ -57,13 +57,17 @@ declare class PlaywrightBrowserProvider implements BrowserProvider {
 	mocker: BrowserModuleMocker;
 	browserName: PlaywrightBrowser;
 	private browserPromise;
+	private launchOptionsJson;
 	private closing;
+	private armedContexts;
 	tracingContexts: Set<string>;
 	pendingTraces: Map<string, string>;
 	initScripts: string[];
 	constructor(project: TestProject, options: PlaywrightProviderOptions);
 	private onSIGTERM;
 	private openBrowser;
+	private armInterception;
+	private probeInterception;
 	private createMocker;
 	private createContext;
 	private getContextOptions;
@@ -80,7 +84,8 @@ declare class PlaywrightBrowserProvider implements BrowserProvider {
 	}): Promise<void>;
 	private _throwIfClosing;
 	getCDPSession(sessionid: string): Promise<CDPSession$1>;
-	close(): Promise<void>;
+	close(options?: BrowserProviderCloseOptions): Promise<void>;
+	private closeContexts;
 }
 declare module './node.js' {
 	interface BrowserCommandContext {

package/dist/toolchain.js

@@ -4,7 +4,7 @@ export const toolchain = {
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.1.0",
+      "version": "1.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.1.0",
+      "version": "1.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@ export const toolchain = {
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.3",
+      "version": "8.3.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.12",
+      "version": "1.2.14",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@ export const toolchain = {
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.3",
+      "version": "5.0.5",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.87.0",
+      "version": "1.88.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.72.0",
+      "version": "0.73.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@ export const toolchain = {
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2003",
+      "version": "7.0.2004",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@ export const toolchain = {
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.23.0",
+      "version": "0.23.1",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -99,8 +99,8 @@ export const toolchain = {
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "7d69d6577ecf6bd83deee32186de59918a712873",
-      "builtAt": "2026-10-07T01:42:39Z",
+      "revision": "9ba4cc93379cf2d7a6c7e657285bb8a00e8339dc",
+      "builtAt": "2026-10-16T05:08:44Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.152.0",
+      "version": "0.154.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.1.0",
+      "version": "1.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.1.0",
+      "version": "1.3.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.3",
+      "version": "8.3.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.12",
+      "version": "1.2.14",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.3",
+      "version": "5.0.5",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.87.0",
+      "version": "1.88.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.72.0",
+      "version": "0.73.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -77,7 +77,7 @@
     {
       "id": "oxlint-tsgolint",
       "name": "oxlint-tsgolint",
-      "version": "7.0.2003",
+      "version": "7.0.2004",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -89,7 +89,7 @@
     {
       "id": "tsdown",
       "name": "tsdown",
-      "version": "0.23.0",
+      "version": "0.23.1",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -99,8 +99,8 @@
     {
       "id": "vite-task",
       "name": "vite-task",
-      "revision": "7d69d6577ecf6bd83deee32186de59918a712873",
-      "builtAt": "2026-10-07T01:42:39Z",
+      "revision": "9ba4cc93379cf2d7a6c7e657285bb8a00e8339dc",
+      "builtAt": "2026-10-16T05:08:44Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.152.0",
+      "version": "0.154.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/{tsconfig-DzZ-nrx2.js → tsconfig-BZu7kl-x.js}

@@ -1,8 +1,8 @@
-import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-CCQkpaxK.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-DR55DpRm.js";
 import { c as modify, l as parse, o as applyEdits } from "./json-JP24qHUF.js";
 import { t as vitest_v5_entry_points_default } from "./vitest-v5-entry-points-DthU1e_O.js";
-import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-ByOzbMBG.js";
-import { n as runCommandSilently } from "./command-CguLh2KL.js";
+import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-1xNz_ne0.js";
+import { n as runCommandSilently } from "./command-CdMBoZFD.js";
 import path from "node:path";
 import { styleText } from "node:util";
 import fs from "node:fs";

package/dist/tsconfig-zWgHiQ3X.js

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

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 { y as version } from "./constants-CCQkpaxK.js";
-import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-BS84eWrW.js";
+import { y as version } from "./constants-DR55DpRm.js";
+import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-CQDXTm6j.js";
 import path from "node:path";
 import { pathToFileURL } from "node:url";
 import fs from "node:fs";

package/dist/versions.js

@@ -1,9 +1,9 @@
 export const versions = {
-  "vite": "8.3.3",
-  "rolldown": "1.2.12",
-  "vitest": "5.0.3",
-  "oxfmt": "0.72.0",
-  "oxlint": "1.87.0",
-  "oxlint-tsgolint": "7.0.2003",
-  "tsdown": "0.23.0"
+  "vite": "8.3.4",
+  "rolldown": "1.2.14",
+  "vitest": "5.0.5",
+  "oxfmt": "0.73.0",
+  "oxlint": "1.88.0",
+  "oxlint-tsgolint": "7.0.2004",
+  "tsdown": "0.23.1"
 };

package/docs/config/run.md

@@ -235,12 +235,16 @@ tasks: {
 
 Do not put a variable in `untrackedEnv` if its value changes the task result. If a cache-reporting tool covers the variable through [automatic tracking](/guide/automatic-data-tracking#cooperative-tracking), leave it out of both `env` and `untrackedEnv`.
 
-Vite Task passes a set of common environment variables to all tasks:
+Vite Task includes default untracked patterns for system variables and common tools. Examples include:
 
-- **System:** `HOME`, `USER`, `PATH`, `SHELL`, `LANG`, `TZ`
-- **Node.js:** `NODE_OPTIONS`, `COREPACK_HOME`, `PNPM_HOME`
-- **CI/CD:** `CI`, `VERCEL_*`, `NEXT_*`, `GITHUB_*`, `RUNNER_*`, `ACTIONS_ID_TOKEN_REQUEST_URL`, `ACTIONS_ID_TOKEN_REQUEST_TOKEN`
-- **Terminal:** Color variables (`FORCE_COLOR`, `NO_COLOR`, `COLORTERM`, `TERM`, `TERM_PROGRAM`) aren't passed to tasks unless you list them under `env` (the value gets fingerprinted, so changing it invalidates the cache) or `untrackedEnv` (passed without fingerprinting). If `FORCE_COLOR` isn't in either list, the child gets `FORCE_COLOR=1` so cached logs stay colored. Colors get stripped on display when the terminal can't render them.
+- **System:** `HOME`, `USER`, `PATH`, `SHELL`, `LANG`, `TZ`, `TMP`, `TEMP`
+- **Node.js and package managers:** `NODE_OPTIONS`, `NPM_CONFIG_STORE_DIR`, `PNPM_HOME`
+- **CI:** `CI`, `VERCEL_*`, `NEXT_*`, `GITHUB_*`, `RUNNER_*`, `ACTIONS_ID_TOKEN_REQUEST_URL`
+- **Windows:** `APPDATA`, `LOCALAPPDATA`, `SYSTEMROOT`, `USERPROFILE`
+- **Development tools:** `VSCODE_*`, `JB_IDE_*`, `DOCKER_*`, `BUILDKIT_*`, `COMPOSE_*`, `PLAYWRIGHT_*`
+- **Tokens:** `*_TOKEN`, including `ACTIONS_ID_TOKEN_REQUEST_TOKEN`
+
+Color variables such as `FORCE_COLOR`, `NO_COLOR`, `COLORTERM`, `TERM`, and `TERM_PROGRAM` require an explicit `env` or `untrackedEnv` entry. If `FORCE_COLOR` isn't listed, Vite Task sets `FORCE_COLOR=1` to keep cached logs colored. Colors are stripped on display when the terminal can't render them.
 
 ### `cache.input`
 

package/docs/config/staged.md

@@ -9,7 +9,7 @@ import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
   staged: {
-    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+    '*': 'vp check --fix',
   },
 });
 ```

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

@@ -10,10 +10,10 @@ Use this page when you need to understand why a task hits or misses the cache, o
 
 Automatic data tracking has two tiers:
 
-| Tier                 | Applies to                               | Records                                                                                                                                                         |
-| -------------------- | ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| File system tracking | All tasks with cache enabled             | <ul><li>Files read by the command</li><li>Missing-file probes</li><li>Directory listings</li><li>Written output files</li></ul>                                 |
-| Cooperative tracking | Cache-reporting tools (`vp build` today) | <ul><li>Environment variables reported by the tool</li><li>Tool-managed paths that should not be inputs or outputs, such as `node_modules/.vite-temp`</li></ul> |
+| Tier                 | Applies to                                    | Records                                                                                                                                                         |
+| -------------------- | --------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| File system tracking | All tasks with cache enabled                  | <ul><li>Files read by the command</li><li>Missing-file probes</li><li>Directory listings</li><li>Written output files</li></ul>                                 |
+| Cooperative tracking | Cache-reporting tools (`vp build`, `vp test`) | <ul><li>Environment variables reported by the tool</li><li>Tool-managed paths that should not be inputs or outputs, such as `node_modules/.vite-temp`</li></ul> |
 
 Vite Task starts with file system tracking for any command. A cache-reporting tool can add information that only the tool knows while it runs.
 
@@ -114,9 +114,10 @@ File system tracking records access. It cannot know why a tool used each path.
 For a standard Vite build, you do not need to add these entries yourself because Vite reports them automatically at runtime:
 
 - `env: ['VITE_*']` or `env: ['NODE_ENV']`
-- `output: ['dist/**']`
 - input or output exclusions for temporary paths like `node_modules/.vite-temp`
 
+Build outputs such as `dist` are captured by automatic file-write tracking and restored on cache hits.
+
 You only need to define the task with `vp build`:
 
 ```ts [vite.config.ts]
@@ -135,7 +136,7 @@ Run this task with `vpr frontendBuild` or `vp run frontendBuild`.
 
 Manual config overrides reported metadata. Add `cache.input`, `cache.output`, `cache.env`, or `cache.untrackedEnv` when your project has behavior that Vite cannot report.
 
-Vite+ supports cooperative tracking for `vp build` today. It will extend this support to more first-party tools in the future. Third-party tools can report cache metadata with [`@voidzero-dev/vite-task-client`](https://npmx.dev/package/@voidzero-dev/vite-task-client).
+Vite+ supports cooperative tracking for `vp build` and `vp test`. `vp test` reports Vitest's on-disk cache paths (`node_modules/.vitest-cache` and the results cache under the Vite cache directory) so they neither invalidate the task nor get restored into it. It will extend this support to more first-party tools in the future. Third-party tools can report cache metadata with [`@voidzero-dev/vite-task-client`](https://npmx.dev/package/@voidzero-dev/vite-task-client).
 
 ## When To Add Manual Config
 

package/docs/guide/cache.md

@@ -15,9 +15,9 @@ When all checks match, Vite Task replays the cached terminal output, restores sa
 When a cache miss occurs, Vite Task tells you exactly why:
 
 ```
-$ vp lint ✗ cache miss: 'src/utils.ts' modified, executing
-$ vp build ✗ cache miss: env 'VITE_GREETING' changed, executing
-$ vp test ✗ cache miss: args changed, executing
+$ vp lint ○ cache miss: 'src/utils.ts' modified, executing
+$ vp build ○ cache miss: env 'VITE_GREETING' changed, executing
+$ vp test ○ cache miss: args changed, executing
 ```
 
 ## When Is Caching Enabled?

package/docs/guide/check.md

@@ -6,19 +6,19 @@
 
 `vp check` is the default command for fast static checks in Vite+. It brings together formatting through [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), linting through [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), and TypeScript type checks through [tsgolint](https://github.com/oxc-project/tsgolint). By merging all of these tasks into a single command, `vp check` is faster than running formatting, linting, and type checking as separate tools in separate commands.
 
-When `typeCheck` is enabled in the `lint.options` block in `vite.config.ts`, `vp check` also runs TypeScript type checks through the Oxlint type-aware path powered by the TypeScript Go toolchain and [tsgolint](https://github.com/oxc-project/tsgolint). `vp create` and `vp migrate` enable both `typeAware` and `typeCheck` by default.
+When both `typeAware` and `typeCheck` are enabled in the `lint.options` block in `vite.config.ts`, `vp check` also runs TypeScript type checks through the Oxlint type-aware path powered by the TypeScript Go toolchain and [tsgolint](https://github.com/oxc-project/tsgolint). `vp create` and `vp migrate` enable both `typeAware` and `typeCheck` by default.
 
-We recommend turning `typeCheck` on so `vp check` becomes the single command for static checks during development.
+We recommend turning both `typeAware` and `typeCheck` on so `vp check` becomes the single command for static checks during development.
 
 ## Usage
 
 ```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).
+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 both `typeAware` and `typeCheck` enabled).
 ```
 
 ## Configuration

package/docs/guide/commit-hooks.md

@@ -74,6 +74,8 @@ vp config --no-agent
 
 Use `--no-hooks` when you want `vp config` to leave the Git hook dispatcher unchanged. Use `--no-agent` when you want it to skip updates to existing coding agent instruction files. You can pass both flags when you want `vp config` to skip both setup steps. After `vp hooks disable`, `vp config` skips reinstalling the dispatcher and points you at `vp hooks enable` instead of prompting again.
 
+If `core.hooksPath` points to another hook directory, `vp config` skips dispatcher installation to preserve the existing setup. Run `vp hooks status` to inspect the current configuration.
+
 You can also set `VP_GIT_HOOKS=0` to disable hook installation from lifecycle scripts such as `prepare` or `postinstall`.
 
 Project-owned hook scripts such as `.vite-hooks/pre-commit` should be committed to the repository. The generated dispatcher and shims under `.vite-hooks/_` are ignored and recreated by `vp config` or `vp hooks enable`. Neither command creates or modifies project hook scripts or staged-file configuration.
@@ -108,7 +110,7 @@ import { defineConfig } from 'vite-plus';
 
 export default defineConfig({
   staged: {
-    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+    '*': 'vp check --fix',
   },
 });
 ```

package/docs/guide/create.md

@@ -20,6 +20,40 @@ vp create <template>
 vp create <template> -- <template-options>
 ```
 
+### Without the Global CLI
+
+If you haven't installed [the global `vp`](/guide/global-cli) yet. Vite+ provides `create-vite-plus` package running `vp create` through your package manager.
+
+::: code-group
+
+```bash [pnpm]
+pnpm create vite-plus
+```
+
+```bash [npm]
+npm create vite-plus@latest
+```
+
+```bash [Yarn]
+yarn create vite-plus
+```
+
+```bash [Bun]
+bun create vite-plus
+```
+
+:::
+
+The new project uses the package manager that ran the command, unless you pass `--package-manager` or create it inside an existing workspace. Arguments are forwarded to `vp create` unchanged, so the first argument is the template, not the target directory:
+
+```bash
+pnpm create vite-plus vite:application --directory my-app
+```
+
+If you are using npm, there is a `--` needed before options meant for `vp create`, for example `npm create vite-plus@latest -- vite:application --directory my-app`.
+
+After creating the project, run `vp` through your package manager, for example `pnpm exec vp run`.
+
 ## Built-in Templates
 
 Vite+ ships with these built-in templates:
@@ -42,12 +76,12 @@ Run `vp create --list` to see the built-in templates and the common shorthand te
 
 ## Options
 
-- `--directory <dir>` writes the generated project into a specific target directory
+- `--directory <dir>` writes the generated project into a specific target directory. Only built-in templates and bundled `@org` templates support this option.
 - `--agent <name>` creates agent instructions files during scaffolding
 - `--no-agent` skips agent instruction setup
 - `--editor <name>` writes editor config files
 - `--no-editor` skips editor config setup
-- `--git` initialize a git repository
+- `--git` initializes a git repository
 - `--no-git` skips git repository initialization
 - `--package-manager <name>` uses a specified package manager (`pnpm`, `npm`, `yarn`, or `bun`)
 - `--approve-builds` approves and runs gated dependency build scripts without prompting
@@ -57,6 +91,10 @@ Run `vp create --list` to see the built-in templates and the common shorthand te
 - `--hooks` enables pre-commit hook setup (dispatcher + `.vite-hooks` + `staged` config)
 - `--no-hooks` skips hook setup
 
+::: info
+`--git` and `--no-git` are not available when adding a package to an existing monorepo.
+:::
+
 After create, manage the dispatcher with `vp hooks status`, `vp hooks disable`, and `vp hooks enable`. See the [Commit hooks guide](/guide/commit-hooks).
 
 ### Dependency build scripts
@@ -130,7 +168,9 @@ If the monorepo has a parent directory matching `generators` or `tools`, the new
 
 Local generators are declared in [`create.templates`](/config/create#create-templates) in the monorepo's `vite.config.ts`. This is the source of truth: only registered templates appear in the `vp create` picker.
 
-`vp create vite:generator` registers the generator for you, adding an entry to `create.templates` in the root `vite.config.ts`:
+`vp create vite:generator` registers the generator for you, adding an entry to `create.templates` in the root `vite.config.ts`.
+
+For example, a generator named `my-generator` created in `generators/my-generator` is registered as follows:
 
 ```ts
 import { defineConfig } from 'vite-plus';
@@ -138,7 +178,11 @@ import { defineConfig } from 'vite-plus';
 export default defineConfig({
   create: {
     templates: [
-      { name: 'my-generator', description: 'Generate new components', template: 'my-generator' },
+      {
+        name: 'my-generator',
+        description: 'A starter for creating a Vite+ code generator.',
+        template: './generators/my-generator',
+      },
     ],
   },
 });

package/docs/guide/env.md

@@ -46,13 +46,16 @@ If no directory declares a version, Vite+ uses the global default (`vp env defau
 ::: 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):
+If your project uses Vite+ to manage Node.js and pnpm versions, add these settings to the project's `pnpm-workspace.yaml` (pnpm 11+):
 
-```bash
-pnpm config set --global runtimeOnFail ignore
+```yaml
+runtimeOnFail: ignore
+pmOnFail: 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.
+[`runtimeOnFail`](https://pnpm.io/settings/cli#runtimeonfail) disables pnpm's automatic management of declared runtimes. [`pmOnFail`](https://pnpm.io/settings/cli#pmonfail) prevents pnpm from switching to the package-manager version declared in `package.json`. Commit these settings so the project shares the same policy.
+
+`runtimeOnFail: ignore` also affects other declared runtimes, including Bun and Deno. If the project relies on pnpm to manage them, consider that before enabling this setting. Switching an existing project to this policy can change runtime entries in `pnpm-lock.yaml` on the next install; review and commit those changes with the configuration.
 :::
 
 ## Package-Manager Selection
@@ -76,7 +79,7 @@ Package-manager selection uses this priority:
 | `VP_YARN_VERSION` | `yarn`, `yarnpkg`           |
 | `VP_BUN_VERSION`  | `bun`, `bunx`               |
 
-These variables accept a version or range, such as `10.18.0`, `10`, or `latest`, and override the matching shim's project and default versions. They do not change the manager or version selected by `vp install`.
+These variables accept a version, range, or npm dist-tag, such as `10.18.0`, `10`, `latest`, or `latest-10`, and override the matching shim's project and default versions. They do not change the manager or version selected by `vp install`.
 
 `vp env use pnpm@10.20.0` sets `VP_PNPM_VERSION` for the current shell, just as `vp env use node@22` sets `VP_NODE_VERSION`. Each package manager has its own override, so switching Yarn does not clear a pnpm override. `vp env use` does not set or clear `VP_PACKAGE_MANAGER`.
 
@@ -87,12 +90,14 @@ VP_PACKAGE_MANAGER=pnpm@10.18.0 vp install
 VP_PNPM_VERSION=10.20.0 pnpm --version
 ```
 
-The overrides apply in managed mode. A package manager can also perform its own version switching after Vite+ launches it; for example, pnpm's `managePackageManagerVersions` setting may switch back to the version in `package.json`.
+The overrides apply in managed mode. A package manager can also perform its own version switching after Vite+ launches it; for example, pnpm 11+'s [`pmOnFail`](https://pnpm.io/settings/cli#pmonfail) defaults to `download` and may switch back to the version in `package.json`. To let Vite+ control the pnpm version, set `pmOnFail: ignore` in the project's `pnpm-workspace.yaml`. In pnpm 10, the corresponding setting is `managePackageManagerVersions`.
 
 A project selection applies only to its matching shims. For example, pnpm controls `pnpm`, `pnpx`, `pn`, and `pnx`; invoking `npm` still resolves npm independently. Without a matching project selection, a named shim uses its configured default version and otherwise uses the latest release without prompting. The npm shim falls back to Node's bundled npm. `vp env use npm` selects standalone npm's latest release for the current shell when no project version or global default is configured.
 
-::: details Latest-version caching
-When a named shim falls back to the latest release, the resolved version is cached for one hour. An expired cache remains available when the registry cannot be reached.
+Package-manager specs follow npm's order: an exact version, then a semver range, then a dist-tag. `default` is an alias of `latest`, except for npm, where it selects the npm on `PATH`.
+
+::: details Dist-tag caching
+When a package-manager dist-tag such as `latest` or `latest-10` is resolved, including a named shim falling back to the latest release, the resolved version is cached for one hour. An expired cache remains available when the registry cannot be reached.
 :::
 
 `pn` runs the same managed binary as `pnpm`, and `pnx` runs the same managed binary as `pnpx` (`pnpm dlx`). These aliases also work with managed pnpm versions older than v11.
@@ -171,15 +176,22 @@ Only `vp env use` needs this alternate command. Other `vp env` commands work nor
 
 In CI, `vp env use` can run without shell initialization. It writes a temporary session file per runtime or package manager in the resolved state directory, such as `.session-node-version` or `.session-pnpm-version`. Later shim calls in the same job use these files to resolve the same environment.
 
+#### Shell completion
+
+The global CLI supports Tab completion in Bash, Zsh, Fish, Nushell, and PowerShell. Run `vp env setup` and follow its printed shell setup instructions to enable it. Press Tab to complete commands, or project task names after `vp run` and `vpr`.
+
+- **Zsh**: Run `autoload -Uz compinit; compinit` before loading the setup script if your shell has not initialized completion.
+- **Nushell**: Completion requires `fish` on `PATH`.
+
 ### Manage
 
 - `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 default <lts|latest>` and `<package-manager>@latest` re-resolve on each use, so the default follows new releases, including new majors. Other versions and ranges, such as `24` or `pnpm@10`, resolve to an exact version when set.
+- `vp env default <lts|latest>` and package-manager dist-tags such as `pnpm@latest` or `pnpm@latest-10` re-resolve on each use, so the default follows the tag, including new majors for `latest`. Other versions and ranges, such as `24` or `pnpm@10`, resolve to an exact version when set.
 - `vp env pin` shows or writes project pins. Existing `.node-version` and top-level `packageManager` fields keep being updated for compatibility. An existing `.nvmrc` is updated when it is the effective Node source in the current directory; its comments and other non-version content are preserved. Otherwise Vite+ writes the matching `devEngines` entry. Use `--target node-version`, `--target nvmrc`, `--target dev-engines`, or `--target package-manager` to choose explicitly. Pinning in a child directory does not modify an inherited `.nvmrc`.
 - `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 uninstall` removes the Node.js version resolved from an explicit version or selector, such as `22` or `lts`. Package managers require a qualified exact version, such as `pnpm@10.18.0`.
 - `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.
@@ -187,7 +199,7 @@ In CI, `vp env use` can run without shell initialization. It writes a temporary
 ### Inspect
 
 - `vp env current` shows the current resolved environment
-- `vp env doctor` runs environment diagnostics
+- `vp env doctor` runs environment diagnostics. Append `node` to focus on Node.js, `pm` for all package managers, or `npm`, `pnpm`, `yarn`, or `bun` for a specific package manager.
 - `vp env which` shows which tool path will be used
 - `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.
@@ -210,7 +222,9 @@ vp env print                  # Print PATH setup for both components
 
 # Manage
 vp env pin lts                # Pin Node.js only to an exact version
+vp env pin node@26            # Pin Node.js 26 to an exact version
 vp env pin lts pnpm@10        # Pin both project components to exact versions
+vp env pin pnpm@latest-10     # Pin pnpm to the version of its latest-10 dist-tag
 vp env install                # Install the complete resolved environment
 vp env use 20 pnpm@10         # Override both components for this shell
 vp env use --unset pnpm       # Remove only the pnpm session version

package/docs/guide/github-actions-cache.md

@@ -56,7 +56,7 @@ Run each task twice:
 vp run build
 vp run build # should print "cache hit"
 vp run lint
-vp run lint # should print "cache hit"
+vp run lint  # should print "cache hit"
 ```
 
 ## 2. Restore The Cache After Install