void 0.21.9 → 0.23.0

package/skills/void/docs/integrations/frameworks/analog.md

@@ -79,7 +79,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with Analog. Use them in page server loaders, actions, and API routes:
 
@@ -99,75 +99,16 @@ export const load = async ({ event }: PageServerLoad) => {
 ```
 
 ::: warning ⚠️ Analog limitation
-Analog uses Nitro, which bundles server routes outside of Vite's plugin pipeline. The schema cannot be injected into the `db` instance, so `db.query.*` relational queries are not available in Analog. Use the standard query builder API (`db.select().from(table)`) instead.
+Use `db.select().from(table)` for database queries in Analog. The `db.query.*` relational API is not available.
 :::
 
-### KV Storage
+### Other resources
 
-```ts
-import type { PageServerLoad } from '@analogjs/router';
-import { kv } from 'void/kv';
-
-export const load = async ({ event }: PageServerLoad) => {
-  return { settings: await kv.get('app:settings') };
-};
-```
-
-### Blob Storage
-
-```ts
-import type { PageServerLoad } from '@analogjs/router';
-import { storage } from 'void/storage';
-
-export const load = async ({ event }: PageServerLoad) => {
-  return { avatar: await storage.get('avatars/user-1.png') };
-};
-```
-
-### AI
-
-```ts
-// src/server/routes/api/summarize.ts
-import { eventHandler } from 'h3';
-import { ai } from 'void/ai';
-
-export default eventHandler(async () => {
-  return ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-    prompt: 'Summarize the latest news',
-  });
-});
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
-
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
 `void/env` replaces the H3 event context and `import { env } from "cloudflare:workers"` for env-var access. Keep those around when you need raw binding access (D1, KV, R2, etc.).
 

package/skills/void/docs/integrations/frameworks/astro.md

@@ -40,8 +40,6 @@ export default defineConfig({
 });
 ```
 
-By default, Astro's Cloudflare runtime and `voidPlugin()` migrations share local state at `.wrangler/state/v3`, so no extra persistence configuration is required.
-
 ### 4. Create `void.config.ts`
 
 Void uses this config for the Cloudflare adapter during development and deployment:
@@ -67,7 +65,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with Astro in both local dev and production when using Astro 6+ with `nodejs_als`.
 
@@ -97,76 +95,13 @@ export const GET: APIRoute = async () => {
 };
 ```
 
-### KV Storage
-
-Use `void/kv` in both dev and production:
-
-```ts
-import type { APIRoute } from 'astro';
-import { kv } from 'void/kv';
-
-export const GET: APIRoute = async () => {
-  const settings = await kv.get('app:settings');
-  return Response.json(settings);
-};
-```
-
-### Blob Storage
-
-```ts
-import type { APIRoute } from 'astro';
-import { storage } from 'void/storage';
-
-export const GET: APIRoute = async () => {
-  const avatar = await storage.get('avatars/user-1.png');
-  return new Response(avatar);
-};
-```
-
-### AI
+### Other resources
 
-```ts
-import type { APIRoute } from 'astro';
-import { ai } from 'void/ai';
-
-export const POST: APIRoute = async () => {
-  const result = await ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-    prompt: 'Summarize the latest news',
-  });
-  return Response.json(result);
-};
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
-
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
 Void always uses `VITE_*` for client-exposed schema keys, including in Astro projects. Astro's separate `PUBLIC_*` convention still applies to direct `import.meta.env` access, but it does not change the `void/env` server/client boundary.
 
@@ -195,7 +130,3 @@ const { DB } = Astro.locals.runtime.env;
 const { results } = await DB.prepare("SELECT * FROM users").all();
 ---
 ```
-
-::: tip Direct Binding Access
-`Astro.locals.runtime.env` is still useful when you need direct access to raw Cloudflare bindings.
-:::

package/skills/void/docs/integrations/frameworks/nuxt.md

