void 0.25.0 → 0.26.1

package/skills/void/SKILL.md

@@ -5,9 +5,12 @@ description: Build Void apps and use the Void CLI by loading the relevant bundle
 
 # Void
 
-Read only the guides needed for the user's task. The bundled documentation lives
-under `docs/` beside this skill; in an installed project it is available at
-`node_modules/void/skills/void/docs/`.
+Read only the guides needed for the user's task. Prefer the app's installed
+documentation at `node_modules/void/docs/` so it matches the app's Void version.
+All `docs/` paths below are relative to that package's root. When using this
+skill globally without a local Void installation, follow the skill's symlink to
+its real directory and use `../../docs/` in the same Void package. If the skill
+was copied without the package, use the guides at [https://void.cloud](https://void.cloud) instead.
 
 Before running a Void command, find its group in `docs/reference/cli.md`, then
 read the matching page under `docs/reference/cli/` for syntax, options, and
@@ -19,6 +22,8 @@ Use `void` and `@void/*` in imports, examples, and package manifests. Follow the
 project's existing framework and deployment destination. Deploying to a Void
 platform requires an explicit `void connect <url>` first; never infer a platform
 from old examples, tokens, or project IDs.
+Platform hostnames passed to `void connect` default to HTTPS; include `http://`
+explicitly when connecting to a local HTTP platform.
 For a one-time deployment elsewhere, connect to that platform, then set
 `VOID_API_URL` for the deploy command and pass `--project <slug>`. This preserves
 the app's existing saved destination, including when the target project is new.
@@ -78,7 +83,8 @@ the app's existing saved destination, including when the target project is new.
 - Declare application environment keys in `env.ts` and access them through
   `void/env`; follow `docs/guide/env-vars.md` for local and production values.
 - For platform setup, follow the pages linked from
-  `docs/guide/self-hosted-platform.md`. For recovery, use its documented resume
+  `docs/guide/self-hosted-platform.md`. Use `void platform list` to find the
+  installation slug for maintenance. For recovery, use its documented resume
   or repair workflow and preserve the installation's credentials and resources.
 - Use `--plan` to review platform changes. If an operation has an uncertain
   outcome, inspect its status and events before retrying.
@@ -87,4 +93,4 @@ If the user invokes this skill without a task, inspect the app's local structure
 configuration, and saved deployment destination, give a brief status, and ask
 what they want to work on.
 
-For AI and Sandbox operations, use `.match({ ok, limited })` and choose a useful quota fallback. In Pages, prefer the adapter’s `Form` with `useForm()` so action failures remain visible and entered data is preserved. See `docs/guide/ai.md`, `docs/guide/sandboxes.md`, and `docs/guide/pages-routing/actions-and-forms.md`.
+Await AI and Sandbox operations normally. Usage limits reject with `UsageLimit` from `void/limits`; Void routes and Pages actions automatically return HTTP 429. Optionally catch with `instanceof UsageLimit` for a fallback or custom response. In Pages, prefer the adapter’s `Form` with `useForm()` so action failures remain visible and entered data is preserved. See `docs/guide/ai.md`, `docs/guide/sandboxes.md`, and `docs/guide/pages-routing/actions-and-forms.md`.

package/dist/cf-build-output-ChY6-XWP.mjs

@@ -1,2 +0,0 @@
-import { t as prepareCfBuildOutput } from "./cf-build-output-U8o1Gl6X.mjs";
-export { prepareCfBuildOutput };

package/dist/client-B4Me-9HE.mjs

@@ -1,2 +0,0 @@
-import { r as PlatformClient } from "./client-RsPo8wsP.mjs";
-export { PlatformClient };

package/dist/config-0acf1oys.mjs

@@ -1,2 +0,0 @@
-import { t as writeDrizzleConfig } from "./config-D8MOgiQV.mjs";
-export { writeDrizzleConfig };

package/dist/config-D8MOgiQV.mjs

@@ -1,32 +0,0 @@
-import { a as join, l as relative } from "./dist-BVqXeR_h.mjs";
-import { n as readProjectPaths } from "./project-paths-GgcMozYz.mjs";
-import { n as schemaSpecifier, t as discoverSchema } from "./discover-BcPPiF1o.mjs";
-import { mkdirSync, writeFileSync } from "node:fs";
-//#region src/drizzle/config.ts
-/**
-* Write a temporary drizzle-kit config to `.void/drizzle.config.json`.
-* All paths are relative to the project root (drizzle-kit resolves
-* relative to `--config` file location, so we use project-root-relative).
-*
-* @returns Absolute path to the written config file.
-*/
-function writeDrizzleConfig(root, dbPath, dialect = "sqlite", options) {
-	const paths = readProjectPaths(root);
-	const schema = discoverSchema(root, paths);
-	const schemaPaths = [...schema ? [schemaSpecifier(schema, root)] : [], ...(options?.additionalSchemas ?? []).map((path) => `./${relative(root, path)}`)];
-	if (schemaPaths.length === 0) throw new Error(`db: No Drizzle schema found. Create ${paths.sourceRelative("db/schema.ts")} or run \`void gen model <name>\`.`);
-	const outDir = join(root, ".void");
-	mkdirSync(outDir, { recursive: true });
-	const config = {
-		dialect,
-		schema: schemaPaths.length === 1 ? schemaPaths[0] : schemaPaths,
-		out: `./${relative(root, paths.migrationsDir)}`,
-		migrations: { prefix: "timestamp" },
-		dbCredentials: { url: dbPath }
-	};
-	const configPath = join(outDir, "drizzle.config.json");
-	writeFileSync(configPath, JSON.stringify(config, null, 2) + "\n");
-	return configPath;
-}
-//#endregion
-export { writeDrizzleConfig as t };

package/dist/deploy-BDu1vhSH.mjs

@@ -1,2 +0,0 @@
-import { r as runDeploy, t as parseRootWranglerConfig, y as checkWranglerMigrationApplySet } from "./deploy-DfsAe-T0.mjs";
-export { checkWranglerMigrationApplySet, parseRootWranglerConfig, runDeploy };

package/dist/discover-AMCBXivQ.mjs

@@ -1,2 +0,0 @@
-import { t as discoverSchema } from "./discover-BcPPiF1o.mjs";
-export { discoverSchema };

package/dist/fetch-error-Sp1R4mZv.d.mts

@@ -1,20 +0,0 @@
-//#region src/runtime/fetch-error.d.ts
-type FetchResponse<T = unknown> = Response & {
-  _data?: T;
-};
-type FetchError<T = unknown> = Error & {
-  request?: RequestInfo;
-  options?: RequestInit & Record<string, unknown>;
-  response?: FetchResponse<T>;
-  data?: T;
-  status?: number;
-  statusText?: string;
-  statusCode?: number;
-  statusMessage?: string;
-};
-type FetchErrorConstructor = new <T = unknown>(message: string, opts?: {
-  cause: unknown;
-}) => FetchError<T>;
-declare const FetchError: FetchErrorConstructor;
-//#endregion
-export { FetchError as t };

package/dist/gen-ById9r2j.mjs

@@ -1,2 +0,0 @@
-import { r as runGenCommand } from "./gen-NjwoG9FK.mjs";
-export { runGenCommand };

package/dist/help-DPGBwomV.mjs

@@ -1,2 +0,0 @@
-import { r as printHelpPage } from "./help-DRZXC4fj.mjs";
-export { printHelpPage };

package/dist/login-C98-sw79.mjs

@@ -1,2 +0,0 @@
-import { r as selectPlatformLoginMethod } from "./login-pWQHYVu2.mjs";
-export { selectPlatformLoginMethod };

package/dist/migrate-CEu2X5DB.mjs

@@ -1,2 +0,0 @@
-import { n as runMigrateCommand } from "./migrate-CV1on-yJ.mjs";
-export { runMigrateCommand };

package/dist/plan-D1Q5rf-r.mjs

@@ -1,2 +0,0 @@
-import { n as buildMigrationPlanBundle } from "./plan-NPpwZ_kc.mjs";
-export { buildMigrationPlanBundle };

package/dist/platform-args-Cq6EjQro.mjs

@@ -1,2 +0,0 @@
-import { t as parsePlatformArgs } from "./platform-args-Bzf8JPc2.mjs";
-export { parsePlatformArgs };

package/dist/prepare-CnjcTV2s.mjs

@@ -1,2 +0,0 @@
-import { t as prepareProject } from "./prepare-DnaKBi--.mjs";
-export { prepareProject };

package/dist/resolve-project-DtbidV4y.mjs

@@ -1,2 +0,0 @@
-import { n as inferDefaultSlug } from "./resolve-project-BG5ORGID.mjs";
-export { inferDefaultSlug };

package/dist/route-url-CG7U-cRN.mjs

@@ -1,15 +0,0 @@
-//#region src/runtime/route-url.ts
-/** Expand complete route tokens without changing query strings or fragments. */
-function interpolateRouteParams(path, params) {
-	if (!params) return path;
-	const suffixIndex = path.search(/[?#]/);
-	const pathname = suffixIndex === -1 ? path : path.slice(0, suffixIndex);
-	const suffix = suffixIndex === -1 ? "" : path.slice(suffixIndex);
-	return pathname.replace(/(^|\/):([^/{}]+)(\{\.\+\})?(?=\/|$)/g, (token, prefix, name, catchAll) => {
-		if (!Object.hasOwn(params, name)) return token;
-		const value = params[name];
-		return prefix + (catchAll ? value.split("/").map(encodeURIComponent).join("/") : encodeURIComponent(value));
-	}) + suffix;
-}
-//#endregion
-export { interpolateRouteParams as t };

package/dist/runner-CXA9Fh8h.mjs

@@ -1,2 +0,0 @@
-import { i as openSqliteDatabase, n as getAppliedMigrations, o as runMigrations, r as getMiniflareDatabasePath, t as getApplicationTables } from "./runner-Ol0TNjk6.mjs";
-export { getApplicationTables, getAppliedMigrations, getMiniflareDatabasePath, openSqliteDatabase, runMigrations };

package/dist/validate-Dq_L3s0S.mjs

@@ -1,2 +0,0 @@
-import { i as validateMigrations } from "./validate-ctOrgiS3.mjs";
-export { validateMigrations };

package/skills/void/docs/guide/platform/installation/uninstall.md

@@ -1,69 +0,0 @@
----
-outline: deep
----
-
-# Disable and Uninstall
-
-To pause a platform without removing its data:
-
-```sh
-void platform disable [id] --plan
-void platform disable [id]
-```
-
-Disabled platforms reject application traffic while retaining domains and routes. Repair and upgrade preserve that state. Restore traffic with:
-
-```sh
-void platform enable [id] --plan
-void platform enable [id]
-```
-
-Add `--yes` to commands that make changes in a non-interactive shell.
-
-While disabled, the platform retries queue batches after five minutes instead of delivering them to apps. Queue retention and retry limits still apply. For a long pause, plan a dead-letter queue or another way to recover messages.
-
-## Uninstall
-
-Preview removal before applying it:
-
-```sh
-void platform uninstall [id] --plan
-void platform uninstall [id]
-```
-
-Uninstall blocks platform traffic, removes Queues that no remaining platform Worker uses, and records the resources left for you to review. By default, Workers, the Queues they use, KV, R2, Hyperdrive, the dispatch namespace, and AI Gateway remain in your account. Adopted resources, external PostgreSQL, zones, DNS records, routes, custom domains, and Cloudflare Access resources are always retained.
-
-To also remove eligible data resources owned by the installer:
-
-```sh
-void platform uninstall [id] --purge-data
-```
-
-Even with `--purge-data`, Void retains Workers, the Queues they use, R2, AI Gateway, DNS records, routes, custom domains, Access resources, adopted resources, external PostgreSQL, and zones. Review those in the Cloudflare dashboard if you want to remove them.
-
-### Remove retained resources
-
-Cloudflare refuses to delete a resource while a platform Worker still uses it. In the Cloudflare dashboard, remove what is left in this order, skipping anything already gone:
-
-1. Delete the platform DNS record, Worker routes, and custom domains.
-2. Open each platform Queue and remove the platform API Worker from its consumers.
-3. Delete the platform Workers.
-4. Delete the platform Queues.
-5. Delete the application Workers in the dispatch namespace, then delete the namespace.
-6. Delete the platform KV namespaces and Hyperdrive configuration.
-7. Empty the R2 bucket, then delete it.
-8. Delete the AI Gateway.
-
-If installation configured Cloudflare Access, the uninstall plan lists its recorded applications and service tokens with their ownership and IDs. Review them in Zero Trust after uninstall. Remove installer-created resources only when nothing else uses them; resources connected from an existing company setup remain under their owner's control.
-
-Uninstall does not remove the applications created for [project Zero Trust](/guide/platform/administration/zero-trust). While Zero Trust is enabled or still has Access applications, uninstall and `--plan` stop before any change and list those applications. Run `void platform zero-trust disable` first. Uninstall reads this from the installation database, so it also stops when the database cannot be reached.
-
-::: details Why some resources require manual cleanup
-
-Resources that may have been shared or repurposed require manual review before deletion. Void verifies ownership, keeps those resources in place, and blocks platform traffic.
-
-If removal is interrupted, rerun the command to continue. If a resource has changed ownership, resolve the reported conflict before retrying.
-
-External PostgreSQL and its data always remain under your control.
-
-:::

package/skills/void/docs/integrations/agents.md

@@ -1,26 +0,0 @@
----
-outline: deep
----
-
-# Using Void with Coding Agents
-
-`void init` gives your coding agent Void instructions and reference docs. To add or refresh just that setup, run:
-
-```sh
-npx void init --agents
-```
-
-Void updates `AGENTS.md` with development guidance and links to the docs, preserving your existing instructions.
-
-The complete Markdown docs ship with the installed package at `node_modules/void/skills/void/docs/`. Agents can read them directly, even without a linked skill.
-
-## Skills
-
-Skills point your agent to the commands and docs it needs for the task. They link to the installed `void` package, so the guidance matches the version your app uses.
-
-Void ships two skills:
-
-- **`void`:** commands and docs for app development.
-- **`migrate-vite-cloudflare-to-void`:** migration skill for converting existing `@cloudflare/vite-plugin` apps to Void.
-
-Skills are linked automatically by `void init --agents` when it detects a supported agent's configuration. For example, Claude Code uses `.claude/skills/`. If no agent is detected, skill linking is skipped and `AGENTS.md` points directly to the bundled docs.

package/dist/{runner-pg-D4OPlil-.mjs → runner-pg-DV8p_zjA.mjs}

@@ -8,10 +8,6 @@ async function readPgAppliedMigrations(client) {
 		throw error;
 	}
 }
-/**
-* Apply unapplied SQL migrations via a connected PostgreSQL client.
-* Each migration runs in its own transaction (BEGIN/COMMIT).
-*/
 async function getPgAppliedMigrations(url) {
 	const { Client } = await import("pg");
 	const client = new Client({ connectionString: url });
@@ -22,6 +18,10 @@ async function getPgAppliedMigrations(url) {
 		await client.end();
 	}
 }
+/**
+* Apply unapplied SQL migrations via a connected PostgreSQL client.
+* Each migration runs in its own transaction (BEGIN/COMMIT).
+*/
 async function applyPgMigrations(client, migrations) {
 	if (migrations.length === 0) return [];
 	await client.query(`CREATE TABLE IF NOT EXISTS _void_migrations (name TEXT PRIMARY KEY, applied_at TEXT NOT NULL)`);

package/{skills/void/docs → docs}/guide/database/d1.md

@@ -29,8 +29,8 @@ See [Database commands](../../reference/cli/database.md#database) for the full w
 D1 supports batching multiple statements into a single round-trip:
 
 ```ts
-import { db, eq } from 'void/db';
 import { users, posts } from '@schema';
+import { db, eq } from 'void/db';
 
 await db.batch([
   db.delete(posts).where(eq(posts.userId, userId)),
@@ -51,9 +51,9 @@ Use `env.DB` from `cloudflare:workers` with another query library or the raw D1
 ### Kysely
 
 ```ts
+import { env } from 'cloudflare:workers';
 import { Kysely } from 'kysely';
 import { D1Dialect } from 'kysely-d1';
-import { env } from 'cloudflare:workers';
 
 const db = new Kysely<Database>({ dialect: new D1Dialect({ database: env.DB }) });
 ```

package/{skills/void/docs → docs}/guide/pages-routing/islands.md

@@ -135,10 +135,10 @@ let { posts } = $props();
 ```
 
 ```tsx [Solid]
+import { For } from 'solid-js';
 // pages/blog/index.island.tsx
 import Counter from './_Counter' with { island: 'load' };
 import PostForm from './_PostForm' with { island: 'visible' };
-import { For } from 'solid-js';
 
 export default function BlogIndex(props) {
   return (
@@ -181,9 +181,9 @@ The `island` attribute value controls _when_ the component hydrates:
 | `"media:(query)"` | CSS media query matches     | Responsive components (e.g., mobile-only)  |
 
 ```tsx
+import Comments from './_Comments' with { island: 'visible' };
 import CookieBanner from './_CookieBanner' with { island: 'idle' };
 import MobileMenu from './_MobileMenu' with { island: 'media:(max-width: 768px)' };
-import Comments from './_Comments' with { island: 'visible' };
 ```
 
 ## Server Handlers

package/{skills/void/docs → docs}/guide/server-routing.md

@@ -43,10 +43,10 @@ export const GET = defineHandler((c) => {
 A file can export multiple methods:
 
 ```ts
+import { users } from '@schema';
 // routes/api/users/index.ts  →  GET + POST /api/users
 import { defineHandler } from 'void';
 import { db } from 'void/db';
-import { users } from '@schema';
 
 export const GET = defineHandler(async () => {
   return await db.select().from(users);
@@ -77,10 +77,10 @@ Return values are automatically converted:
 `defineHandler.withValidator()` adds input validation for `body`, `query`, and `params`. The recommended approach is to derive validators from your [Drizzle schema](./database.md#schema-derived-validators), which keeps validation in sync with the database.
 
 ```ts
+import { users, insertUserSchema } from '@schema';
 // routes/api/users/index.ts
 import { defineHandler } from 'void';
 import { db } from 'void/db';
-import { users, insertUserSchema } from '@schema';
 
 export const POST = defineHandler.withValidator({
   body: insertUserSchema,
@@ -216,9 +216,9 @@ defineHandler(middleware1, middleware2, handler);
 Middleware runs in order. Each can short-circuit (return a response without calling `next()`) or post-process (modify the response after `await next()`). Both `defineMiddleware`-wrapped functions and raw Hono `MiddlewareHandler` functions are accepted.
 
 ```ts
+import { cors } from 'hono/cors';
 // routes/api/stats.ts
 import { defineHandler } from 'void';
-import { cors } from 'hono/cors';
 
 export const GET = defineHandler(cors({ origin: 'https://app.example.com' }), (c) => ({
   stats: '...',

package/{skills/void/docs → docs}/integrations/frameworks/analog.md

@@ -27,8 +27,8 @@ Void provides the local Cloudflare binding runtime. `nitro-cloudflare-dev` creat
 
 ```ts
 import { resolve } from 'node:path';
-import { defineConfig } from 'vite';
 import analog from '@analogjs/platform';
+import { defineConfig } from 'vite';
 import { voidPlugin } from 'void';
 
 export default defineConfig({
@@ -90,8 +90,8 @@ Void-managed auth is not supported in framework mode yet. Use Better Auth's offi
 ```ts
 // src/app/pages/users.server.ts
 import type { PageServerLoad } from '@analogjs/router';
-import { db } from 'void/db';
 import { users } from '@schema';
+import { db } from 'void/db';
 
 export const load = async ({ event }: PageServerLoad) => {
   return { users: await db.select().from(users) };
@@ -117,9 +117,9 @@ Declare variables in `env.ts` and read them with `import { env } from "void/env"
 You can also access raw Cloudflare bindings via the H3 event context or the `cloudflare:workers` module:
 
 ```ts
+import { env } from 'cloudflare:workers';
 // src/server/routes/api/users.ts
 import { eventHandler } from 'h3';
-import { env } from 'cloudflare:workers';
 
 export default eventHandler(async () => {
   const { results } = await env.DB.prepare('SELECT * FROM users').all();

package/{skills/void/docs → docs}/integrations/frameworks/react-router.md

@@ -24,8 +24,8 @@ npm install -D void
 ### 3. Configure `vite.config.ts`
 
 ```ts
-import { defineConfig } from 'vite';
 import { reactRouter } from '@react-router/dev/vite';
+import { defineConfig } from 'vite';
 import { voidPlugin } from 'void';
 
 export default defineConfig({
@@ -52,9 +52,9 @@ Void-managed auth is not supported in framework mode yet. Use Better Auth's offi
 ### Database
 
 ```tsx
-import type { Route } from './+types/users';
-import { db } from 'void/db';
 import { users } from '@schema';
+import { db } from 'void/db';
+import type { Route } from './+types/users';
 
 export async function loader({}: Route.LoaderArgs) {
   return { users: await db.select().from(users) };

package/{skills/void/docs → docs}/integrations/frameworks/sveltekit.md

@@ -91,9 +91,9 @@ Void-managed auth is not supported in framework mode yet. Use Better Auth's offi
 ### Database
 
 ```ts
+import { users } from '@schema';
 // src/routes/users/+page.server.ts
 import { db } from 'void/db';
-import { users } from '@schema';
 
 export async function load() {
   return { users: await db.select().from(users) };

package/{skills/void/docs → docs}/integrations/frameworks/tanstack-start.md

@@ -24,9 +24,9 @@ npm install -D void
 ### 3. Configure `vite.config.ts`
 
 ```ts
-import { defineConfig } from 'vite';
 import { tanstackStart } from '@tanstack/react-start/plugin';
 import react from '@vitejs/plugin-react';
+import { defineConfig } from 'vite';
 import { voidPlugin } from 'void';
 
 export default defineConfig({
@@ -54,9 +54,9 @@ Void-managed auth is not supported in framework mode yet. Use Better Auth's offi
 ### Database
 
 ```tsx
+import { users } from '@schema';
 import { createServerFn } from '@tanstack/react-start';
 import { db } from 'void/db';
-import { users } from '@schema';
 
 const getUsers = createServerFn().handler(async () => {
   return db.select().from(users);

package/{skills/void/docs → docs}/reference/api/database.md

@@ -11,8 +11,8 @@ Imported from `"void/db"`. The `db` export is a [Drizzle ORM](https://orm.drizzl
 Default Drizzle instance, pre-wired with your schema from `db/schema.ts`.
 
 ```ts
-import { db } from 'void/db';
 import { users } from '@schema';
+import { db } from 'void/db';
 
 const allUsers = await db.select().from(users).all();
 ```
@@ -30,8 +30,8 @@ Creates a Drizzle instance for the active dialect.
 For D1 projects, pass a specific D1 binding. Use this when you have multiple D1 databases or need a non-default binding.
 
 ```ts
-import { createDb } from 'void/db';
 import { env } from 'cloudflare:workers';
+import { createDb } from 'void/db';
 
 const db = createDb(env.MY_OTHER_DB);
 ```