void 0.10.13 → 0.20.1

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

@@ -1,134 +0,0 @@
-# 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.
-
-Building with an AI assistant? Copy a ready-made setup prompt:
-
-<CopyPrompt />
-
-## 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 exec`](/guide/vpx) runs local project binaries.
-- [`vp node`](/guide/env) runs Node.js scripts with the resolved Vite+ environment.
-- [`vp dlx`](/guide/vpx) downloads and runs package binaries without adding them as dependencies.
-- [`vp cache clean`](/guide/cache) clears task cache entries.
-- [`vpx`](/guide/vpx) downloads and runs binaries globally.
-
-### 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 list`](/guide/install), [`vp why`](/guide/install), and [`vp info`](/guide/install) wrap package-manager workflows.
-- [`vp link`](/guide/install), [`vp unlink`](/guide/install), and [`vp rebuild`](/guide/install) cover local package links and native module rebuilds.
-- [`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)
-:::

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

@@ -1,199 +0,0 @@
-# Installing Dependencies
-
-`vp install` installs dependencies using the current workspace's package manager.
-
-## Overview
-
-Use Vite+ to manage dependencies across pnpm, npm, Yarn, and Bun. Instead of switching between `pnpm install`, `npm install`, `yarn install`, and `bun install`, you can keep using `vp install`, `vp add`, `vp remove`, and the rest of the Vite+ package-management commands.
-
-Vite+ detects the package manager from the workspace root in this order:
-
-1. `packageManager` in `package.json`
-2. `devEngines.packageManager` in `package.json`
-3. `pnpm-workspace.yaml`
-4. `pnpm-lock.yaml`
-5. `yarn.lock` or `.yarnrc.yml`
-6. `package-lock.json`
-7. `bun.lock` or `bun.lockb`
-8. `.pnpmfile.cjs` or `pnpmfile.cjs`
-9. `bunfig.toml`
-10. `yarn.config.cjs`
-
-If none of those files are present, `vp` falls back to `pnpm` by default. Vite+ automatically downloads the matching package manager and uses it for the command you ran. When detection comes from lockfiles or config files, the resolved version is written to `devEngines.packageManager` so future runs are deterministic; projects that already declare `packageManager` or `devEngines.packageManager` are left as-is.
-
-The [`devEngines.packageManager`](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines) field accepts a single object or an array of objects, and its `version` may be a semver range:
-
-```json
-{
-  "devEngines": {
-    "packageManager": {
-      "name": "pnpm",
-      "version": "^11.0.0",
-      "onFail": "download"
-    }
-  }
-}
-```
-
-A range resolves to an already-downloaded satisfying version when possible, otherwise to the latest satisfying version from the npm registry. The range itself stays the source of truth; Vite+ never freezes it into an exact `packageManager` pin. When both `packageManager` and `devEngines.packageManager` are declared, the `packageManager` field drives selection and Vite+ warns when it does not satisfy the devEngines constraint (`vp env doctor` shows details).
-
-Vite+ currently downloads the declared package manager (the `onFail: "download"` behavior); the other `onFail` values are accepted but not yet differentiated.
-
-The explicit `packageManager` field (or the `devEngines.packageManager` declaration) also affects matching package-manager shims. If a project has `packageManager: "npm@10.9.4"`, `npm` and `npx` use npm 10.9.4. Other generated alias pairs behave the same way: `pnpm`/`pnpx`, `yarn`/`yarnpkg`, and `bun`/`bunx`. Mismatched tools are not translated; `npm` in a `pnpm` project still resolves as npm.
-
-## Usage
-
-```bash
-vp install
-```
-
-Common install flows:
-
-```bash
-vp install
-vp install --frozen-lockfile
-vp install --lockfile-only
-vp install --filter web
-vp install -w
-```
-
-`vp install` maps to the correct underlying install behavior for the detected package manager, including the right lockfile flags for pnpm, npm, Yarn, and Bun.
-
-## Global Packages
-
-Use the `-g` flag for installing, updating or removing globally installed packages:
-
-- `vp install -g <pkg>` installs a package globally
-- `vp uninstall -g <pkg>` removes a global package
-- `vp update -g [pkg]` updates one global package or all of them
-- `vp list -g [pkg]` lists global packages
-- `vp outdated -g [pkg]` prints outdated packages
-
-::: warning
-These commands do **NOT** interact with the underlying package manager's global installation directory.
-
-Instead, Vite+ manages its own global packages under `~/.vite-plus/packages`, allowing them to remain available across different Node.js versions.
-
-As a result, commands such as `vp link` do not affect Vite+'s global packages and will not appear in `vp list -g`.
-:::
-
-## Managing Dependencies
-
-Vite+ provides all the familiar package management commands:
-
-- `vp install` installs the current dependency graph for the project
-- `vp add <pkg>` adds packages to `dependencies`, use `-D` for `devDependencies`
-- `vp remove <pkg>` removes packages
-- `vp update` updates dependencies
-- `vp dedupe` reduces duplicate dependency entries where the package manager supports it
-- `vp outdated` shows available updates
-- `vp list` shows installed packages
-- `vp why <pkg>` explains why a package is present
-- `vp info <pkg>` shows registry metadata for a package
-- `vp rebuild` rebuilds native modules (e.g. after switching Node.js versions)
-- `vp link` and `vp unlink` manage local package links
-- `vp dlx <pkg>` runs a package binary without adding it to the project
-- `vp pm <command>` forwards a raw package-manager-specific command when you need behavior outside the normalized `vp` command set
-
-### Command Guide
-
-#### Install
-
-Use `vp install` when you want to install exactly what the current `package.json` and lockfile describe.
-
-- `vp install` is the standard install command
-- `vp install --frozen-lockfile` fails if the lockfile would need changes
-- `vp install --no-frozen-lockfile` allows lockfile updates explicitly
-- `vp install --lockfile-only` updates the lockfile without performing a full install
-- `vp install --prefer-offline` and `vp install --offline` prefer or require cached packages
-- `vp install --ignore-scripts` skips lifecycle scripts
-- `vp install --filter <pattern>` scopes install work in monorepos
-- `vp install -w` installs in the workspace root
-
-#### Global Install
-
-Use these commands when you want package-manager-managed tools available outside a single project.
-
-- `vp install -g typescript`
-- `vp uninstall -g typescript`
-- `vp update -g`
-- `vp list -g`
-- `vp outdated -g`
-
-#### Add and Remove
-
-Use `vp add` and `vp remove` for day-to-day dependency edits instead of editing `package.json` by hand.
-
-- `vp add react`
-- `vp add -D typescript vitest`
-- `vp add -O fsevents`
-- `vp add --save-peer react`
-- `vp remove react`
-- `vp remove --filter web react`
-
-#### Update, Dedupe, and Outdated
-
-Use these commands to maintain the dependency graph over time.
-
-- `vp update` refreshes packages to newer versions
-- `vp outdated` shows which packages have newer versions available
-- `vp dedupe` asks the package manager to collapse duplicates where possible
-
-#### Inspect
-
-Use these when you need to understand the current state of dependencies.
-
-- `vp list` shows installed packages
-- `vp why react` explains why `react` is installed
-- `vp info react` shows registry metadata such as versions and dist-tags
-
-#### Rebuild
-
-Use `vp rebuild` when native modules need to be recompiled, for example after switching Node.js versions or when a C/C++ addon fails to load.
-
-- `vp rebuild` rebuilds all native modules
-- `vp rebuild <package...>` rebuilds the listed packages only
-- `vp rebuild -- <args>` passes extra arguments to the underlying package manager
-
-```bash
-vp rebuild
-vp rebuild better-sqlite3 sharp
-vp rebuild -- --update-binary
-```
-
-`vp rebuild` is a shorthand for `vp pm rebuild`.
-
-With pnpm v10+, bare `vp rebuild` only rebuilds packages whose build scripts are listed in `onlyBuiltDependencies` (or approved via `pnpm approve-builds`); name the package explicitly to force a rebuild that bypasses the approval gate.
-
-#### Advanced
-
-Use these when you need lower-level package-manager behavior.
-
-- `vp link` and `vp unlink` manage local development links
-- `vp dlx create-vite` runs a package binary without saving it as a dependency
-- `vp pm <command>` forwards directly to the resolved package manager
-
-Examples:
-
-```bash
-vp pm config get registry
-vp pm cache clean -- --force
-vp pm audit --json
-```
-
-#### Staged publishing
-
-`vp pm stage` exposes [npm's staged publishing](https://docs.npmjs.com/staged-publishing) workflow: a build is uploaded to a staging area (no 2FA, CI-friendly), then a maintainer approves or rejects it from a trusted device (2FA). It adapts to the detected package manager.
-
-```bash
-vp pm stage publish              # upload the package to staging (no 2FA)
-vp pm stage list                 # list staged versions
-vp pm stage view <stage-id>      # inspect a staged version
-vp pm stage download <stage-id>  # download the staged tarball
-vp pm stage approve <stage-id>   # promote to the live registry (2FA)
-vp pm stage reject <stage-id>    # discard a staged version (2FA)
-```
-
-- pnpm (`pnpm stage`, requires pnpm ≥ 11.3) and npm (`npm stage`, requires npm ≥ 11.15 and Node ≥ 22.14) pass through directly.
-- yarn (Berry) uses its npm plugin (`yarn npm publish --staged`, `yarn npm stage …`); `view`/`download` fall back to npm.
-- yarn Classic and bun have no staged-publishing support and fall back to `npm stage`.

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

@@ -1,50 +0,0 @@
-# Lint
-
-`vp lint` lints code with Oxlint.
-
-## Overview
-
-`vp lint` is built on [Oxlint](https://oxc.rs/docs/guide/usage/linter.html), the Oxc linter. Oxlint is designed as a fast replacement for ESLint for most frontend projects and ships with built-in support for core ESLint rules and many popular community rules.
-
-Use `vp lint` to lint your project, and `vp check` to format, lint and type-check all at once.
-
-## Usage
-
-```bash
-vp lint
-vp lint --fix
-vp lint --type-aware
-```
-
-## Configuration
-
-Put lint configuration directly in the `lint` block in `vite.config.ts` so all your configuration stays in one place. We do not recommend using `oxlint.config.ts` or `.oxlintrc.json` with Vite+.
-
-For the upstream rule set, options, and compatibility details, see the [Oxlint docs](https://oxc.rs/docs/guide/usage/linter.html).
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  lint: {
-    ignorePatterns: ['dist/**'],
-    options: {
-      typeAware: true,
-      typeCheck: true,
-    },
-  },
-});
-```
-
-## Type-Aware Linting
-
-We recommend enabling both `typeAware` and `typeCheck` in the `lint` block:
-
-- `typeAware: true` enables rules that require TypeScript type information
-- `typeCheck: true` enables full type checking during linting
-
-This path is powered by [tsgolint](https://github.com/oxc-project/tsgolint) on top of the TypeScript Go toolchain. It gives Oxlint access to type information and allows type checking directly via `vp lint` and `vp check`.
-
-## JS Plugins
-
-If you are migrating from ESLint and still depend on a few critical JavaScript-based ESLint plugins, Oxlint has [JS plugin support](https://oxc.rs/docs/guide/usage/linter/js-plugins) that can help you keep those plugins running while you complete the migration.