void 0.7.1 → 0.7.3

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/commit-hooks.md

@@ -0,0 +1,51 @@
+# Commit Hooks
+
+Use `vp config` to install commit hooks, and `vp staged` to run checks on staged files.
+
+## Overview
+
+Vite+ supports commit hooks and staged-file checks without additional tooling.
+
+Use:
+
+- `vp config` to set up project hooks and related integrations
+- `vp staged` to run checks against the files currently staged in Git
+
+If you use [`vp create`](/guide/create) or [`vp migrate`](/guide/migrate), Vite+ prompts you to set this up for your project automatically.
+
+## Commands
+
+### `vp config`
+
+`vp config` configures Vite+ for the current project. It installs Git hooks, sets up the hook directory, and can also handle related project integration such as agent setup. By default, hooks are written to `.vite-hooks`:
+
+```bash
+vp config
+vp config --hooks-dir .vite-hooks
+```
+
+### `vp staged`
+
+`vp staged` runs staged-file checks using the `staged` config from `vite.config.ts`. If you set up Vite+ to handle your commit hooks, it will automatically run when you commit your local changes.
+
+```bash
+vp staged
+vp staged --verbose
+vp staged --fail-on-changes
+```
+
+## Configuration
+
+Define staged-file checks in the `staged` block in `vite.config.ts`:
+
+```ts [vite.config.ts]
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  staged: {
+    '*.{js,ts,tsx,vue,svelte}': 'vp check --fix',
+  },
+});
+```
+
+This is the default Vite+ approach and should replace separate `lint-staged` configuration in most projects. Because `vp staged` reads from `vite.config.ts`, your staged-file checks stay in the same place as your lint, format, test, build, and task-runner config.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/create.md

@@ -0,0 +1,88 @@
+# Creating a Project
+
+`vp create` interactively scaffolds new Vite+ projects, monorepos, and apps inside existing workspaces.
+
+## Overview
+
+The `create` command is the fastest way to start with Vite+. It can be used in a few different ways:
+
+- Start a new Vite+ monorepo
+- Create a new standalone application or library
+- Add a new app or library inside an existing project
+
+This command can be used with built-in templates, community templates, or remote GitHub templates.
+
+## Usage
+
+```bash
+vp create
+vp create <template>
+vp create <template> -- <template-options>
+```
+
+## Built-in Templates
+
+Vite+ ships with these built-in templates:
+
+- `vite:monorepo` creates a new monorepo
+- `vite:application` creates a new application
+- `vite:library` creates a new library
+- `vite:generator` creates a new generator
+
+## Template Sources
+
+`vp create` is not limited to the built-in templates.
+
+- Use shorthand templates like `vite`, `@tanstack/start`, `svelte`, `next-app`, `nuxt`, `react-router`, and `vue`
+- Use full package names like `create-vite` or `create-next-app`
+- Use local templates such as `./tools/create-ui-component` or `@acme/generator-*`
+- Use remote templates such as `github:user/repo` or `https://github.com/user/template-repo`
+
+Run `vp create --list` to see the built-in templates and the common shorthand templates Vite+ recognizes.
+
+## Options
+
+- `--directory <dir>` writes the generated project into a specific target directory
+- `--agent <name>` creates agent instructions files during scaffolding
+- `--editor <name>` writes editor config files
+- `--hooks` enables pre-commit hook setup
+- `--no-hooks` skips hook setup
+- `--no-interactive` runs without prompts
+- `--verbose` shows detailed scaffolding output
+- `--list` prints the available built-in and popular templates
+
+## Template Options
+
+Arguments after `--` are passed directly to the selected template.
+
+This matters when the template itself accepts flags. For example, you can forward Vite template selection like this:
+
+```bash
+vp create vite -- --template react-ts
+```
+
+## Examples
+
+```bash
+# Interactive mode
+vp create
+
+# Create a Vite+ monorepo, application, library, or generator
+vp create vite:monorepo
+vp create vite:application
+vp create vite:library
+vp create vite:generator
+
+# Use shorthand community templates
+vp create vite
+vp create @tanstack/start
+vp create svelte
+
+# Use full package names
+vp create create-vite
+vp create create-next-app
+
+# Use remote templates
+vp create github:user/repo
+vp create https://github.com/user/template-repo
+```

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/dev.md

