void 0.7.1 → 0.7.3

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/templates/generator/README.md

@@ -0,0 +1,35 @@
+# Vite+ Code Generator Starter
+
+A starter for creating a Vite+ code generator.
+
+## Usage
+
+From monorepo root:
+
+```bash
+# run and select the generator
+vp create
+```
+
+## Development
+
+```bash
+# Edit the template
+code src/template.ts
+
+# Test the generator CLI
+vp run dev
+
+# Run tests
+vp run test
+```
+
+## Customization
+
+Edit `src/template.ts` to customize:
+
+- Options schema (using Zod)
+- File generation logic
+- Scripts and suggestions
+
+More information about the [Bingo Templates](https://create.bingo/) can be found [here](https://create.bingo/build/concepts/creations).

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/templates/monorepo/README.md

@@ -0,0 +1,29 @@
+# Vite+ Monorepo Starter
+
+A starter for creating a Vite+ monorepo.
+
+## Development
+
+- Check everything is ready:
+
+```bash
+vp run ready
+```
+
+- Run the tests:
+
+```bash
+vp run -r test
+```
+
+- Build the monorepo:
+
+```bash
+vp run -r build
+```
+
+- Run the development server:
+
+```bash
+vp run dev
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/AGENTS.md

@@ -0,0 +1,15 @@
+<!--VITE PLUS START-->
+
+# Using Vite+, the Unified Toolchain for the Web
+
+This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, and it invokes Vite through `vp dev` and `vp build`. Run `vp help` to print a list of commands and `vp <command> --help` for information about a specific command.
+
+Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.dev/guide/.
+
+## Review Checklist
+
+- [ ] Run `vp install` after pulling remote changes and before getting started.
+- [ ] Run `vp check` and `vp test` to format, lint, type check and test changes.
+- [ ] Check if there are `vite.config.ts` tasks or `package.json` scripts necessary for validation, run via `vp run <script>`.
+
+<!--VITE PLUS END-->

package/skills/void/docs/node_modules/void/node_modules/vite-plus/README.md

@@ -0,0 +1,208 @@
+# VITE+(⚡︎) Local CLI
+
+**The Unified Toolchain for the Web**
+_runtime and package management, create, dev, check, test, build, pack, and monorepo task caching in a single dependency_
+
+This package provides the project-local version of Vite+. The global `vite` command automatically delegates to this package for all project-specific tasks.
+
+---
+
+Vite+ is the unified entry point for local web development. It combines [Vite](https://vite.dev/), [Vitest](https://vitest.dev/), [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), [Rolldown](https://rolldown.rs/), [tsdown](https://tsdown.dev/), and [Vite Task](https://github.com/voidzero-dev/vite-task) into one zero-config toolchain that also manages runtime and package manager workflows:
+
+- **`vp env`:** Manage Node.js globally and per project
+- **`vp install`:** Install dependencies with automatic package manager detection
+- **`vp dev`:** Run Vite's fast native ESM dev server with instant HMR
+- **`vp check`:** Run formatting, linting, and type checks in one command
+- **`vp test`:** Run tests through bundled Vitest
+- **`vp build`:** Build applications for production with Vite + Rolldown
+- **`vp run`:** Execute monorepo tasks with caching and dependency-aware scheduling
+- **`vp pack`:** Build libraries for npm publishing or standalone app binaries
+- **`vp create` / `vp migrate`:** Scaffold new projects and migrate existing ones
+
+All of this is configured from your project root and works across Vite's framework ecosystem.
+Vite+ is fully open-source under the MIT license.
+
+## Getting Started
+
+Install Vite+ globally as `vp`:
+
+For Linux or macOS:
+
+```bash
+curl -fsSL https://vite.plus | bash
+```
+
+For Windows:
+
+```bash
+irm https://viteplus.dev/install.ps1 | iex
+```
+
+`vp` handles the full development lifecycle such as package management, development servers, linting, formatting, testing and building for production.
+
+## Configuring Vite+
+
+Vite+ can be configured using a single `vite.config.ts` at the root of your project:
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  // Standard Vite configuration for dev/build/preview.
+  plugins: [],
+
+  // Vitest configuration.
+  test: {
+    include: ['src/**/*.test.ts'],
+  },
+
+  // Oxlint configuration.
+  lint: {
+    ignorePatterns: ['dist/**'],
+  },
+
+  // Oxfmt configuration.
+  fmt: {
+    semi: true,
+    singleQuote: true,
+  },
+
+  // Vite Task configuration.
+  run: {
+    tasks: {
+      'generate:icons': {
+        command: 'node scripts/generate-icons.js',
+        envs: ['ICON_THEME'],
+      },
+    },
+  },
+
+  // `vp staged` configuration.
+  staged: {
+    '*': 'vp check --fix',
+  },
+});
+```
+
+This lets you keep the configuration for your development server, build, test, lint, format, task runner, and staged-file workflow in one place with type-safe config and shared defaults.
+
+Use `vp migrate` to migrate to Vite+. It merges tool-specific config files such as `.oxlintrc*`, `.oxfmtrc*`, and lint-staged config into `vite.config.ts`.
+
+### CLI Workflows (`vp help`)
+
+#### Start
+
+- **create** - Create a new project from a template
+- **migrate** - Migrate an existing project to Vite+
+- **config** - Configure hooks and agent integration
+- **staged** - Run linters on staged files
+- **install** (`i`) - Install dependencies
+- **env** - Manage Node.js versions
+
+#### Develop
+
+- **dev** - Run the development server
+- **check** - Run format, lint, and type checks
+- **lint** - Lint code
+- **fmt** - Format code
+- **test** - Run tests
+
+#### Execute
+
+- **run** - Run monorepo tasks
+- **exec** - Execute a command from local `node_modules/.bin`
+- **dlx** - Execute a package binary without installing it as a dependency
+- **cache** - Manage the task cache
+
+#### Build
+
+- **build** - Build for production
+- **pack** - Build libraries
+- **preview** - Preview production build
+
+#### Manage Dependencies
+
+Vite+ automatically wraps your package manager (pnpm, npm, or Yarn) based on `packageManager` and lockfiles:
+
+- **add** - Add packages to dependencies
+- **remove** (`rm`, `un`, `uninstall`) - Remove packages from dependencies
+- **update** (`up`) - Update packages to latest versions
+- **dedupe** - Deduplicate dependencies
+- **outdated** - Check outdated packages
+- **list** (`ls`) - List installed packages
+- **why** (`explain`) - Show why a package is installed
+- **info** (`view`, `show`) - View package metadata from the registry
+- **link** (`ln`) / **unlink** - Manage local package links
+- **pm** - Forward a command to the package manager
+
+#### Maintain
+
+- **upgrade** - Update `vp` itself to the latest version
+- **implode** - Remove `vp` and all related data
+
+### Scaffolding your first Vite+ project
+
+Use `vp create` to create a new project:
+
+```bash
+vp create
+```
+
+You can run `vp create` inside of a project to add new apps or libraries to your project.
+
+### Migrating an existing project
+
+You can migrate an existing project to Vite+:
+
+```bash
+vp migrate
+```
+
+### GitHub Actions
+
+Use the official [`setup-vp`](https://github.com/voidzero-dev/setup-vp) action to install Vite+ in GitHub Actions:
+
+```yaml
+- uses: voidzero-dev/setup-vp@v1
+  with:
+    node-version: '22'
+    cache: true
+```
+
+#### Manual Installation & Migration
+
+If you are manually migrating a project to Vite+, install these dev dependencies first:
+
+```bash
+npm install -D vite-plus @voidzero-dev/vite-plus-core@latest
+```
+
+You need to add overrides to your package manager for `vite` and `vitest` so that other packages depending on Vite and Vitest will use the Vite+ versions:
+
+```json
+"overrides": {
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
+  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+}
+```
+
+If you are using `pnpm`, add this to your `pnpm-workspace.yaml`:
+
+```yaml
+overrides:
+  vite: npm:@voidzero-dev/vite-plus-core@latest
+  vitest: npm:@voidzero-dev/vite-plus-test@latest
+```
+
+Or, if you are using Yarn:
+
+```json
+"resolutions": {
+  "vite": "npm:@voidzero-dev/vite-plus-core@latest",
+  "vitest": "npm:@voidzero-dev/vite-plus-test@latest"
+}
+```
+
+## Sponsors
+
+Thanks to [namespace.so](https://namespace.so) for powering our CI/CD pipelines with fast, free macOS and Linux runners.

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/build.md

@@ -0,0 +1,21 @@
+# Build Config
+
+`vp dev`, `vp build`, and `vp preview` use the standard [Vite configuration](https://vite.dev/config/), including [plugins](https://vite.dev/guide/using-plugins), [aliases](https://vite.dev/config/shared-options#resolve-alias), [`server`](https://vite.dev/config/server-options), [`build`](https://vite.dev/config/build-options) and [`preview`](https://vite.dev/config/preview-options) fields.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  server: {
+    port: 3000,
+  },
+  build: {
+    sourcemap: true,
+  },
+  preview: {
+    port: 4173,
+  },
+});
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/fmt.md

@@ -0,0 +1,18 @@
+# Format Config
+
+`vp fmt` and `vp check` read Oxfmt settings from the `fmt` block in `vite.config.ts`. See [Oxfmt's configuration](https://oxc.rs/docs/guide/usage/formatter/config.html) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  fmt: {
+    ignorePatterns: ['dist/**'],
+    singleQuote: true,
+    semi: true,
+    sortPackageJson: true,
+  },
+});
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/index.md

