vite-plus 1.0.0 → 1.2.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.0.0",
+      "version": "1.2.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@ export const toolchain = {
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@ export const toolchain = {
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.1",
+      "version": "8.3.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@ export const toolchain = {
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.11",
+      "version": "1.2.13",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@ export const toolchain = {
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.1",
+      "version": "5.0.4",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@ export const toolchain = {
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.85.0",
+      "version": "1.88.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@ export const toolchain = {
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.70.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-09-28T02:31:26Z",
+      "revision": "9ba4cc93379cf2d7a6c7e657285bb8a00e8339dc",
+      "builtAt": "2026-10-14T08:52:28Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@ export const toolchain = {
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.151.0",
+      "version": "0.153.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/toolchain.json

@@ -4,7 +4,7 @@
     {
       "id": "vite-plus",
       "name": "vite-plus",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -14,7 +14,7 @@
     {
       "id": "vite-plus-core",
       "name": "@voidzero-dev/vite-plus-core",
-      "version": "1.0.0",
+      "version": "1.2.0",
       "kind": "package",
       "delivery": [
         "dependency"
@@ -26,7 +26,7 @@
     {
       "id": "vite",
       "name": "vite",
-      "version": "8.3.1",
+      "version": "8.3.4",
       "kind": "tool",
       "delivery": [
         "bundled"
@@ -36,7 +36,7 @@
     {
       "id": "rolldown",
       "name": "rolldown",
-      "version": "1.2.11",
+      "version": "1.2.13",
       "kind": "tool",
       "delivery": [
         "bundled",
@@ -47,7 +47,7 @@
     {
       "id": "vitest",
       "name": "vitest",
-      "version": "5.0.1",
+      "version": "5.0.4",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -57,7 +57,7 @@
     {
       "id": "oxlint",
       "name": "oxlint",
-      "version": "1.85.0",
+      "version": "1.88.0",
       "kind": "tool",
       "delivery": [
         "dependency"
@@ -67,7 +67,7 @@
     {
       "id": "oxfmt",
       "name": "oxfmt",
-      "version": "0.70.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-09-28T02:31:26Z",
+      "revision": "9ba4cc93379cf2d7a6c7e657285bb8a00e8339dc",
+      "builtAt": "2026-10-14T08:52:28Z",
       "kind": "tool",
       "delivery": [
         "compiled"
@@ -110,7 +110,7 @@
     {
       "id": "oxc",
       "name": "oxc",
-      "version": "0.151.0",
+      "version": "0.153.0",
       "kind": "engine",
       "delivery": [
         "compiled"

package/dist/tsconfig-C5PnJfW4.js

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

package/dist/{tsconfig-BoYTBNX_.js → tsconfig-D2DzAQ_D.js}

@@ -1,7 +1,7 @@
-import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-BqJiMVVU.js";
+import { p as createBaseUrlTsconfigFixArgs, t as BASEURL_TSCONFIG_FIX_PACKAGE } from "./constants-BW3g7VnD.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 { S as log, b as confirm, k as isCancel, t as cancelAndExit } from "./prompts-jMH8S4Wp.js";
+import { C as confirm, M as isCancel, T as log, t as cancelAndExit } from "./prompts-BGpQtC5z.js";
 import { n as runCommandSilently } from "./command-CguLh2KL.js";
 import path from "node:path";
 import { styleText } from "node:util";

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-BqJiMVVU.js";
-import { i as hasVitePlusDependency, n as detectPackageMetadata } from "./package-Cgdlhamw.js";
+import { y as version } from "./constants-BW3g7VnD.js";
+import { a as hasVitePlusDependency, n as detectPackageMetadata } from "./package-BP16iQby.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.1",
-  "rolldown": "1.2.11",
-  "vitest": "5.0.1",
-  "oxfmt": "0.70.0",
-  "oxlint": "1.85.0",
-  "oxlint-tsgolint": "7.0.2003",
-  "tsdown": "0.23.0"
+  "vite": "8.3.4",
+  "rolldown": "1.2.13",
+  "vitest": "5.0.4",
+  "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/ci.md

@@ -14,20 +14,19 @@ Run `vp migrate` to replace exact `voidzero-dev/setup-vp@v1` references in GitHu
 
 ## GitHub Actions
 
-The GitHub Action sets up Vite+, the required Node.js version, and the package manager. This means you usually do not need separate `setup-node`, package-manager setup, or manual dependency caching steps in your workflow.
+The GitHub Action sets up Vite+, the required Node.js version, and the package manager. This means you usually do not need separate `setup-node`, package-manager setup, dependency installation, or manual dependency caching steps in your workflow.
 
 ```yaml [.github/workflows/ci.yml]
 - uses: voidzero-dev/setup-vp@<setup-vp-version>
   with:
     node-version: '24'
     cache: true
-- run: vp install
 - run: vp check
 - run: vp test
 - run: vp build
 ```
 
-With `cache: true`, `setup-vp` handles dependency caching for you automatically.
+`setup-vp` runs `vp install` by default. If you set `run-install: false`, make sure to add a `vp install` step before running other commands. With `cache: true`, `setup-vp` handles dependency caching for you automatically.
 
 ::: tip
 `setup-vp` caches package-manager data. To reuse Vite Task results across CI runs, add a separate [GitHub Actions cache for Vite Task](/guide/github-actions-cache).
@@ -151,7 +150,7 @@ If you are migrating an existing GitHub Actions workflow, you can often replace
     node-version: '24'
     cache: true
 
-- run: vp install && vp run dev:setup
+- run: vp run dev:setup
 - run: vp check
 - run: vp test
 ```

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

@@ -42,12 +42,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 +57,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 +134,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 +144,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

@@ -171,14 +171,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 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.
@@ -186,7 +194,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.
@@ -208,13 +216,17 @@ vp env off pnpm               # Prefer system pnpm only
 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 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 pnpm       # Remove only the pnpm session version
 vp env use --unset pm         # Remove all package-manager session versions
+
+# Manage (global)
+vp env default lts            # Always use the latest LTS, including new majors
+vp env default node@24        # Pin the Node.js default to an exact version
+vp env default pnpm@10        # Pin the pnpm default to an exact version
 vp env clean                  # Remove unused managed Node.js and package manager versions
 
 # Inspect
@@ -244,7 +256,7 @@ The JSON output for `current`, `list`, and `list-remote` is organized by compone
     "source": "devEngines.runtime",
     "source_path": "/project/package.json",
     "project_root": "/project",
-    "bin_path": "/home/.vite-plus/js_runtime/node/22.0.0/bin/node",
+    "bin_path": "/home/.local/share/vite-plus/js_runtime/node/22.0.0/bin/node",
     "installed": true,
     "mode": "managed"
   },
@@ -255,8 +267,8 @@ The JSON output for `current`, `list`, and `list-remote` is organized by compone
     "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"
+      "pnpm": "/home/.local/share/vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpm",
+      "pnpx": "/home/.local/share/vite-plus/package_manager/pnpm/10.18.0/pnpm/bin/pnpx"
     },
     "installed": true,
     "mode": "managed"

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

@@ -56,12 +56,12 @@ 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
 
-Restore `node_modules/.vite/task-cache` after `vp install`, because package installation can recreate or modify `node_modules`.
+Restore `node_modules/.vite/task-cache` after the `setup-vp` step, because package installation can recreate or modify `node_modules`.
 
 Set `<setup-vp-version>` below 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.
 
@@ -89,8 +89,6 @@ jobs:
           node-version: '24'
           cache: true
 
-      - run: vp install
-
       - name: Restore Vite Task cache
         id: vite-task-cache
         uses: actions/cache/restore@v6