vite-plus 1.0.0-rc.0 → 1.0.0

package/docs/config/run.md

@@ -80,7 +80,7 @@ tasks: {
 }
 ```
 
-Use the object form when a task needs other fields like `cache`, `dependsOn`, `env`, or `input`.
+Use the object form when a task needs other fields like `cache`, `dependsOn`, or `cwd`.
 
 ### `command`
 
@@ -156,10 +156,26 @@ See [Task Dependencies](/guide/run#task-dependencies) for details on how explici
 
 ### `cache`
 
-- **Type:** `boolean`
+- **Type:** `boolean | { env?: string[], untrackedEnv?: string[], input?: Array<...>, output?: Array<...> }`
 - **Default:** `true`
 
-Whether to cache this task's output. Set to `false` for tasks that should never be cached, like dev servers:
+Whether and how to cache this task. Caching is enabled with default settings when `cache` is omitted, `true`, or `{}`.
+
+Use an object to configure how the task is cached with [`cache.env`](#cache-env), [`cache.untrackedEnv`](#cache-untrackedenv), [`cache.input`](#cache-input), and [`cache.output`](#cache-output):
+
+```ts [vite.config.ts]
+tasks: {
+  build: {
+    command: 'node build.mjs',
+    cache: {
+      env: ['NODE_ENV'],
+      input: [{ auto: true }, '!dist/**'],
+    },
+  },
+}
+```
+
+Set `cache` to `false` for tasks that should never be cached, like dev servers:
 
 ```ts [vite.config.ts]
 tasks: {
@@ -170,7 +186,7 @@ tasks: {
 }
 ```
 
-### `env`
+### `cache.env`
 
 - **Type:** `string[]`
 - **Default:** `[]`
@@ -181,7 +197,9 @@ Environment variables included in the cache fingerprint. When any listed variabl
 tasks: {
   build: {
     command: 'node build.mjs',
-    env: ['NODE_ENV'],
+    cache: {
+      env: ['NODE_ENV'],
+    },
   },
 }
 ```
@@ -195,7 +213,7 @@ $ NODE_ENV=development vp run build    # first run
 $ NODE_ENV=production vp run build     # cache miss: env 'NODE_ENV' changed
 ```
 
-### `untrackedEnv`
+### `cache.untrackedEnv`
 
 - **Type:** `string[]`
 - **Default:** see below
@@ -206,12 +224,14 @@ Environment variables passed to the task process but **not** included in the cac
 tasks: {
   build: {
     command: 'node build.mjs',
-    untrackedEnv: ['CI', 'GITHUB_ACTIONS'],
+    cache: {
+      untrackedEnv: ['CI', 'GITHUB_ACTIONS'],
+    },
   },
 }
 ```
 
-`untrackedEnv` accepts the same wildcard and `!` exclusion patterns as [`env`](#env).
+`untrackedEnv` accepts the same wildcard and `!` exclusion patterns as [`env`](#cache-env).
 
 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`.
 
@@ -222,7 +242,7 @@ Vite Task passes a set of common environment variables to all tasks:
 - **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.
 
-### `input`
+### `cache.input`
 
 - **Type:** `Array<string | { auto: boolean } | { pattern: string, base: "workspace" | "package" }>`
 - **Default:** `[{ auto: true }]` (auto-inferred)
@@ -235,8 +255,10 @@ Vite Task automatically detects which files a command uses. See [Automatic Data
 tasks: {
   build: {
     command: 'vp build',
-    // Use `{ auto: true }` to use automatic fingerprinting (default).
-    input: [{ auto: true }, '!**/*.tsbuildinfo', '!dist/**'],
+    cache: {
+      // Use `{ auto: true }` to use automatic fingerprinting (default).
+      input: [{ auto: true }, '!**/*.tsbuildinfo', '!dist/**'],
+    },
   },
 }
 ```
@@ -247,7 +269,9 @@ tasks: {
 tasks: {
   build: {
     command: 'vp build',
-    input: ['src/**/*.ts', 'vite.config.ts'],
+    cache: {
+      input: ['src/**/*.ts', 'vite.config.ts'],
+    },
   },
 }
 ```
@@ -258,10 +282,12 @@ tasks: {
 tasks: {
   build: {
     command: 'vp build',
-    input: [
-      { auto: true },
-      { pattern: 'shared-config/**', base: 'workspace' },
-    ],
+    cache: {
+      input: [
+        { auto: true },
+        { pattern: 'shared-config/**', base: 'workspace' },
+      ],
+    },
   },
 }
 ```
@@ -277,7 +303,9 @@ The `base` field is required and controls how the glob pattern is resolved:
 tasks: {
   greet: {
     command: 'node greet.mjs',
-    input: [],
+    cache: {
+      input: [],
+    },
   },
 }
 ```
@@ -286,7 +314,7 @@ tasks: {
 String glob patterns are resolved relative to the package directory by default. Use the object form with `base: "workspace"` to resolve relative to the workspace root.
 :::
 
-### `output`
+### `cache.output`
 
 - **Type:** `Array<string | { auto: boolean } | { pattern: string, base: "workspace" | "package" }>`
 - **Default:** automatic write tracking
@@ -299,7 +327,9 @@ If you omit `output`, Vite Task uses automatic write tracking to choose those fi
 tasks: {
   build: {
     command: 'node build.mjs',
-    output: ['dist/**', '!dist/cache/**'],
+    cache: {
+      output: ['dist/**', '!dist/cache/**'],
+    },
   },
 }
 ```
@@ -312,7 +342,9 @@ This is useful when a task writes files that should not be restored from the cac
 tasks: {
   typecheck: {
     command: 'tsc --build',
-    output: [{ auto: true }, '!*.tsbuildinfo'],
+    cache: {
+      output: [{ auto: true }, '!*.tsbuildinfo'],
+    },
   },
 }
 ```
@@ -323,10 +355,12 @@ If a task writes outside its own package, use the object form with `base: "works
 tasks: {
   build: {
     command: 'node build.mjs',
-    output: [
-      'dist/**',
-      { pattern: 'shared-artifacts/**', base: 'workspace' },
-    ],
+    cache: {
+      output: [
+        'dist/**',
+        { pattern: 'shared-artifacts/**', base: 'workspace' },
+      ],
+    },
   },
 }
 ```
@@ -337,7 +371,9 @@ Set `output: []` to disable output restoration for a cached task:
 tasks: {
   report: {
     command: 'node scripts/report.mjs',
-    output: [],
+    cache: {
+      output: [],
+    },
   },
 }
 ```

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

@@ -4,7 +4,7 @@ Automatic data tracking is how Vite Task learns what inputs a task needs for cac
 
 When you run a cache-enabled task, Vite Task observes the task's execution and records what files were read and written, as well as any metadata reported by the task. On the next run, Vite Task uses the recorded fingerprint to decide whether to replay the cache or run the task.
 
-Use this page when you need to understand why a task hits or misses the cache, or when you need to decide whether to add `input`, `output`, `env`, or `untrackedEnv` config.
+Use this page when you need to understand why a task hits or misses the cache, or when you need to decide whether to add `cache.input`, `cache.output`, `cache.env`, or `cache.untrackedEnv` config.
 
 ## Tracking Tiers
 
@@ -19,7 +19,7 @@ Vite Task starts with file system tracking for any command. A cache-reporting to
 
 ## File System Tracking
 
-File system tracking applies to every cache-enabled task. If you omit [`input`](/config/run#input), Vite Task tracks the files a command reads while it runs:
+File system tracking applies to every cache-enabled task. If you omit [`cache.input`](/config/run#cache-input), Vite Task tracks the files a command reads while it runs:
 
 ```ts [vite.config.ts]
 import { defineConfig } from 'vite-plus';
@@ -37,7 +37,7 @@ export default defineConfig({
 
 For this task, Vite Task records source files, config files, missing files the command checked, and directories the command scanned. Subsequent runs re-run the task when one of those tracked inputs changes.
 
-File system tracking also tracks outputs. If you omit [`output`](/config/run#output), Vite Task archives files the command writes after a successful run and restores them on a cache hit.
+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.
 
 ### Limitations
 
@@ -45,13 +45,13 @@ Vite Task cannot track environment variable reads, and it cannot always tell whi
 
 Use [Override Inputs And Outputs](#override-inputs-and-outputs) when file system tracking includes files that should not affect the cache, misses files that should, or restores the wrong outputs.
 
-Use [`env`](/config/run#env) when a command needs an environment variable and the value should affect the cache, or [`untrackedEnv`](/config/run#untrackedenv) when the value should not affect the cache.
+Use [`cache.env`](/config/run#cache-env) when a command needs an environment variable and the value should affect the cache, or [`cache.untrackedEnv`](/config/run#cache-untrackedenv) when the value should not affect the cache.
 
 These limitations do not apply to `vp build`: Vite reports [Cooperative Tracking](#cooperative-tracking) metadata automatically, including `VITE_*`, `NODE_ENV`, and Vite-managed cache paths that should not become inputs or outputs. A standard `vp build` task does not need manual `input`, `output`, or `env`.
 
 ### Override Inputs And Outputs
 
-[`input`](/config/run#input) controls what invalidates the cache. [`output`](/config/run#output) controls which files Vite Task restores on a cache hit.
+[`cache.input`](/config/run#cache-input) controls what invalidates the cache. [`cache.output`](/config/run#cache-output) controls which files Vite Task restores on a cache hit.
 
 Both options use the same syntax and can be configured separately.
 
@@ -65,12 +65,13 @@ Both options use the same syntax and can be configured separately.
 tasks: {
   build: {
     command: 'node build.mjs',
+    cache: {
+      // Keep automatic input tracking, but exclude `dist` from inputs.
+      input: [{ auto: true }, '!dist/**'],
 
-    // Keep automatic input tracking, but exclude `dist` from inputs.
-    input: [{ auto: true }, '!dist/**'],
-
-    // Disable automatic output tracking and restore only `dist/**` on a cache hit.
-    output: ['dist/**'],
+      // Disable automatic output tracking and restore only `dist/**` on a cache hit.
+      output: ['dist/**'],
+    },
   },
 }
 ```
@@ -81,8 +82,10 @@ Use explicit `input` globs only when you know the command's full input set. This
 tasks: {
   lint: {
     command: 'vp lint',
-    // Disable automatic input tracking and fingerprint only these files.
-    input: ['src/**', 'vite.config.ts'],
+    cache: {
+      // Disable automatic input tracking and fingerprint only these files.
+      input: ['src/**', 'vite.config.ts'],
+    },
   },
 }
 ```
@@ -93,7 +96,9 @@ Set `input: []` when no files should affect the cache fingerprint. This is rarel
 tasks: {
   downloadSchema: {
     command: 'curl -O https://example.com/schema.json',
-    input: [],
+    cache: {
+      input: [],
+    },
   },
 }
 ```
@@ -128,13 +133,13 @@ export default defineConfig({
 
 Run this task with `vpr frontendBuild` or `vp run frontendBuild`.
 
-Manual config overrides reported metadata. Add `input`, `output`, `env`, or `untrackedEnv` when your project has behavior that Vite cannot report.
+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).
 
 ## When To Add Manual Config
 
-Add config when your project has behavior the command or tool cannot know.
+Add config when your project has behavior the command or tool cannot know. These options go under the task's [`cache`](/config/run#cache) object.
 
 | Case                                                              | Example                                                                                         |
 | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |

package/docs/guide/cache.md

@@ -7,7 +7,7 @@ Vite Task can automatically track dependencies and cache tasks run through `vp r
 When a task runs successfully (exit code 0), its terminal output (stdout/stderr) and all written files (output files) are saved. On the next run, Vite Task checks if anything changed:
 
 1. **Arguments:** did the [additional arguments](/guide/run#additional-arguments) passed to the task change?
-2. **Environment variables:** did any [fingerprinted env vars](/config/run#env) change?
+2. **Environment variables:** did any [fingerprinted env vars](/config/run#cache-env) change?
 3. **Inputs:** did any input file that the command reads change?
 
 When all checks match, Vite Task replays the cached terminal output, restores saved output files, and skips the command.
@@ -50,14 +50,16 @@ Vite Task uses [automatic data tracking](/guide/automatic-data-tracking) to lear
 - **File system tracking:** Vite Task records file reads, missing-file probes, directory listings, and written output files for every task with cache enabled.
 - **Cooperative tracking:** cache-reporting tools can report metadata that file system tracking cannot infer. Vite+ supports this for `vp build` today.
 
-Use [`input`](/config/run#input) or [`output`](/config/run#output) when a task needs manual tracking rules. `input` controls what invalidates the cache. `output` controls which files Vite Task restores on a cache hit.
+Use [`cache.input`](/config/run#cache-input) or [`cache.output`](/config/run#cache-output) when a task needs manual tracking rules. `input` controls what invalidates the cache. `output` controls which files Vite Task restores on a cache hit.
 
 ```ts [vite.config.ts]
 tasks: {
   build: {
     command: 'node build.mjs',
-    input: [{ auto: true }, '!dist/**'],
-    output: ['dist/**'],
+    cache: {
+      input: [{ auto: true }, '!dist/**'],
+      output: ['dist/**'],
+    },
   },
 }
 ```
@@ -66,20 +68,22 @@ tasks: {
 
 By default, tasks run in a clean environment. Only a small set of common variables, such as `PATH`, `HOME`, and `CI`, are passed through. Other environment variables are neither visible to the task nor included in the cache fingerprint.
 
-To add an environment variable to the cache key, add it to [`env`](/config/run#env). Changing its value then invalidates the cache:
+To add an environment variable to the cache key, add it to [`cache.env`](/config/run#cache-env). Changing its value then invalidates the cache:
 
 ```ts [vite.config.ts]
 tasks: {
   build: {
     command: 'webpack --mode production',
-    env: ['NODE_ENV'],
+    cache: {
+      env: ['NODE_ENV'],
+    },
   },
 }
 ```
 
-To pass a variable to the task **without** affecting cache behavior, use [`untrackedEnv`](/config/run#untrackedenv). This is useful for variables like `CI` or `GITHUB_ACTIONS` that should be available in the task, but do not affect caching behavior.
+To pass a variable to the task **without** affecting cache behavior, use [`cache.untrackedEnv`](/config/run#cache-untrackedenv). This is useful for variables like `CI` or `GITHUB_ACTIONS` that should be available in the task, but do not affect caching behavior.
 
-See [Run Config](/config/run#env) for details on wildcard patterns and the full list of automatically passed-through variables.
+See [Run Config](/config/run#cache-env) for details on wildcard patterns and the full list of automatically passed-through variables.
 
 ## Cache Sharing
 

package/docs/guide/fmt.md

@@ -20,9 +20,11 @@ vp fmt . --write
 
 Put formatting configuration directly in the `fmt` block in the root `vite.config.ts` so all your configuration stays in one place. We do not recommend using `.oxfmtrc.json` with Vite+.
 
-When the workspace-root config has a `fmt` block, `vp fmt` and `vp check` use it even when run from a package directory. Package configs cannot replace the root format settings. Commands keep the package working directory, so relative file arguments retain their meaning. Use [`fmt.overrides`](/guide/monorepo#format-overrides) for file- or package-specific options.
+`vp fmt` finds its config from the working directory, so package directories without their own `fmt` block use the root config. Relative file arguments retain their meaning. Use [`fmt.overrides`](/guide/monorepo#format-overrides) for file- or package-specific options instead of adding `fmt` blocks to package configs.
 
-An explicit `vp fmt -c <path>` or `vp fmt --config <path>` selects another config. Otherwise, when running from the workspace root or when the root config has no `fmt` block, Oxfmt discovers the nearest `vite.config.*` file with a `fmt` block. Supported extensions are `.js`, `.mjs`, `.ts`, `.cjs`, `.mts`, and `.cts`. Nested configs do not override settings for individual files.
+`vp check` uses the workspace-root `fmt` block when it exists, including from a package directory. Package configs cannot replace those format settings in `vp check`.
+
+An explicit `vp fmt -c <path>` or `vp fmt --config <path>` selects another config. Otherwise, Oxfmt discovers the nearest `vite.config.*` file with a `fmt` block. Supported extensions are `.js`, `.mjs`, `.ts`, `.cjs`, `.mts`, and `.cts`. Nested configs do not override settings for individual files.
 
 For editors, disable nested formatter configs to prevent per-file overrides:
 

package/docs/guide/lint.md

@@ -20,9 +20,11 @@ vp lint --type-aware
 
 Put lint configuration directly in the `lint` block in the root `vite.config.ts` so all your configuration stays in one place. We do not recommend using `oxlint.config.ts` or `.oxlintrc.json` with Vite+.
 
-When the workspace-root config has a `lint` block, `vp lint` and `vp check` use it even when run from a package directory. Package configs cannot replace the root rules or disable its `typeAware` and `typeCheck` options. Commands keep the package working directory, so relative file arguments retain their meaning. Use [`lint.overrides`](/guide/monorepo#root-config-with-overrides) for file- or package-specific rules.
+`vp lint` finds its config from the working directory, so package directories without their own `lint` block use the root config. Relative file arguments retain their meaning. Use [`lint.overrides`](/guide/monorepo#root-config-with-overrides) for file- or package-specific rules instead of adding `lint` blocks to package configs.
 
-An explicit `vp lint -c <path>` or `vp lint --config <path>` selects another config. Otherwise, when running from the workspace root or when the root config has no `lint` block, Oxlint discovers the nearest `vite.config.*` file with a `lint` block. Supported extensions are `.js`, `.mjs`, `.ts`, `.cjs`, `.mts`, and `.cts`. Nested configs do not override settings for individual files.
+`vp check` uses the workspace-root `lint` block when it exists, including from a package directory. Package configs cannot replace those lint settings in `vp check`.
+
+An explicit `vp lint -c <path>` or `vp lint --config <path>` selects another config. Otherwise, Oxlint discovers the nearest `vite.config.*` file with a `lint` block. Supported extensions are `.js`, `.mjs`, `.ts`, `.cjs`, `.mts`, and `.cts`. Nested configs do not override settings for individual files.
 
 For the upstream rule set, options, and compatibility details, see the [Oxlint docs](https://oxc.rs/docs/guide/usage/linter.html).
 

package/docs/guide/migrate-rules.md

@@ -52,6 +52,48 @@ When `external` accompanies either `skipNodeModulesBundle` form, static matchers
 
 The transform does not evaluate configuration code. Objects with spreads, computed keys, or duplicate keys, and conflicting old and new options require manual review. Dynamic boolean selectors remain unchanged. Unrelated Vite and plugin options remain unchanged. Run `vp pack` after migration to check the result. Node.js requirements, TypeScript module resolution, and programmatic `build()` return values require separate review.
 
+## Task Cache Configuration
+
+`vp migrate` moves `env`, `untrackedEnv`, `input`, and `output` from the top level of each task into the task's [`cache`](/config/run#cache) object. It updates static `run.tasks` objects in `vite.config.*`. This also runs on existing Vite+ projects without `--full`, including workspace packages.
+
+| Previous task config | Updated task config                            |
+| -------------------- | ---------------------------------------------- |
+| No `cache`           | Adds `cache` with the moved settings           |
+| `cache: true`        | Replaces `true` with the moved settings        |
+| `cache: { ... }`     | Adds the moved settings to the existing object |
+
+```ts
+// Before
+build: {
+  command: 'vp build',
+  env: ['NODE_ENV'],
+  input: [{ auto: true }, '!dist/**'],
+},
+
+// After
+build: {
+  command: 'vp build',
+  cache: {
+    env: ['NODE_ENV'],
+    input: [{ auto: true }, '!dist/**'],
+  },
+},
+```
+
+Moved settings keep their text and indentation, and the formatting step described in [After the Migration](#after-the-migration) indents them inside `cache`. Comments on their own line above a moved setting, and `//` comments that follow it on the same line, move with it.
+
+The transform does not evaluate configuration code. It leaves a task unchanged and prints a manual-migration warning when the task has:
+
+- spreads, or computed, escaped, or duplicate keys;
+- a moved setting written as a method, such as `input() { ... }`;
+- a comment between a moved setting and its comma, or after the last setting in `cache`;
+- a moved setting that already exists in `cache`;
+- a `cache` value other than `true` or an object literal.
+
+It also warns about tasks in a `vite.config.*` object that is not the exported config itself, such as a variable the config refers to or an object passed to `mergeConfig`. Tasks created in other modules, for example by a shared helper function, are not detected. Move their settings by hand; `vp run` lists every task that still needs it.
+
+With `cache: false`, the moved settings would have no effect, so decide whether to remove them or enable caching. On a project that is otherwise up to date, `vp migrate` prints these warnings without running the rest of the migration.
+
 ## Dependency Rules
 
 What happens to each toolchain dependency, at a glance:

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.0.0-rc.0` 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.0.0` release:
 
 ::: code-group
 
 ```bash [pnpm]
-pnpm dlx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive
+pnpm dlx --package=vite-plus@1.0.0 vp migrate --no-interactive
 ```
 
 ```bash [npm]
-npx --package=vite-plus@1.0.0-rc.0 vp migrate --no-interactive
+npx --package=vite-plus@1.0.0 vp migrate --no-interactive
 ```
 
 :::
 
-Replace `1.0.0-rc.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.
+Replace `1.0.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:
 

package/docs/guide/monorepo.md

@@ -8,9 +8,11 @@ Because `vite.config.ts` is just JavaScript, you can choose to put your entire c
 
 Run `vp lint`, `vp fmt`, and `vp check` from the workspace root to apply the root lint and format settings across packages. These commands do not apply nested configs to individual files. Define file- or package-specific settings with overrides in the root `vite.config.ts`.
 
-When run from a package directory, `vp lint`, `vp fmt`, and `vp check` still use the root `lint` and `fmt` blocks. Package configs cannot replace root format settings, lint rules, or type-check options. File arguments remain relative to the package working directory.
+When run from a package directory, `vp lint` and `vp fmt` still use the root settings unless the package config defines its own `lint` or `fmt` block. We do not recommend package-level blocks; use overrides in the root config instead. File arguments remain relative to the package working directory.
 
-Use `-c <path>` or `--config <path>` with `vp lint` or `vp fmt` to select another config. If the root config has no block for that tool, the tool uses native discovery from the working directory.
+`vp check` uses the root `lint` and `fmt` blocks when they exist. Package configs cannot replace root format settings, lint rules, or type-check options in `vp check`.
+
+Use `-c <path>` or `--config <path>` with `vp lint` or `vp fmt` to select another config explicitly.
 
 Use `lint.overrides` for Oxlint rules that only apply to some packages:
 

package/docs/guide/run.md

@@ -95,7 +95,9 @@ export default defineConfig({
       build: {
         command: 'vp build',
         dependsOn: ['lint'],
-        env: ['NODE_ENV'],
+        cache: {
+          env: ['NODE_ENV'],
+        },
       },
       deploy: {
         command: 'deploy-script --prod',

package/docs/guide/troubleshooting.md

@@ -26,7 +26,7 @@ The Oxlint type checker path powered by `tsgolint` does not support `baseUrl`. `
 
 ## Nested lint or format config is not applied
 
-When running `vp lint`, `vp fmt`, or `vp check`, configs in subdirectories do not override settings for individual files. Commands run from a package directory still use the workspace-root `lint` and `fmt` blocks when they exist. Use `-c <path>` or `--config <path>` with `vp lint` or `vp fmt` to select another config. If the root config has no block for that tool, the tool uses native discovery from the working directory.
+When running `vp lint`, `vp fmt`, or `vp check`, configs in subdirectories do not override settings for individual files. `vp lint` and `vp fmt` let Oxlint and Oxfmt discover configuration from the working directory, so a `lint` or `fmt` block in a package config takes effect when run from that package, which we do not recommend. `vp check` selects the workspace-root `lint` and `fmt` blocks when they exist. Use `-c <path>` or `--config <path>` with `vp lint` or `vp fmt` to select another config explicitly.
 
 Keep lint and format settings in the root `vite.config.ts`. Use [`lint.overrides`](/guide/monorepo#root-config-with-overrides) and [`fmt.overrides`](/guide/monorepo#format-overrides) for file- or package-specific settings. You can also [import configuration objects](/guide/monorepo#composing-configuration-files) into the root config to keep settings in separate files.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plus",
-  "version": "1.0.0-rc.0",
+  "version": "1.0.0",
   "description": "The Unified Toolchain for the Web",
   "homepage": "https://viteplus.dev/guide",
   "bugs": {
@@ -349,8 +349,8 @@
     "@vitest/utils": "5.0.1",
     "oxfmt": "=0.70.0",
     "oxlint": "=1.85.0",
-    "oxlint-tsgolint": "=7.0.2002",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0-rc.0",
+    "oxlint-tsgolint": "=7.0.2003",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.0.0",
     "vitest": "5.0.1"
   },
   "devDependencies": {
@@ -363,7 +363,7 @@
     "@types/validate-npm-package-name": "^4.0.2",
     "@vitest/browser-playwright": "5.0.1",
     "@vitest/browser-webdriverio": "5.0.0",
-    "@voidzero-dev/vite-plus-prompts": "1.0.0-rc.0",
+    "@voidzero-dev/vite-plus-prompts": "1.0.0",
     "bingo": "^0.9.3",
     "cac": "^7.0.0",
     "cross-spawn": "^7.0.5",
@@ -411,14 +411,14 @@
     "node": "^22.18.0 || ^24.11.0 || >=26.0.0"
   },
   "optionalDependencies": {
-    "@voidzero-dev/vite-plus-darwin-arm64": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-darwin-x64": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-linux-x64-musl": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.0.0-rc.0",
-    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.0.0-rc.0"
+    "@voidzero-dev/vite-plus-darwin-arm64": "1.0.0",
+    "@voidzero-dev/vite-plus-darwin-x64": "1.0.0",
+    "@voidzero-dev/vite-plus-linux-arm64-gnu": "1.0.0",
+    "@voidzero-dev/vite-plus-linux-arm64-musl": "1.0.0",
+    "@voidzero-dev/vite-plus-linux-x64-gnu": "1.0.0",
+    "@voidzero-dev/vite-plus-linux-x64-musl": "1.0.0",
+    "@voidzero-dev/vite-plus-win32-x64-msvc": "1.0.0",
+    "@voidzero-dev/vite-plus-win32-arm64-msvc": "1.0.0"
   },
   "scripts": {
     "build": "oxnode -C dev ./build.ts",

package/dist/dist-Dqv1-Clg.js

@@ -1,3 +0,0 @@
-import { t as require_dist } from "./dist-BDYZP12R.js";
-export default require_dist();
-export {};