@@ -0,0 +1,31 @@
+# Configuring Vite+
+
+Vite+ keeps project configuration in one place: `vite.config.ts`, allowing you to consolidate many top-level configuration files in a single file. You can keep using your Vite configuration such as `server` or `build`, and add Vite+ blocks for the rest of your workflow:
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  server: {},
+  build: {},
+  preview: {},
+
+  test: {},
+  lint: {},
+  fmt: {},
+  run: {},
+  pack: {},
+  staged: {},
+});
+```
+
+## Vite+ Specific Configuration
+
+Vite+ extends the basic Vite configuration with these additions:
+
+- [`lint`](/config/lint) for Oxlint
+- [`fmt`](/config/fmt) for Oxfmt
+- [`test`](/config/test) for Vitest
+- [`run`](/config/run) for Vite Task
+- [`pack`](/config/pack) for tsdown
+- [`staged`](/config/staged) for staged-file checks

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/lint.md

@@ -0,0 +1,24 @@
+# Lint Config
+
+`vp lint` and `vp check` read Oxlint settings from the `lint` block in `vite.config.ts`. See [Oxlint's configuration](https://oxc.rs/docs/guide/usage/linter/config.html) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  lint: {
+    ignorePatterns: ['dist/**'],
+    options: {
+      typeAware: true,
+      typeCheck: true,
+    },
+    rules: {
+      'no-console': ['error', { allow: ['error'] }],
+    },
+  },
+});
+```
+
+We recommend enabling both `options.typeAware` and `options.typeCheck` so `vp lint` and `vp check` can use the full type-aware path.

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/pack.md