@@ -0,0 +1,24 @@
+# Dev
+
+`vp dev` starts the Vite development server.
+
+## Overview
+
+`vp dev` runs the standard Vite development server through Vite+, so you keep the normal Vite dev experience while using the same CLI entry point as the rest of the toolchain. For more information about using and configuring the dev server, see the [Vite guide](https://vite.dev/guide/).
+
+## Usage
+
+```bash
+vp dev
+```
+
+## Configuration
+
+Use standard Vite config in `vite.config.ts`. For the full configuration reference, see the [Vite config docs](https://vite.dev/config/).
+
+Use it for:
+
+- [plugins](https://vite.dev/guide/using-plugins)
+- [aliases](https://vite.dev/config/shared-options#resolve-alias)
+- [`server`](https://vite.dev/config/server-options)
+- [environment modes](https://vite.dev/guide/env-and-mode)

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/env.md

@@ -0,0 +1,102 @@
+# Environment
+
+`vp env` manages Node.js versions globally and per project.
+
+## Overview
+
+Managed mode is on by default, so `node`, `npm`, and related shims resolve through Vite+ and pick the right Node.js version for the current project.
+
+By default, Vite+ stores its managed runtime and related files in `~/.vite-plus`. If needed, you can override that location with `VP_HOME`.
+
+If you want to keep that behavior, run:
+
+```bash
+vp env on
+```
+
+This enables managed mode, where the shims always use the Vite+-managed Node.js installation.
+
+If you do not want Vite+ to manage Node.js first, run:
+
+```bash
+vp env off
+```
+
+This switches to system-first mode, where the shims prefer your system Node.js and only fall back to the Vite+-managed runtime when needed.
+
+## Commands
+
+### Setup
+
+- `vp env setup` creates or updates shims in `VP_HOME/bin`
+- `vp env on` enables managed mode so shims always use Vite+-managed Node.js
+- `vp env off` enables system-first mode so shims prefer system Node.js first
+- `vp env print` prints the shell snippet for the current session
+
+### Manage
+
+- `vp env default` sets or shows the global default Node.js version
+- `vp env pin` pins a Node.js version in the current directory
+- `vp env unpin` removes `.node-version` from the current directory
+- `vp env use` sets a Node.js version for the current shell session
+- `vp env install` installs a Node.js version
+- `vp env uninstall` removes an installed Node.js version
+- `vp env exec` runs a command with a specific Node.js version
+- `vp node` runs a Node.js script — shorthand for `vp env exec node`
+
+### Inspect
+
+- `vp env current` shows the current resolved environment
+- `vp env doctor` runs environment diagnostics
+- `vp env which` shows which tool path will be used
+- `vp env list` shows locally installed Node.js versions
+- `vp env list-remote` shows available Node.js versions from the registry
+
+## Project Setup
+
+- Pin a project version with `.node-version`
+- Use `vp install`, `vp dev`, and `vp build` normally
+- Let Vite+ pick the right runtime for the project
+
+## Examples
+
+```bash
+# Setup
+vp env setup                  # Create shims for node, npm, npx
+vp env on                     # Use Vite+ managed Node.js
+vp env print                  # Print shell snippet for this session
+
+# Manage
+vp env pin lts                # Pin the project to the latest LTS release
+vp env install                # Install the version from .node-version or package.json
+vp env default lts            # Set the global default version
+vp env use 20                 # Use Node.js 20 for the current shell session
+vp env use --unset            # Remove the session override
+
+# Inspect
+vp env current                # Show current resolved environment
+vp env current --json         # JSON output for automation
+vp env which node             # Show which node binary will be used
+vp env list-remote --lts      # List only LTS versions
+
+# Execute
+vp env exec --node lts npm i  # Execute npm with latest LTS
+vp env exec node -v           # Use shim mode with automatic version resolution
+vp node script.js             # Shorthand: run a Node.js script with the resolved version
+vp node -e "console.log(1+1)" # Shorthand: forward any node flag or argument
+```
+
+## Custom Node.js Mirror
+
+By default, Vite+ downloads Node.js from `https://nodejs.org/dist`. If you're behind a corporate proxy or need to use an internal mirror (e.g., Artifactory), set the `VP_NODE_DIST_MIRROR` environment variable:
+
+```bash
+# Install a specific version from your custom mirror
+VP_NODE_DIST_MIRROR=https://my-mirror.example.com/nodejs/dist vp env install 22
+
+# Set the global default version using a custom mirror
+VP_NODE_DIST_MIRROR=https://my-mirror.example.com/nodejs/dist vp env default lts
+
+# Set it permanently in your shell profile (.bashrc, .zshrc, etc.)
+echo 'export VP_NODE_DIST_MIRROR=https://my-mirror.example.com/nodejs/dist' >> ~/.zshrc
+```

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

@@ -0,0 +1,41 @@
+# Format
+
+`vp fmt` formats code with Oxfmt.
+
+## Overview
+
+`vp fmt` is built on [Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html), the Oxc formatter. Oxfmt has full Prettier compatibility and is designed as a fast drop-in replacement for Prettier.
+
+Use `vp fmt` to format your project, and `vp check` to format, lint and type-check all at once.
+
+## Usage
+
+```bash
+vp fmt
+vp fmt --check
+vp fmt . --write
+```
+
+## Configuration
+
+Put formatting configuration directly in the `fmt` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `.oxfmtrc.json` with Vite+.
+
+For editors, point the formatter config path at `./vite.config.ts` so format-on-save uses the same `fmt` block:
+
+```json [.vscode/settings.json]
+{
+  "oxc.fmt.configPath": "./vite.config.ts"
+}
+```
+
+For the upstream formatter behavior and configuration reference, see the [Oxfmt docs](https://oxc.rs/docs/guide/usage/formatter.html).
+
+```ts [vite.config.ts]
+import { defineConfig } from 'vite-plus';
+
+export default defineConfig({
+  fmt: {
+    singleQuote: true,
+  },
+});
+```

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/ide-integration.md

@@ -0,0 +1,101 @@
+# IDE Integration
+
+Vite+ supports VS Code and Zed through editor-specific settings that `vp create` and `vp migrate` can automatically write into your project.
+
+## VS Code
+
+For the best VS Code experience with Vite+, install the [Vite Plus Extension Pack](https://marketplace.visualstudio.com/items?itemName=VoidZero.vite-plus-extension-pack). It currently includes:
+
+- `Oxc` for formatting and linting via `vp check`
+- `Vitest` for test runs via `vp test`
+
+When you create or migrate a project, Vite+ prompts whether you want editor config written for VS Code. `vp create` additionally sets `npm.scriptRunner` to `vp` so the VS Code NPM Scripts panel runs scripts through the Vite+ task runner. For migrated or existing projects, you can add this setting manually (see below).
+
+You can also manually set up the VS Code config:
+
+```json [.vscode/extensions.json]
+{
+  "recommendations": ["VoidZero.vite-plus-extension-pack"]
+}
+```
+
+```json [.vscode/settings.json]
+{
+  "editor.defaultFormatter": "oxc.oxc-vscode",
+  "[javascript]": { "editor.defaultFormatter": "oxc.oxc-vscode" },
+  "[javascriptreact]": { "editor.defaultFormatter": "oxc.oxc-vscode" },
+  "[typescript]": { "editor.defaultFormatter": "oxc.oxc-vscode" },
+  "[typescriptreact]": { "editor.defaultFormatter": "oxc.oxc-vscode" },
+  "oxc.fmt.configPath": "./vite.config.ts",
+  "editor.formatOnSave": true,
+  "editor.formatOnSaveMode": "file",
+  "editor.codeActionsOnSave": {
+    "source.fixAll.oxc": "explicit"
+  }
+}
+```
+
+This gives the project a shared default formatter and enables Oxc-powered fix actions on save. The language-specific override blocks (`[javascript]`, `[typescript]`, etc.) are required because VS Code prioritizes user-level `[language]` settings over the workspace-level `editor.defaultFormatter` — without them, a global Prettier configuration would silently take over. Setting `oxc.fmt.configPath` to `./vite.config.ts` keeps editor format-on-save aligned with the `fmt` block in your Vite+ config. Vite+ uses `formatOnSaveMode: "file"` because Oxfmt does not support partial formatting.
+
+To let the VS Code NPM Scripts panel run scripts through `vp`, add the following to your `.vscode/settings.json`:
+
+```json [.vscode/settings.json]
+{
+  "npm.scriptRunner": "vp"
+}
+```
+
+This is included automatically by `vp create` but not by `vp migrate`, since existing projects may have team members who do not have `vp` installed locally.
+
+## Zed
+
+For the best Zed experience with Vite+, install the [oxc-zed](https://github.com/oxc-project/oxc-zed) extension from the Zed extensions marketplace. It provides formatting and linting via `vp check`.
+
+When you create or migrate a project, Vite+ prompts you to choose whether you want the editor config written for Zed.
+
+You can also manually set up the Zed config:
+
+```json [.zed/settings.json]
+{
+  "lsp": {
+    "oxlint": {
+      "initialization_options": {
+        "settings": {
+          "run": "onType",
+          "fixKind": "safe_fix",
+          "typeAware": true,
+          "unusedDisableDirectives": "deny"
+        }
+      }
+    },
+    "oxfmt": {
+      "initialization_options": {
+        "settings": {
+          "configPath": "./vite.config.ts",
+          "run": "onSave"
+        }
+      }
+    }
+  },
+  "languages": {
+    "JavaScript": {
+      "format_on_save": "on",
+      "prettier": { "allowed": false },
+      "formatter": [{ "language_server": { "name": "oxfmt" } }],
+      "code_action": "source.fixAll.oxc"
+    },
+    "TypeScript": {
+      "format_on_save": "on",
+      "prettier": { "allowed": false },
+      "formatter": [{ "language_server": { "name": "oxfmt" } }]
+    },
+    "Vue.js": {
+      "format_on_save": "on",
+      "prettier": { "allowed": false },
+      "formatter": [{ "language_server": { "name": "oxfmt" } }]
+    }
+  }
+}
+```
+
+Setting `oxfmt.configPath` to `./vite.config.ts` keeps editor format-on-save aligned with the `fmt` block in your Vite+ config. The full generated config covers additional languages (CSS, HTML, JSON, Markdown, etc.) — run `vp create` or `vp migrate` to get the complete file written automatically.

package/skills/void/docs/node_modules/void/node_modules/@void/md/node_modules/vite-plus/docs/guide/implode.md

@@ -0,0 +1,23 @@
+# Removing Vite+
+
+Use `vp implode` to remove `vp` and all related Vite+ data from your machine.
+
+## Overview
+
+`vp implode` is the cleanup command for removing a Vite+ installation and its managed data. Use it if you no longer want Vite+ to manage your runtime, package manager, and related local tooling state.
+
+::: info
+If you decide Vite+ is not for you, please [share your feedback with us](https://discord.gg/cAnsqHh5PX).
+:::
+
+## Usage
+
+```bash
+vp implode
+```
+
+Skip the confirmation prompt with:
+
+```bash
+vp implode --yes
+```

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

@@ -0,0 +1,128 @@
+# Getting Started
+
+Vite+ is the unified toolchain and entry point for web development. It manages your runtime, package manager, and frontend toolchain in one place by combining [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).
+
+Vite+ ships in two parts: `vp`, the global command-line tool, and `vite-plus`, the local package installed in each project. If you already have a Vite project, use [`vp migrate`](/guide/migrate) to migrate it to Vite+, or paste our [migration prompt](/guide/migrate#migration-prompt) into your coding agent.
+
+## Install `vp`
+
+### macOS / Linux
+
+```bash
+curl -fsSL https://vite.plus | bash
+```
+
+### Windows
+
+```powershell
+irm https://vite.plus/ps1 | iex
+```
+
+Alternatively, download and run [`vp-setup.exe`](https://setup.viteplus.dev).
+
+::: tip SmartScreen warning
+The `vp-setup.exe` is not yet code-signed. Your browser may show a warning when downloading. Click **"..."** → **"Keep"** → **"Keep anyway"** to proceed. If Windows Defender SmartScreen blocks the file when you run it, click **"More info"** → **"Run anyway"**.
+:::
+
+After installation, open a new shell and run:
+
+```bash
+vp help
+```
+
+::: info
+Vite+ will manage your global Node.js runtime and package manager. If you'd like to opt out of this behavior, run `vp env off`. If you realize Vite+ is not for you, type `vp implode`, but please [share your feedback with us](https://discord.gg/cAnsqHh5PX).
+:::
+
+::: details Using a minor platform (CPU architecture, OS) ?
+
+Prebuilt binaries are distributed for the following platforms (grouped by [Node.js v24 platform support tier](https://github.com/nodejs/node/blob/v24.x/BUILDING.md#platform-list)):
+
+- Tier 1
+  - Linux x64 glibc (`x86_64-unknown-linux-gnu`)
+  - Linux arm64 glibc (`aarch64-unknown-linux-gnu`)
+  - Windows x64 (`x86_64-pc-windows-msvc`)
+  - macOS x64 (`x86_64-apple-darwin`)
+  - macOS arm64 (`aarch64-apple-darwin`)
+- Tier 2
+  - Windows arm64 (`aarch64-pc-windows-msvc`)
+- Experimental
+  - Linux x64 musl (`x86_64-unknown-linux-musl`)
+- Other
+  - Linux arm64 musl (`aarch64-unknown-linux-musl`)
+
+If a prebuilt binary is not available for your platform, installation will fail with an error.
+
+On Alpine Linux (musl), you need to install `libstdc++` before using Vite+:
+
+```sh
+apk add libstdc++
+```
+
+This is required because the managed [unofficial-builds](https://unofficial-builds.nodejs.org/) Node.js runtime depends on the GNU C++ standard library.
+
+:::
+
+## Quick Start
+
+Create a project, install dependencies, and use the default commands:
+
+```bash
+vp create # Create a new project
+vp install # Install dependencies
+vp dev # Start the dev server
+vp check # Format, lint, type-check
+vp test # Run JavaScript tests
+vp build # Build for production
+```
+
+You can also just run `vp` on its own and use the interactive command line.
+
+## Core Commands
+
+Vite+ can handle the entire local frontend development cycle from starting a project, developing it, checking & testing, and building it for production.
+
+### Start
+
+- [`vp create`](/guide/create) creates new apps, packages, and monorepos.
+- [`vp migrate`](/guide/migrate) moves existing projects onto Vite+.
+- [`vp config`](/guide/commit-hooks) configures commit hooks and agent integration.
+- [`vp staged`](/guide/commit-hooks) runs checks on staged files.
+- [`vp install`](/guide/install) installs dependencies with the right package manager.
+- [`vp env`](/guide/env) manages Node.js versions.
+
+### Develop
+
+- [`vp dev`](/guide/dev) starts the dev server powered by Vite.
+- [`vp check`](/guide/check) runs format, lint, and type checks together.
+- [`vp lint`](/guide/lint), [`vp fmt`](/guide/fmt), and [`vp test`](/guide/test) let you run those tools directly.
+
+### Execute
+
+- [`vp run`](/guide/run) runs tasks across workspaces with caching.
+- [`vp cache clean`](/guide/cache) clears task cache entries.
+- [`vpx`](/guide/vpx) downloads and runs binaries globally.
+- [`vp exec`](/guide/vpx) runs local project binaries.
+- [`vp dlx`](/guide/vpx) downloads and runs package binaries without adding them as dependencies.
+
+### Build
+
+- [`vp build`](/guide/build) builds apps.
+- [`vp pack`](/guide/pack) builds libraries or standalone artifacts.
+- [`vp preview`](/guide/build) previews the production build locally.
+
+### Manage Dependencies
+
+- [`vp add`](/guide/install), [`vp remove`](/guide/install), [`vp update`](/guide/install), [`vp dedupe`](/guide/install), [`vp outdated`](/guide/install), [`vp why`](/guide/install), and [`vp info`](/guide/install) wrap package-manager workflows.
+- [`vp pm <command>`](/guide/install) calls other package manager commands directly.
+
+### Maintain
+
+- [`vp upgrade`](/guide/upgrade) updates the `vp` installation itself.
+- [`vp implode`](/guide/implode) removes `vp` and related Vite+ data from your machine.
+
+::: info
+Vite+ ships with many predefined commands such as `vp build`, `vp test`, and `vp dev`. These commands are built-in and cannot be changed. If you want to run a command from your `package.json` scripts, use `vp run <command>` or `vpr <command>`.
+
+[Learn more about `vp run`.](/guide/run)
+:::