void 0.10.12 → 0.20.0

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

@@ -1,108 +0,0 @@
-# Troubleshooting
-
-Use this page when something in Vite+ is not behaving the way you expect.
-
-::: warning
-Vite+ is still in alpha. We are making frequent changes, adding features quickly, and we want feedback to help make it great.
-:::
-
-## Supported Tool Versions
-
-Vite+ expects modern upstream tool versions.
-
-- Vite 8 or newer
-- Vitest 4.1 or newer
-
-If you are migrating an existing project and it still depends on older Vite or Vitest versions, upgrade those first before adopting Vite+.
-
-## `vp check` does not run type-aware lint rules or type checks
-
-- Confirm that `lint.options.typeAware` and `lint.options.typeCheck` are enabled in `vite.config.ts`
-- Check whether your `tsconfig.json` still uses `compilerOptions.baseUrl`
-
-The Oxlint type checker path powered by `tsgolint` does not support `baseUrl`.
-`vp migrate` and `vp lint --init` try to run the `vp dlx @andrewbranch/ts5to6 --fixBaseUrl .`
-fix before enabling type-aware linting. If that fix fails or is declined, Vite+
-skips `typeAware` and `typeCheck`.
-
-## VS Code extension does not read `vite.config.ts`
-
-If VS Code has multiple folders open, the shared Oxc language server may pick a different workspace than expected. That can make it look like `vite.config.ts` support is missing.
-
-- Confirm the extension is using the intended workspace.
-
-## `vp build` does not run my build script
-
-Unlike package managers, built-in commands cannot be overwritten. If you are trying to run a `package.json` script use `vp run build` instead.
-
-For example:
-
-- `vp build` always runs the built-in Vite build
-- `vp test` always runs the built-in Vitest command
-- `vp run build` and `vp run test` run `package.json` scripts instead
-
-::: info
-You can also run custom tasks defined in `vite.config.ts` and migrate away from `package.json` scripts entirely.
-:::
-
-## Staged Checks and Commit Hooks
-
-If `vp staged` fails or your pre-commit hook does not run:
-
-- make sure `vite.config.ts` contains a `staged` block
-- run `vp config` to install hooks
-- check whether hook installation was skipped intentionally through `VITE_GIT_HOOKS=0`
-
-A minimal staged config looks like this:
-
-```ts [vite.config.ts]
-import { defineConfig } from 'vite-plus';
-
-export default defineConfig({
-  staged: {
-    '*': 'vp check --fix',
-  },
-});
-```
-
-## Slow config loading caused by heavy plugins
-
-When `vite.config.ts` imports plugins at the top level, they are evaluated for every command, including `vp lint`, `vp fmt`, editor integrations, and long-lived background processes. This can make config loading slow and may trigger plugin setup side effects, such as reading files, starting watchers, or connecting to services.
-
-Use `lazyPlugins` to skip the plugin factory when vite-plus loads your config only to read a metadata block (`lint`, `fmt`, `check`, `staged`, `pack`, `create`, the `run`/`cache` task lookup, and editor tooling). The plugins still load whenever Vite actually runs, `dev`, `build`, `test`, `preview`, and any build your own scripts spawn (a `vp run` task, `vp exec`):
-
-```ts [vite.config.ts]
-import { defineConfig, lazyPlugins } from 'vite-plus';
-import myPlugin from 'vite-plugin-foo';
-
-export default defineConfig({
-  plugins: lazyPlugins(() => [myPlugin()]),
-});
-```
-
-For heavy plugins that should be lazily imported, combine with dynamic `import()`:
-
-```ts [vite.config.ts]
-import { defineConfig, lazyPlugins } from 'vite-plus';
-
-export default defineConfig({
-  plugins: lazyPlugins(async () => {
-    const { default: heavyPlugin } = await import('vite-plugin-heavy');
-    return [heavyPlugin()];
-  }),
-});
-```
-
-## Asking for Help
-
-If you are stuck, please reach out:
-
-- [Discord](https://discord.gg/cAnsqHh5PX) for real-time discussion and troubleshooting help
-- [GitHub](https://github.com/voidzero-dev/vite-plus) for issues, discussions, and bug reports
-
-When reporting a problem, please include:
-
-- The full output of `vp env current` and `vp --version`
-- The package manager used by the project
-- The exact steps needed to reproduce the problem and your `vite.config.ts`
-- A minimal reproduction repository or runnable sandbox

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

@@ -1,101 +0,0 @@
-# Upgrading Vite+
-
-Use `vp upgrade` to update the global `vp` binary, and use Vite+'s package management commands to update the local `vite-plus` package in a project.
-
-## Overview
-
-There are two parts to upgrading Vite+:
-
-- The global `vp` command installed on your machine
-- The local `vite-plus` package used by an individual project
-
-You can upgrade both of them independently.
-
-## Global `vp`
-
-```bash
-vp upgrade                        # upgrade to the latest version
-vp upgrade --check                # check for updates without installing
-vp upgrade <version>              # install a specific version
-vp upgrade --registry <registry>  # use a custom npm registry
-```
-
-### Rollback
-
-Vite+ keeps the **3 most recent** versions installed so you can revert quickly:
-
-```bash
-vp upgrade --rollback
-```
-
-Older versions are pruned automatically after each upgrade. The active version and the previous version are always kept, so a rollback target is never removed.
-
-## Local `vite-plus`
-
-The recommended way to upgrade an existing Vite+ project is `vp migrate`:
-
-```bash
-vp migrate
-```
-
-On a project that is already on Vite+, migrate does a toolchain version upgrade only: it re-pins `vite-plus`, the `vite` -> `@voidzero-dev/vite-plus-core` alias, and the `vitest` pin to the versions the global `vp` now bundles, across every workspace package. It skips the first-time setup steps (git hooks, editor and agent files, lint migration), so a version bump does not re-touch things you already configured. Pass `--full` to also run that setup.
-
-### Updating the Vitest Pin
-
-If you migrated with `vp migrate`, your project pins `vitest` to an exact version so the whole project shares a single Vitest copy with the bundled `vp test` runner. The pin lives in your package manager's override block:
-
-- **npm / Bun:** a `vitest` entry under `overrides` in `package.json`
-- **Yarn:** a `vitest` entry under `resolutions` in `package.json`
-- **pnpm:** a `vitest` entry under `overrides` in `pnpm-workspace.yaml` — unless your `package.json` already had a `pnpm` field, in which case it lives under `pnpm.overrides` in `package.json` instead (pnpm ignores `pnpm-workspace.yaml` overrides when `package.json` defines `pnpm.overrides`)
-
-A Vite+ release can bump the bundled Vitest. Because that pin also applies to `vite-plus`'s own `vitest` dependency, an out-of-date pin keeps installing the previous runner even after you upgrade `vite-plus` — splitting Vitest's internals (mocks, `expect`, runner state) between the pinned copy and the one `vp test` loads.
-
-After upgrading `vite-plus`, re-pin `vitest` to the version Vite+ now bundles. Check that version with:
-
-```bash
-vp --version
-```
-
-Then set the `vitest` override to that exact version, or rerun `vp migrate` to update the pin for you.
-
-## Preview Builds
-
-Some Vite+ pull requests publish temporary packages for testing before an npm release. Treat these as nightly or bleeding-edge builds: they are useful when you want to verify a specific fix, test a fresh upstream dependency bump, or confirm a change before the next release. For day-to-day work, prefer the published `latest` release.
-
-Each commit on an eligible pull request is published to [pkg.pr.new](https://pkg.pr.new) and registered with the [registry bridge](https://registry-bridge.viteplus.dev/). The bridge serves these builds as ordinary npm versions of the form `0.0.0-commit.<sha>` and proxies every other package to the npm registry. That means you install a preview with normal version specs instead of mutable URLs, and the same versions resolve in CI.
-
-Both `vite-plus` and `@voidzero-dev/vite-plus-core` publish under the same `0.0.0-commit.<sha>` version. Each pull request carries a comment listing the exact version for its latest commit, along with ready-to-copy install steps.
-
-You can find preview builds in pull requests that automatically update upstream dependencies. For examples, search the merged pull requests for [upstream dependency updates](https://github.com/voidzero-dev/vite-plus/pulls?q=is%3Apr+is%3Amerged+upgrade+upstream+dependencies).
-
-Preview builds are addressed by pull request number or commit SHA. They are not a stable version range, and you should avoid leaving them in long-lived branches unless a maintainer asks you to.
-
-### Global `vp` Preview
-
-Install a preview build of the global CLI by passing `VP_PR_VERSION` to the installer. Pass a pull request number or a commit SHA:
-
-```bash
-curl -fsSL https://vite.plus | VP_PR_VERSION=<pr-or-sha> bash
-```
-
-On Windows:
-
-```powershell
-$env:VP_PR_VERSION = "<pr-or-sha>"
-irm https://vite.plus/ps1 | iex
-Remove-Item Env:\VP_PR_VERSION
-```
-
-The installer resolves the ref to its `0.0.0-commit.<sha>` build through the registry bridge and installs it like any other version. Run `vp --version` afterward to confirm which build and bundled tool versions are active. When you are done testing, return to the published release with `vp upgrade --force` or by running the installer again without `VP_PR_VERSION`.
-
-### Local `vite-plus` Preview
-
-After installing the preview global CLI above, run migrate in the project to move its local `vite-plus` onto the same build:
-
-```bash
-vp migrate
-```
-
-Migrate points the project at the bridge registry (writing it to `.npmrc`, or `.yarnrc.yml` for Yarn Berry) and pins `vite-plus` and the `vite` -> `@voidzero-dev/vite-plus-core` alias to the matching `0.0.0-commit.<sha>` version. That registry line is what lets the same versions resolve in the project's own CI, so commit it if you want CI to test the preview too.
-
-After installing, check the bundled versions with `vp --version`. When testing is complete, restore the published release: set `vite-plus` back to `latest`, remove the bridge `registry` line from `.npmrc` (or `.yarnrc.yml`), and reinstall with `vp install`.

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

@@ -1,66 +0,0 @@
-# Running Binaries
-
-Use `vpx`, `vp exec`, and `vp dlx` to run binaries without switching between local installs, downloaded packages, and project-specific tools.
-
-## Overview
-
-`vpx` executes a command from a local or remote npm package. It can run a package that is already available locally, download a package on demand, or target an explicit package version.
-
-Use the other binary commands when you need stricter control:
-
-- `vpx` resolves a package binary locally first by default and downloads it if not found; with `pkg@version`, `--package/-p`, or `--shell-mode`, it runs via `vp dlx`
-- `vp exec` runs a binary from the current project's `node_modules/.bin`
-- `vp dlx` runs a package binary without adding it as a dependency
-
-## `vpx`
-
-Use `vpx` for running any local or remote binary:
-
-```bash
-vpx <pkg[@version]> [args...]
-```
-
-### Options
-
-- `-p, --package <name>` installs one or more additional packages before running the command
-- `-c, --shell-mode` executes the command inside a shell
-- `-s, --silent` suppresses Vite+ output and only shows the command output
-
-### Examples
-
-```bash
-vpx eslint .
-vpx create-vue my-app
-vpx typescript@5.5.4 tsc --version
-vpx -p cowsay -c 'echo "hi" | cowsay'
-```
-
-## `vp exec`
-
-Use `vp exec` when the binary must come from the current project, for example a binary from a dependency installed in `node_modules/.bin`.
-
-```bash
-vp exec <command> [args...]
-```
-
-Examples:
-
-```bash
-vp exec eslint .
-vp exec tsc --noEmit
-```
-
-## `vp dlx`
-
-Use `vp dlx` for one-off package execution without adding the package to your project dependencies.
-
-```bash
-vp dlx <package> [args...]
-```
-
-Examples:
-
-```bash
-vp dlx create-vite
-vp dlx typescript tsc --version
-```

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

@@ -1,39 +0,0 @@
-# Why Vite+?
-
-Working in the JavaScript ecosystem today, developers need a runtime such as Node.js, a package manager like pnpm, a dev server, a linter, a formatter, a test runner, a bundler, a task runner, and a growing number of config files.
-
-Vite showed that frontend tooling could become dramatically faster by rethinking the architecture instead of accepting the status quo. Vite+ applies that same idea to the rest of the local development workflow, and unifies them all into a single package that speeds up and simplifies development.
-
-## The Problem Vite+ is Solving
-
-The JavaScript tooling ecosystem has seen its fair share of fragmentation and churn. Web apps keep getting larger, and as a result tooling performance, complexity, and inconsistencies have become real bottlenecks as projects grow.
-
-These bottlenecks are amplified in organizations with multiple teams, each using a different tooling stack. Dependency management, build infrastructure, and code quality become fragmented responsibilities, handled team by team and often not owned as a priority by anyone. As a result, dependencies drift out of sync, builds get slower, and code quality declines. Fixing those problems later requires significantly more effort, slows everyone down, and pulls teams away from shipping product.
-
-## What's Included in Vite+
-
-Vite+ brings the tools needed for modern web development together into a single, integrated toolchain. Instead of assembling and maintaining a custom toolchain, Vite+ provides a consistent entry point that manages the runtime, dependencies, development server, code quality checks, testing, and builds in one place.
-
-- **[Vite](https://vite.dev/)** and **[Rolldown](https://rolldown.rs/)** for development and application builds
-- **[Vitest](https://vitest.dev/)** for testing
-- **[Oxlint](https://oxc.rs/docs/guide/usage/linter.html)** and **[Oxfmt](https://oxc.rs/docs/guide/usage/formatter.html)** for linting and formatting
-- **[tsdown](https://tsdown.dev/)** for library builds or standalone executables
-- **[Vite Task](https://github.com/voidzero-dev/vite-task)** for task orchestration
-
-In practice, this means developers interact with one consistent workflow: `vp dev`, `vp check`, `vp test`, and `vp build`.
-
-This unified toolchain reduces configuration overhead, improves performance, and makes it easier for teams to maintain consistent tooling across projects.
-
-## Fast and Scalable by Default
-
-Vite+ is built on top of modern tooling such as Vite, Rolldown, Oxc, Vitest, and Vite Task to keep your projects fast and scalable as your codebase grows. By using Rust, we can speed up common tasks by [10× or sometimes even by 100×](https://voidzero.dev/posts/announcing-vite-plus-alpha#performance-scale). However, many Rust-based toolchains are incompatible with existing tools, or aren't extensible using JavaScript.
-
-Vite+ bridges Rust to JavaScript via [NAPI-RS](https://napi.rs/) which allows it to provide a familiar, easy-to-configure, and extensible interface in JavaScript with a great ecosystem-compatible developer experience.
-
-Unifying the toolchain has performance benefits beyond just using faster tools on their own. For example, many developers set up their linter with "type aware" tools, requiring a full-typecheck to be run during the linting stage. With `vp check` you can format, lint, and type-check your code all in a single pass, speeding up static checks by 2× compared to running type-aware lint rules and type-checks separately.
-
-## Fully Open Source
-
-Vite+ is fully open source and not a new framework or locked-down platform. Vite+ integrates with the existing Vite ecosystem and the frameworks built on top of it, including React, Vue, Svelte, and others. It can use pnpm, npm, yarn, or Bun as package manager, and manages the Node.js runtime for you.
-
-We always welcome contributions from the community. See our [Contributing Guidelines](https://github.com/voidzero-dev/vite-plus/blob/main/CONTRIBUTING.md) to get involved.

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

@@ -1,12 +0,0 @@
----
-home: true
-layout: home
-theme: light
-titleTemplate: The Unified Toolchain for the Web
----
-
-<script setup>
-import Home from '@layouts/Home.vue'
-</script>
-
-<Home />

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

@@ -1,35 +0,0 @@
----
-layout: page
-title: Meet the Team
-description: The development of Vite+ is guided by an international team.
----
-
-<script setup>
-import {
-  VPTeamPage,
-  VPTeamPageTitle,
-  VPTeamPageSection,
-  VPTeamMembers
-} from '@voidzero-dev/vitepress-theme'
-import { core } from './_data/team'
-</script>
-
-<VPTeamPage>
-  <VPTeamPageTitle>
-    <template #title>Meet the Team</template>
-    <template #lead>
-      The team members who work on Vite+ and are responsible for its development, maintenance, and community engagement.
-    </template>
-  </VPTeamPageTitle>
-  <VPTeamMembers :members="core" />
-  <!-- <VPTeamPageSection v-if="emeriti.length">
-    <template #title>Team Emeriti</template>
-    <template #lead>
-      Here we honor some no-longer-active team members who have made valuable
-      contributions in the past.
-    </template>
-    <template #members>
-      <VPTeamMembers size="small" :members="emeriti" />
-    </template>
-  </VPTeamPageSection> -->
-</VPTeamPage>

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

@@ -1,35 +0,0 @@
-# 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/vite-plus/templates/monorepo/README.md

@@ -1,29 +0,0 @@
-# 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/wrangler/README.md

@@ -1,63 +0,0 @@
-<h1 align="center"> ⛅️ wrangler </h1>
-<section align="center" id="shieldio-badges">
-<a href="https://www.npmjs.com/package/wrangler"><img alt="npm"  src="https://img.shields.io/npm/dw/wrangler?style=flat-square"></a>
-<img alt="GitHub contributors" src="https://img.shields.io/github/contributors/cloudflare/workers-sdk?style=flat-square">
-<img alt="GitHub commit activity (branch)" src="https://img.shields.io/github/commit-activity/w/cloudflare/workers-sdk/main?style=flat-square">
-<a href="https://discord.cloudflare.com"><img alt="Discord" src="https://img.shields.io/discord/595317990191398933?color=%23F48120&style=flat-square"></a>
-</section>
-
-`wrangler` is a command line tool for building [Cloudflare Workers](https://workers.cloudflare.com/).
-
-## Quick Start
-
-To get started quickly with a Hello World worker, run the command below:
-
-```bash
-npx wrangler init my-worker -y
-```
-
-For more info, visit our [Getting Started](https://developers.cloudflare.com/workers/get-started/guide/) guide.
-
-<details><summary>Wrangler System Requirements</summary>
-
-We support running the Wrangler CLI with the [Current, Active, and Maintenance](https://nodejs.org/en/about/previous-releases) versions of Node.js. Your Worker will always be executed in `workerd`, the open source Cloudflare Workers runtime.
-
-Wrangler is only supported on macOS 13.5+, Windows 11, and Linux distros that support glib 2.35. This follows [`workerd`'s OS support policy](https://github.com/cloudflare/workerd?tab=readme-ov-file#running-workerd).
-
-</details>
-
-## Documentation
-
-For the latest Wrangler documentation, [click here](https://developers.cloudflare.com/workers/wrangler/).
-
-To read more about Workers in general:
-
-- [Getting Started](https://developers.cloudflare.com/workers/get-started/guide/)
-- [How Workers works](https://developers.cloudflare.com/workers/reference/how-workers-works/)
-- [Observability](https://developers.cloudflare.com/workers/observability/)
-- [Platform](https://developers.cloudflare.com/workers/platform/)
-
-## Configuration
-
-Wrangler is configured via a `wrangler.jsonc` (recommended), `wrangler.json` or `wrangler.toml` file in the project root. An example configuration generated by `npx wrangler init` or `npx create cloudflare` is as follows:
-
-```jsonc
-{
-	"$schema": "node_modules/wrangler/config-schema.json",
-	"name": "my-worker",
-	"main": "./src/index.ts",
-	"compatibility_date": "YYYY-MM-DD",
-}
-```
-
-For more detailed information about configuration, refer to the [documentation](https://developers.cloudflare.com/workers/wrangler/configuration/).
-
-## Commands
-
-The `wrangler` CLI offers various commands, the most popular being:
-
-- `wrangler dev` to start a local development server, with live reloading and devtools.
-
-- `wrangler deploy` to deploy a Worker to the Cloudflare's global network.
-
-There are many more commands and options available, for a full list refer to the [official Cloudflare documentation](https://developers.cloudflare.com/workers/wrangler/commands/).