@@ -0,0 +1,17 @@
+# Pack Config
+
+`vp pack` reads tsdown settings from the `pack` block in `vite.config.ts`. See [tsdown's configuration](https://tsdown.dev/options/config-file) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  pack: {
+    dts: true,
+    format: ['esm', 'cjs'],
+    sourcemap: true,
+  },
+});
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/run.md

@@ -0,0 +1,249 @@
+# Run Config
+
+You can configure Vite Task under the `run` field in `vite.config.ts`. Check out [`vp run`](/guide/run) to learn more about running scripts and tasks with Vite+.
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  run: {
+    enablePrePostScripts: true,
+    cache: {
+      /* ... */
+    },
+    tasks: {
+      /* ... */
+    },
+  },
+});
+```
+
+## `run.enablePrePostScripts`
+
+- **Type:** `boolean`
+- **Default:** `true`
+
+Whether to automatically run `preX`/`postX` package.json scripts as lifecycle hooks when script `X` is executed.
+
+When enabled (the default), running a script like `test` will automatically run `pretest` before it and `posttest` after it, if they exist in `package.json`.
+
+```ts
+export default defineConfig({
+  run: {
+    enablePrePostScripts: false, // Disable pre/post lifecycle hooks
+  },
+});
+```
+
+::: warning
+This option can only be set in the workspace root's `vite.config.ts`. Setting it in a package's config will result in an error.
+:::
+
+## `run.cache`
+
+- **Type:** `boolean | { scripts?: boolean, tasks?: boolean }`
+- **Default:** `{ scripts: false, tasks: true }`
+
+Controls whether task results are cached and replayed on subsequent runs.
+
+```ts
+export default defineConfig({
+  run: {
+    cache: {
+      scripts: true, // Cache package.json scripts (default: false)
+      tasks: true, // Cache task definitions (default: true)
+    },
+  },
+});
+```
+
+`cache: true` enables both task and script caching, `cache: false` disables both.
+
+## `run.tasks`
+
+- **Type:** `Record<string, TaskConfig>`
+
+Defines tasks that can be run with `vp run <task>`.
+
+### `command`
+
+- **Type:** `string`
+
+Defines the shell command to run for the task.
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+  },
+}
+```
+
+Each task defined in `vite.config.ts` must include its own `command`. You cannot define a task in both `vite.config.ts` and `package.json` with the same task name.
+
+Commands joined with `&&` are automatically split into independently cached sub-tasks. See [Compound Commands](/guide/run#compound-commands).
+
+### `dependsOn`
+
+- **Type:** `string[]`
+- **Default:** `[]`
+
+Tasks that must complete successfully before this one starts.
+
+```ts
+tasks: {
+  deploy: {
+    command: 'deploy-script --prod',
+    dependsOn: ['build', 'test'],
+  },
+}
+```
+
+Dependencies can reference tasks in other packages using the `package#task` format:
+
+```ts
+dependsOn: ['@my/core#build', '@my/utils#lint'];
+```
+
+See [Task Dependencies](/guide/run#task-dependencies) for details on how explicit and topological dependencies interact.
+
+### `cache`
+
+- **Type:** `boolean`
+- **Default:** `true`
+
+Whether to cache this task's output. Set to `false` for tasks that should never be cached, like dev servers:
+
+```ts
+tasks: {
+  dev: {
+    command: 'vp dev',
+    cache: false,
+  },
+}
+```
+
+### `env`
+
+- **Type:** `string[]`
+- **Default:** `[]`
+
+Environment variables included in the cache fingerprint. When any listed variable's value changes, the cache is invalidated.
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+    env: ['NODE_ENV'],
+  },
+}
+```
+
+Wildcard patterns are supported: `VITE_*` matches all variables starting with `VITE_`.
+
+```bash
+$ NODE_ENV=development vp run build    # first run
+$ NODE_ENV=production vp run build     # cache miss: variable changed
+```
+
+### `untrackedEnv`
+
+- **Type:** `string[]`
+- **Default:** see below
+
+Environment variables passed to the task process but **not** included in the cache fingerprint. Changing these values won't invalidate the cache.
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+    untrackedEnv: ['CI', 'GITHUB_ACTIONS'],
+  },
+}
+```
+
+A set of common environment variables are automatically passed through to all tasks:
+
+- **System:** `HOME`, `USER`, `PATH`, `SHELL`, `LANG`, `TZ`
+- **Node.js:** `NODE_OPTIONS`, `COREPACK_HOME`, `PNPM_HOME`
+- **CI/CD:** `CI`, `VERCEL_*`, `NEXT_*`
+- **Terminal:** `TERM`, `COLORTERM`, `FORCE_COLOR`, `NO_COLOR`
+
+### `input`
+
+- **Type:** `Array<string | { auto: boolean } | { pattern: string, base: "workspace" | "package" }>`
+- **Default:** `[{ auto: true }]` (auto-inferred)
+
+Vite Task automatically detects which files are used by a command (see [Automatic File Tracking](/guide/cache#automatic-file-tracking)). The `input` option can be used to explicitly include or exclude certain files.
+
+**Exclude files** from automatic tracking:
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+    // Use `{ auto: true }` to use automatic fingerprinting (default).
+    input: [{ auto: true }, '!**/*.tsbuildinfo', '!dist/**'],
+  },
+}
+```
+
+**Specify explicit files** only without automatic tracking:
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+    input: ['src/**/*.ts', 'vite.config.ts'],
+  },
+}
+```
+
+**Resolve patterns relative to the workspace root** using the object form:
+
+```ts
+tasks: {
+  build: {
+    command: 'vp build',
+    input: [
+      { auto: true },
+      { pattern: 'shared-config/**', base: 'workspace' },
+    ],
+  },
+}
+```
+
+The `base` field is required and controls how the glob pattern is resolved:
+- `"package"`: relative to the package directory
+- `"workspace"`: relative to the workspace root
+
+**Disable file tracking** entirely and cache only on command/env changes:
+
+```ts
+tasks: {
+  greet: {
+    command: 'node greet.mjs',
+    input: [],
+  },
+}
+```
+
+::: tip
+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.
+:::
+
+### `cwd`
+
+- **Type:** `string`
+- **Default:** package root
+
+Working directory for the task, relative to the package root.
+
+```ts
+tasks: {
+  'test-e2e': {
+    command: 'vp test',
+    cwd: 'tests/e2e',
+  },
+}
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/staged.md

@@ -0,0 +1,15 @@
+# Staged Config
+
+`vp staged` and `vp config` read staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit hooks guide](/guide/commit-hooks).
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+  },
+});
+```

package/skills/void/docs/node_modules/void/node_modules/vite-plus/docs/config/test.md

@@ -0,0 +1,18 @@
+# Test Config
+
+`vp test` reads Vitest settings from the `test` block in `vite.config.ts`. See [Vitest's configuration](https://vitest.dev/config/) for details.
+
+## Example
+
+```ts
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  test: {
+    include: ['src/**/*.test.ts'],
+    coverage: {
+      reporter: ['text', 'html'],
+    },
+  },
+});
+```