void 0.10.13 → 0.20.1

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

@@ -4,7 +4,7 @@ outline: deep
 
 # Nuxt
 
-[Nuxt](https://nuxt.com/) has its own CLI and build system based on Nitro. Add `voidPlugin()` to Nuxt's Vite config for binding inference, typed DB, and migrations during development.
+Use Void with [Nuxt](https://nuxt.com/) for resource detection, typed database queries, and migrations. Nuxt keeps its own build and Cloudflare integration; Void plugs into its Vite configuration.
 
 ## Setup
 
@@ -18,10 +18,10 @@ cd my-app
 ### 2. Install dependencies
 
 ```bash
-npm install -D void wrangler
+npm install -D void
 ```
 
-The `wrangler` dependency is needed by Nuxt to create Cloudflare platform proxy during dev.
+Void includes the Cloudflare tooling used by Nuxt's platform proxy during development.
 
 ### 3. Configure `nuxt.config.ts`
 
@@ -42,7 +42,7 @@ export default defineNuxtConfig({
 });
 ```
 
-By default, Nuxt Cloudflare dev runtime and `voidPlugin()` migrations share Wrangler's local state at `.wrangler/state/v3`, so no extra persistence configuration is required.
+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 `wrangler.jsonc`
 
@@ -146,7 +146,7 @@ export default defineQueue<{ to: string; subject: string }>(async (batch) => {
 
 ### Environment Variables
 
-Void gives you a typed env layer: declare keys in `env.ts`, read them via `import { env } from "void/env"`, and get schema validation at build + deploy time plus a client-leak guard that fails the build if a server-only key reaches the browser. See the [env vars guide](../../guide/env-vars.md) for the full feature set.
+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).
 
 `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

@@ -4,11 +4,11 @@ outline: deep
 
 # Meta-Frameworks
 
-Use this section when your app already has a framework that owns routing and rendering. Void does not try to replace that layer. Instead, it plugs into the Vite build and deployment pipeline so you still get the platform features that matter on the backend.
+Keep your framework's routes and rendering, and add Void for databases, storage, jobs, and deployment. The guides in this section show how to connect each framework to Void.
 
-Void supports deploying meta-framework apps with `void deploy`. Add `voidPlugin()` to your framework's Vite config to get binding inference, typed DB generation, migration management, cron jobs, queues, and caching.
+Add `voidPlugin()` to the framework's Vite config. It detects resource usage, generates database types, manages migrations, and prepares the app for `void deploy`.
 
-Some frameworks, such as TanStack Start and React Router, compose directly with `@cloudflare/vite-plugin`, which Void already covers. Others, such as SvelteKit, Nuxt, Analog, and Astro, bring their own Cloudflare integrations. In both cases, the framework stays in charge of routing and rendering. Void handles the platform-facing pieces around it.
+TanStack Start and React Router use the Cloudflare Vite plugin provided by Void. SvelteKit, Nuxt, Analog, and Astro use their own Cloudflare adapters. The setup differs, but your framework continues to handle routing and rendering.
 
 ![void relationships with meta frameworks and deployment targets](./void-relationships.svg)
 

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

@@ -4,7 +4,7 @@ outline: deep
 
 # React Router v7
 
-[React Router v7](https://reactrouter.com/) is a Vite-based full-stack React framework. `voidPlugin()` composes directly with the React Router plugin in the Vite pipeline, so there is no separate adapter to install.
+Add `voidPlugin()` alongside the [React Router v7](https://reactrouter.com/) Vite plugin to use Void's database, storage, and deployment features. You don't need a separate Cloudflare adapter.
 
 ## Setup
 
@@ -122,9 +122,9 @@ export default defineQueue<{ to: string; subject: string }>(async (batch) => {
 
 ### Environment Variables
 
-Void gives you a typed env layer: declare keys in `env.ts`, read them via `import { env } from "void/env"`, and get schema validation at build + deploy time plus a client-leak guard that fails the build if a server-only key reaches the browser. See the [env vars guide](../../guide/env-vars.md) for the full feature set.
+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).
 
-React Router-specific caveat: because `loader()` and the component live in the same route file, the leak guard treats the module as client-reachable. Reading `env.SERVER_ONLY_KEY` inside `loader()` is safe at runtime (RR strips loaders from the client bundle), but the guard flags it as a potential leak. Move server-only secrets into a `.server.ts` companion file to silence the guard cleanly.
+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.
 
 ## Accessing Bindings Directly
 

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

@@ -4,7 +4,7 @@ outline: deep
 
 # SvelteKit
 
-[SvelteKit](https://svelte.dev/docs/kit) uses Vite internally with its own Cloudflare adapter (`@sveltejs/adapter-cloudflare`). Add `voidPlugin()` to the Vite config for binding inference, typed DB, and migrations during development.
+Use Void with [SvelteKit](https://svelte.dev/docs/kit) for resource detection, typed database queries, and migrations. SvelteKit keeps its own build and Cloudflare integration; Void plugs into its Vite configuration.
 
 ## Setup
 
@@ -61,7 +61,7 @@ SvelteKit's adapter reads bindings from `wrangler.jsonc` for local dev. `voidPlu
 }
 ```
 
-By default, SvelteKit's Cloudflare adapter, `voidPlugin()` migrations, and `void db` commands share Wrangler's local state at `.wrangler/state/v3`, so no extra `platformProxy.persist` configuration is required.
+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.
 
 ### 6. Configure `tsconfig.json`
 
@@ -168,7 +168,7 @@ export default defineQueue<{ to: string; subject: string }>(async (batch) => {
 
 ### Environment Variables
 
-Void gives you a typed env layer: declare keys in `env.ts`, read them via `import { env } from "void/env"`, and get schema validation at build + deploy time plus a client-leak guard that fails the build if a server-only key reaches the browser. `void/env` is a drop-in replacement for SvelteKit's `$env/static/*` and `$env/dynamic/*` for env-var access. See the [env vars guide](../../guide/env-vars.md) for the full feature set.
+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).
 
 ## Accessing Bindings Directly
 

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

@@ -4,7 +4,7 @@ outline: deep
 
 # TanStack Start
 
-[TanStack Start](https://tanstack.com/start/latest) is a Vite-based full-stack React framework. `voidPlugin()` composes directly with the TanStack Start plugin in the Vite pipeline, so there is no separate adapter to install.
+Add `voidPlugin()` alongside the [TanStack Start](https://tanstack.com/start/latest) Vite plugin to use Void's database, storage, and deployment features. You don't need a separate Cloudflare adapter.
 
 ## Setup
 
@@ -127,7 +127,7 @@ export default defineQueue<{ to: string; subject: string }>(async (batch) => {
 
 ### Environment Variables
 
-Void gives you a typed env layer: declare keys in `env.ts`, read them via `import { env } from "void/env"`, and get schema validation at build + deploy time plus a client-leak guard that fails the build if a server-only key reaches the browser. See the [env vars guide](../../guide/env-vars.md) for the full feature set.
+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).
 
 ## Accessing Bindings Directly
 

package/skills/void/docs/integrations/nodejs-bun-deno.md

@@ -4,7 +4,7 @@ outline: deep
 
 # Node.js, Bun, and Deno
 
-Void apps default to Cloudflare Workers, but you can target Node.js, Bun, or Deno instead by setting `target` in `void.json`. This is useful when you want to deploy to a traditional server, run in a container, or use a runtime that isn't Cloudflare.
+Set `target` in `void.json` to build for Node.js, Bun, or Deno. You can run the resulting server on your own machine, in a container, or with a hosting provider.
 
 ```json
 { "target": "node" }
@@ -66,7 +66,9 @@ deno run -A npm:vite build
 deno run -A dist/ssr/index.js
 ```
 
-The server listens on `PORT` (env variable) or `3000` by default.
+Run these commands from your app directory. The server listens on `PORT` (env variable) or `3000` by default.
+
+Pages builds load their client manifest from `dist/client/.vite/manifest.json` and serve the generated JavaScript, CSS, and public assets. Keep `dist/ssr` and `dist/client` together when deploying. Asset paths resolve from the emitted server module, so the app also works when imported or started from another working directory.
 
 ## Build Output
 
@@ -78,6 +80,7 @@ dist/
     app.js       ← Hono app with static asset middleware (default export)
     index.js     ← imports app.js and starts the HTTP server
   client/        ← static assets (pages mode only)
+    .vite/manifest.json
     assets/
       ...
 ```
@@ -123,17 +126,21 @@ Void-managed WebSocket route files (`*.ws.ts`) are still Cloudflare-only because
 
 You can still define [cron jobs](../guide/jobs.md) in `crons/` and they will compile into the bundle, but there is no built-in scheduler to invoke them. On Cloudflare, Workers Cron Triggers call the `scheduled` handler automatically. On Node.js, you'll need an external scheduler (e.g. `node-cron`, systemd timers, or your hosting platform's cron) to trigger the exported handler.
 
+### No inbound email
+
+Inbound [email handlers](../guide/email.md#inbound) in `email/` need Cloudflare Email Routing to invoke the worker's `email()` export, and the Node.js entry exposes HTTP only. An `email/` directory fails the build with guidance. Outbound `sendEmail` has no send transport on these targets either: it returns a `BINDING_MISSING` error.
+
 ### No prerendering
 
 [Prerendering](../guide/edge/prerendering.md) is a platform feature that relies on Cloudflare's edge cache and the Void deploy pipeline. It is not available for non-CF targets.
 
 ### No `void deploy`
 
-The `void deploy` CLI deploys to the Void platform on Cloudflare. For non-CF targets, build with `vite build` and deploy the `dist/` directory using your hosting provider's workflow, whether that is Docker, systemd, PM2, Fly.io, Railway, or any other Node.js host.
+`void deploy` handles Cloudflare and Void platform deployments. For Node.js, Bun, or Deno, run `vite build` and deploy `dist/` using your hosting provider's workflow.
 
 ### Ignored config fields
 
-These `void.json` fields are silently ignored (with a warning) when using a non-CF target:
+Void warns and ignores these Cloudflare-specific `void.json` fields on other targets:
 
 - `inference.bindings`: Cloudflare binding configuration
 - `remote`: remote binding proxy

package/skills/void/docs/reference/api.md

@@ -586,9 +586,34 @@ The typed client is built on [ofetch](https://github.com/unjs/ofetch) with a typ
 
 `headers` and `signal` are passed through to the underlying fetch unchanged.
 
+## Durable State
+
+Imported from `"void/durable"`. See [Durable State](../guide/durable-state.md) for the complete file convention and deployment support.
+
+### `defineDurableState(definition)`
+
+Defines a typed, persisted Durable Object state machine. The returned object must be the default export of a module under `durable-objects/`; named-export the same object for typed RPC calls elsewhere in the app.
+
+```ts
+function defineDurableState<TState, TEnv, TMethods>(definition: {
+  initialState: TState | ((env: TEnv) => TState | Promise<TState>);
+  version?: number;
+  migrations?: Array<{
+    version: number;
+    migrate(state: unknown): TState | Promise<TState>;
+  }>;
+  methods: TMethods;
+  fetch?: (context, request: Request) => Response | Promise<Response>;
+  alarm?: (context) => void | Promise<void>;
+  storageKey?: string;
+}): DurableStateApi<TMethods>;
+```
+
+`DurableStateApi` exposes `class`, `get(name)`, `get(namespace, name)`, `getById(id)`, and `getById(namespace, id)`. Stubs returned by the lookup helpers contain the definition's methods with their argument types preserved and return values wrapped in `Promise`.
+
 ## Database
 
-Imported from `"void/db"`. The `db` export is a [Drizzle ORM](https://orm.drizzle.team) instance for the configured database dialect: [Cloudflare D1](https://developers.cloudflare.com/d1/) by default, or PostgreSQL when `void.json` sets `"database": "pg"` / `"postgresql"`. See the [Database guide](../guide/database.md) for usage and the [Drizzle docs](https://orm.drizzle.team/docs/select) for the full query API.
+Imported from `"void/db"`. The `db` export is a [Drizzle ORM](https://orm.drizzle.team) instance for the configured database dialect: [Cloudflare D1](https://developers.cloudflare.com/d1/) by default, PostgreSQL with `"database": "pg"`, or MySQL with `"database": "mysql"`.
 
 ### `db`
 
@@ -605,6 +630,7 @@ When the Void plugin is active, `void/db` is served as a virtual module that aut
 
 - D1 projects resolve the `DB` binding and expose `DrizzleD1Database<Schema>`.
 - PostgreSQL projects use `DATABASE_URL` during local development and Hyperdrive's `connectionString` in production, exposing `NodePgDatabase<Schema>`.
+- MySQL projects use the same connection sources and expose `MySql2Database<Schema>`.
 
 The published npm fallback uses a lazy D1 proxy that resolves the `DB` binding at first access.
 
@@ -621,7 +647,7 @@ import { env } from 'cloudflare:workers';
 const db = createDb(env.MY_OTHER_DB);
 ```
 
-For PostgreSQL projects, pass a connection string.
+For PostgreSQL and MySQL projects, pass a connection string.
 
 ```ts
 import { createDb } from 'void/db';
@@ -637,6 +663,9 @@ function createDb(d1: D1Database): DrizzleD1Database<Schema>;
 
 // PostgreSQL
 function createDb(connectionString: string): NodePgDatabase<Schema>;
+
+// MySQL
+function createDb(connectionString: string): MySql2Database<Schema>;
 ```
 
 ### Query Operators
@@ -876,10 +905,10 @@ Register an env schema and return the typed [`env`](#env) proxy. Void auto-disco
 import { defineEnv, string, number, oneOf, url } from 'void/env';
 
 export default defineEnv({
-  STRIPE_KEY: string().secret(),
+  STRIPE_KEY: string(),
   PORT: number().default(3000),
   NODE_ENV: oneOf(['development', 'production']),
-  VITE_PUBLIC_URL: url().public(),
+  VITE_PUBLIC_URL: url(),
 });
 ```
 
@@ -895,7 +924,9 @@ const port = env.PORT;
 
 ### Schema helpers
 
-`void/env` includes Standard Schema-compatible helpers: `string()`, `number()`, `boolean()`, `url()`, `email()`, `oneOf([...])`, and `json<T>()`. Each helper supports `.optional()`, `.default(value)`, `.secret()`, and `.public()`.
+`void/env` includes Standard Schema-compatible helpers: `string()`, `number()`, `boolean()`, `url()`, `email()`, `oneOf([...])`, and `json<T>()`. Each helper supports `.optional()` and `.default(value)`.
+
+Non-client keys are server values and use remote secret storage in production. `VITE_*` keys are public build-time client values. Invalid input is redacted uniformly; storage is not selected with schema modifiers.
 
 ### Types
 
@@ -959,6 +990,8 @@ Imported from `"@void/vue"`.
 
 Vue `Link` GET `data` is merged into the rendered `href` query string. Primitive values are serialized with `String(value)`, arrays become repeated keys, `null` and `undefined` are omitted, and nested objects throw. `prefetch` and `reloadDocument` are GET-only and throw for mutation links.
 
+Vue GET navigation remounts the page so `useForm()` picks up the destination record's URL and defaults; layouts persist. Mutations and `router.refresh()` preserve page state by default. Set `preserveState` explicitly to override the default for navigation within the same record.
+
 ### `@void/react`
 
 #### `voidReact(options?)`
@@ -1153,6 +1186,7 @@ This table lists app-facing imports. Exported implementation subpaths such as `v
 | `void/client`             | `fetch`, `fetchStream`, `FetchError`, `auth`, `createAuthClient`, `AuthUser`, `AuthSession`, `AuthState`                                                                                                                                                                                                                                                                                                                                                                                                                 |
 | `void/client/{framework}` | Same as `void/client`, with framework-specific Better Auth clients for `react`, `vue`, `svelte`, and `solid`                                                                                                                                                                                                                                                                                                                                                                                                             |
 | `void/ws`                 | `defineRoom`, `defineWebSocket`, `connect`, WebSocket context and connection types                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `void/durable`            | `defineDurableState`, typed state/RPC/context/migration types                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | `void/sse`                | `eventStream`, `formatSse`, `formatSseText`, `getLastEventId`, `SseStreamClosedError`, SSE message and stream types                                                                                                                                                                                                                                                                                                                                                                                                      |
 | `void/sse/client`         | `connectEventStream`, browser `EventSource` wrapper types                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | `void/live`               | `defineLiveStream`, SSE topic fanout runtime types. Server-only.                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
@@ -1164,7 +1198,9 @@ This table lists app-facing imports. Exported implementation subpaths such as `v
 | `void/drizzle-arktype`    | Re-exports [`drizzle-arktype`](https://orm.drizzle.team/docs/arktype) for schema-derived ArkType validators for Drizzle tables                                                                                                                                                                                                                                                                                                                                                                                           |
 | `void/schema-d1`          | Re-exports [`drizzle-orm/sqlite-core`](https://orm.drizzle.team/docs/column-types/sqlite) for D1 table and column builders                                                                                                                                                                                                                                                                                                                                                                                               |
 | `void/schema-pg`          | Re-exports [`drizzle-orm/pg-core`](https://orm.drizzle.team/docs/column-types/pg) for PostgreSQL table and column builders                                                                                                                                                                                                                                                                                                                                                                                               |
-| `void/db`                 | `db` (Drizzle D1 or PostgreSQL instance for the active dialect), `createDb`, query operators (`eq`, `and`, `or`, `desc`, `like`, `inArray`, etc.)                                                                                                                                                                                                                                                                                                                                                                        |
+| `void/schema-mysql`       | Re-exports `drizzle-orm/mysql-core` for MySQL table and column builders                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `void/database-provider`  | `defineDatabaseProvider` and adapter types for `void db connect --provider`                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `void/db`                 | `db` (Drizzle D1, PostgreSQL, or MySQL instance for the active dialect), `createDb`, query operators (`eq`, `and`, `or`, `desc`, `like`, `inArray`, etc.)                                                                                                                                                                                                                                                                                                                                                                |
 | `void/seed`               | `defineSeed`, `SeedContext`, `SeedFn` for programmatic `void db seed` modules                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | `void/kv`                 | `kv`, `createKV`, typed KV client/map types                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | `void/storage`            | `storage`, `createStorage` for the inferred R2 binding or a specific `R2Bucket`                                                                                                                                                                                                                                                                                                                                                                                                                                          |