@@ -43,8 +43,6 @@ export default defineNuxtConfig({
 });
 ```
 
-By default, Nuxt's Cloudflare development runtime and `voidPlugin()` migrations share local state at `.wrangler/state/v3`, so no extra persistence configuration is required.
-
 ### 4. Create `void.config.ts`
 
 Void generates the Cloudflare config used by Nuxt's development runtime:
@@ -68,7 +66,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with Nuxt. Use them in server routes, API handlers, and middleware:
 
@@ -87,71 +85,16 @@ export default defineEventHandler(async () => {
 ```
 
 ::: warning ⚠️ Nuxt limitation
-Nuxt uses Nitro, which bundles server routes outside of Vite's plugin pipeline. The schema cannot be injected into the `db` instance, so `db.query.*` relational queries are not available in Nuxt. Use the standard query builder API (`db.select().from(table)`) instead.
+Use `db.select().from(table)` for database queries in Nuxt. The `db.query.*` relational API is not available.
 :::
 
-### KV Storage
-
-```ts
-import { kv } from 'void/kv';
-
-export default defineEventHandler(async () => {
-  return kv.get('app:settings');
-});
-```
-
-### Blob Storage
-
-```ts
-import { storage } from 'void/storage';
-
-export default defineEventHandler(async () => {
-  return storage.get('avatars/user-1.png');
-});
-```
-
-### AI
-
-```ts
-import { ai } from 'void/ai';
-
-export default defineEventHandler(async () => {
-  return ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-    prompt: 'Summarize the latest news',
-  });
-});
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
+### Other resources
 
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
 `void/env` replaces `useRuntimeConfig()` and `event.context.cloudflare.env` for env-var access. Keep `event.context.cloudflare.env` around when you need raw binding access (D1, KV, R2, etc.), and `useRuntimeConfig()` when you need non-env runtime config.
 

package/skills/void/docs/integrations/frameworks/overview.md

@@ -14,32 +14,23 @@ TanStack Start and React Router use the Cloudflare Vite plugin provided by Void.
 
 ## Supported Frameworks
 
-| Framework                                           | Package                 | Integration                                                                  |
-| --------------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------- |
-| [TanStack Start](https://tanstack.com/start/latest) | `@tanstack/react-start` | Vite plugin composition. `voidPlugin()` runs alongside the framework plugin. |
-| [React Router v7](https://reactrouter.com/)         | `@react-router/dev`     | Vite plugin composition. Setup matches TanStack Start.                       |
-| [SvelteKit](https://svelte.dev/docs/kit)            | `@sveltejs/kit`         | Vite-based, uses its own Cloudflare adapter                                  |
-| [Nuxt](https://nuxt.com/)                           | `nuxt`                  | Own CLI and build toolchain                                                  |
-| [Analog](https://analogjs.org/)                     | `@analogjs/platform`    | Vite-based, uses Nitro with Cloudflare preset                                |
-| [Astro **v6+**](https://astro.build/)               | `astro`                 | Own CLI and Cloudflare adapter (v6 required)                                 |
+| Framework                             | Package                 | Integration                                                                  |
+| ------------------------------------- | ----------------------- | ---------------------------------------------------------------------------- |
+| [TanStack Start](./tanstack-start.md) | `@tanstack/react-start` | Vite plugin composition. `voidPlugin()` runs alongside the framework plugin. |
+| [React Router v7](./react-router.md)  | `@react-router/dev`     | Vite plugin composition. Setup matches TanStack Start.                       |
+| [SvelteKit](./sveltekit.md)           | `@sveltejs/kit`         | Vite-based, uses its own Cloudflare adapter                                  |
+| [Nuxt](./nuxt.md)                     | `nuxt`                  | Own CLI and build toolchain                                                  |
+| [Analog](./analog.md)                 | `@analogjs/platform`    | Vite-based, uses Nitro with Cloudflare preset                                |
+| [Astro **v6+**](./astro.md)           | `astro`                 | Own CLI and Cloudflare adapter (v6 required)                                 |
 
 Detection is automatic. The CLI reads your `package.json` dependencies.
 
-See the individual framework guides for setup instructions:
-
-- [TanStack Start](./tanstack-start.md)
-- [React Router](./react-router.md)
-- [SvelteKit](./sveltekit.md)
-- [Nuxt](./nuxt.md)
-- [Analog](./analog.md)
-- [Astro](./astro.md)
-
 ## Feature Support
 
 With `voidPlugin()` added to the framework's Vite config, frameworks get most of the same backend/platform features as [Void apps](../../guide/app-types.md#void-apps):
 
 - **Binding inference:** D1, KV, R2, AI, and queues are detected from source code.
-- **Typed database:** query helpers are generated from `db/migrations/*.sql`.
+- **Typed database:** query types come from your Drizzle schema.
 - **Migrations:** local D1 is updated on dev startup, and migrations are validated and deployed with `void deploy`.
 - **Runtime helpers:** `void/db`, `void/kv`, `void/storage`, and `void/ai` give you typed access to Cloudflare bindings in dev and production.
 - **Auth:** Void-managed auth is not supported in framework mode yet. For now, use Better Auth's official integration for your framework.
@@ -104,40 +95,6 @@ Existing bindings are preserved. D1, KV, and R2 use local placeholder IDs until
 
 Void combines these settings with inferred bindings and records provisioned resource IDs in `void.lock.json`. Commit both files.
 
-## Deploy Pipeline
-
-SvelteKit, Nuxt, Analog, and Astro apps follow this pipeline:
+## Deployment
 
-```
-void deploy
-  │
-  ├─ 1. Detect framework
-  │    Reads package.json → determines framework + output conventions
-  │
-  ├─ 2. Build
-  │    Runs framework's build command (or void.config.ts `build` override)
-  │    SvelteKit: vite build → .svelte-kit/cloudflare/
-  │    Nuxt:      nuxt build → .output/
-  │    Analog:    vite build → dist/analog/
-  │    Astro:     astro build → dist/
-  │
-  ├─ 3. Analyze
-  │    ├─ Locate worker entry + static assets from known output paths
-  │    ├─ Infer bindings from source or read from void.config.ts
-  │    ├─ Collect migrations from db/migrations/*.sql
-  │    ├─ Detect cron and queue handlers
-  │    └─ Read void.config.ts Cloudflare settings
-  │
-  ├─ 4. Wrap (if needed)
-  │    If crons or queues are configured:
-  │    ├─ Generate wrapper entry module
-  │    ├─ Bundle with Vite (wraps framework's worker)
-  │    └─ Wrapper adds scheduled/queue handlers
-  │
-  ├─ 5. Package + upload
-  │    Same as full-stack: hash-based asset diffing,
-  │    multipart upload, platform provisioning
-  │
-  └─ 6. Live
-       https://my-app.void.app
-```
+Run `void deploy` to build with your framework and deploy to the selected target. See [Deployment](../../guide/deployment.md) for setup and CI.

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

@@ -43,7 +43,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with React Router. Use them in loaders and actions:
 
@@ -61,70 +61,15 @@ export async function loader({}: Route.LoaderArgs) {
 }
 ```
 
-### KV Storage
+### Other resources
 
-```tsx
-import { kv } from 'void/kv';
-
-export async function loader() {
-  return { settings: await kv.get('app:settings') };
-}
-```
-
-### Blob Storage
-
-```tsx
-import { storage } from 'void/storage';
-
-export async function loader() {
-  return { avatar: await storage.get('avatars/user-1.png') };
-}
-```
-
-### AI
-
-```tsx
-import { ai } from 'void/ai';
-
-export async function action() {
-  return ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-    prompt: 'Summarize the latest news',
-  });
-}
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
-
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
-React Router keeps loaders and components in the same route file. Void's client check therefore treats that file as reachable from the browser, even though React Router removes loaders from the client bundle. Read server secrets in a `.server.ts` companion module to keep that separation explicit.
+Read server secrets in a `.server.ts` companion module and import it into your loader or action. Void rejects server-secret reads in route files that also contain browser components.
 
 ## Accessing Bindings Directly
 

package/skills/void/docs/integrations/frameworks/sveltekit.md

@@ -64,13 +64,11 @@ export default defineConfig({
 });
 ```
 
-By default, SvelteKit's Cloudflare adapter, `voidPlugin()` migrations, and `void db` commands share local state at `.wrangler/state/v3`, so no extra `platformProxy.persist` configuration is required.
-
 ### 5. Configure `tsconfig.json`
 
-SvelteKit generates `.svelte-kit/tsconfig.json` and expects your root config to extend it. Void generates `.void/tsconfig.json` for project-specific aliases such as `void/db` and `@schema`.
+Extend SvelteKit’s generated config. The `withVoidTSConfig()` hook in the Vite config above adds Void’s types and aliases:
 
-Do not add Void's `compilerOptions.paths` to the root `tsconfig.json`; SvelteKit warns because root-level paths override its generated aliases. The `withVoidTSConfig()` hook merges Void's generated files and aliases into SvelteKit's generated config instead.
+Keep `compilerOptions.paths` out of the root config so it does not override SvelteKit’s aliases.
 
 ```json
 {
@@ -90,7 +88,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with SvelteKit. Use them in server load functions, actions, and API routes:
 
@@ -108,70 +106,13 @@ export async function load() {
 }
 ```
 
-### KV Storage
-
-```ts
-import { kv } from 'void/kv';
-
-export async function load() {
-  return { settings: await kv.get('app:settings') };
-}
-```
-
-### Blob Storage
-
-```ts
-import { storage } from 'void/storage';
-
-export async function load() {
-  return { avatar: await storage.get('avatars/user-1.png') };
-}
-```
-
-### AI
-
-```ts
-import { ai } from 'void/ai';
+### Other resources
 
-export const actions = {
-  summarize: async () => {
-    return ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-      prompt: 'Summarize the latest news',
-    });
-  },
-};
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
-
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
 ## Accessing Bindings Directly
 

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

@@ -45,7 +45,7 @@ void auth login
 void deploy
 ```
 
-## Using Void Platform Features
+## Using Void Features
 
 Most [Void platform features](../../guide/app-types.md#void-apps) work with TanStack Start. Use them in server functions:
 
@@ -63,71 +63,13 @@ const getUsers = createServerFn().handler(async () => {
 });
 ```
 
-### KV Storage
+### Other resources
 
-```tsx
-import { createServerFn } from '@tanstack/react-start';
-import { kv } from 'void/kv';
-
-const getSettings = createServerFn().handler(async () => {
-  return kv.get('app:settings');
-});
-```
-
-### Blob Storage
-
-```tsx
-import { createServerFn } from '@tanstack/react-start';
-import { storage } from 'void/storage';
-
-const getAvatar = createServerFn().handler(async () => {
-  return storage.get('avatars/user-1.png');
-});
-```
-
-### AI
-
-```tsx
-import { createServerFn } from '@tanstack/react-start';
-import { ai } from 'void/ai';
-
-const summarize = createServerFn().handler(async () => {
-  return ai.run('@cf/meta/llama-3.3-70b-instruct-fp8-fast', {
-    prompt: 'Summarize the latest news',
-  });
-});
-```
-
-### Cron Jobs
-
-```ts
-// crons/daily-cleanup.ts
-import { defineScheduled } from 'void';
-
-export const cron = '0 0 * * *';
-
-export default defineScheduled(async () => {
-  // runs daily at midnight
-});
-```
-
-### Queue Consumers
-
-```ts
-// queues/emails.ts
-import { defineQueue } from 'void';
-
-export default defineQueue<{ to: string; subject: string }>(async (batch) => {
-  for (const msg of batch.messages) {
-    // process each message
-    msg.ack();
-  }
-});
-```
+Use [KV](../../guide/kv.md), [object storage](../../guide/storage.md), and [AI](../../guide/ai.md) from server-side code with the same imports as a Void app. Add [cron jobs](../../guide/jobs.md) in `crons/` and [queue consumers](../../guide/queues.md) in `queues/`.
 
 ### Environment Variables
 
-Declare environment variables in `env.ts`, then read them with `import { env } from "void/env"`. Void supplies types, checks values during build and deploy, and stops the build if client code references a server-only key. See [Environment Variables](../../guide/env-vars.md).
+Declare variables in `env.ts` and read them with `import { env } from "void/env"`. See [Environment Variables](../../guide/env-vars.md) for local values, production secrets, and public `VITE_*` values.
 
 ## Accessing Bindings Directly