void 1.1.11 → 1.2.0

package/docs/reference/api/deploy.md

@@ -1,6 +1,6 @@
 # Deployment artifacts
 
-Use `void/deploy` from Node.js to prepare a built Void app for a managed platform deployment without platform credentials.
+Use `void/deploy` from Node.js to prepare a built Void app, SPA, or static site for a managed platform deployment without platform credentials.
 
 Build the app in managed mode inside its isolated environment:
 
@@ -16,8 +16,40 @@ import { prepareDeployArtifact } from 'void/deploy';
 const { artifact, assets } = await prepareDeployArtifact('/path/to/app');
 ```
 
-`artifact` contains the deployment manifest, content-addressed asset metadata, and base64 Worker modules. `assets` maps asset URL paths to base64 bytes. Keep this result immutable while requesting [publish approval](/guide/platform/administration/connected-apps).
+`artifact` contains the deployment manifest, content-addressed asset metadata, and base64 Worker modules when the app needs a Worker. SPAs and static sites contain only assets, using the same app detection, output directory and routing configuration as `void deploy`. `assets` maps asset URL paths to base64 bytes. Keep this result immutable while requesting [publish approval](/guide/platform/administration/connected-apps).
 
-Preparation packages existing build output; it does not build, contact a platform, provision resources, or deploy. It supports Void Cloudflare Worker builds. Node targets, static output, remote data, deploy-time prerendering, Sandbox, and Live resources require the normal `void deploy` workflow instead.
+Preparation packages existing build output; it does not build, contact a platform, provision resources, or deploy. It supports Void Cloudflare Worker builds, SPAs, and static sites. Node targets, Pages `output: 'static'`, remote data, deploy-time prerendering, Sandbox, and Live resources require the normal `void deploy` workflow instead.
 
 Run preparation inside the same isolated environment as the app build. App configuration and build plugins execute project code; keep platform credentials on the publishing server.
+
+## Cloudflare Build Output
+
+::: warning Experimental
+`prepareCfBuildOutput` follows Cloudflare's draft Build Output format. Its options and the prepared directory can change between Void releases.
+:::
+
+Use `prepareCfBuildOutput` to convert an existing Cloudflare Worker build into a disposable Cloudflare Build Output directory:
+
+```ts
+import { prepareCfBuildOutput } from 'void/deploy';
+
+const prepared = await prepareCfBuildOutput('/path/to/app/dist/server', { mode: 'staging' });
+if (!prepared) {
+  throw new Error('The Worker build could not be prepared.');
+}
+
+try {
+  // Inspect or pass prepared.directory to your Cloudflare publication workflow.
+} finally {
+  await prepared.dispose();
+}
+```
+
+Pass the Worker output directory that contains a generated `wrangler.json`, such as `dist/ssr`, `dist/rsc`, or `dist/server`. When Cloudflare's build tooling built the app, pass the project root that contains its native Build Output at `.cloudflare/output/v0` instead. Preparation copies modules and assets without changing that input. Native output keeps its module types, auxiliary Workers, Container declarations, and build metadata. Preparation does not provision resources, upload a Worker, or activate a deployment. Container images built from a local Dockerfile exist only in the Docker environment that built them, so publish from that environment.
+
+| Option      | Description                                                                                                                                          |
+| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accountId` | Cloudflare account the build must target. A different account in the build returns `null`. When omitted, the build's account is kept or left unset.  |
+| `mode`      | Vite build mode. Native output keeps the mode it was built with, and a different value returns `null`. For other output it defaults to `production`. |
+
+The result contains `directory`, an optional `assetsDirectory` pointing to the input assets, and an asynchronous `dispose()` method. Always dispose the result after use. Unsupported build configuration returns `null`. A directory without a Worker build, a missing or invalid Worker module, or an asset symlink outside the asset directory throws an error.

package/docs/reference/api/env.md

@@ -45,6 +45,6 @@ Non-client keys are server values and use remote secret storage in production. `
 /// <reference types="void/env" />
 ```
 
-Declares the `Cloudflare.Env` namespace with `DB`, `KV`, `STORAGE`, `AI`, and `SANDBOX` binding types.
+Declares the `Cloudflare.Env` namespace with `DB`, `KV`, `STORAGE`, `AI`, `SANDBOX`, and `ASSETS` binding types.
 
 For handler context variables such as `c.set()` and `c.get()`, augment [`CloudContextVariables`](./types.md#cloudcontextvariables). This is separate from `Cloudflare.Env`, which types worker bindings. Framework adapters such as `@void/vue`, `@void/react`, and `@void/svelte` also augment `CloudContextVariables` to add the `shared` key used by `useShared()`.

package/docs/reference/api/rewrites.md

@@ -10,7 +10,7 @@ URL rewrites re-dispatch a request at a different internal path without changing
 
 Re-dispatches the current request at `destination` and returns the resulting `Response`. The browser URL does not change — this is a server-side hop. If `destination` has no query string, the original request query is preserved. If `destination` includes a query string, it replaces the original query. `destination` must start with `/`; known generated routes autocomplete via [`RewriteDestination`](#rewritedestination), while arbitrary strings remain accepted for dynamic paths.
 
-`c.redirect()` also preserves request query params for internal destinations, but it merges rather than replaces: destination params win on collision, and request-only params are appended.
+`c.redirect()` also preserves request query params for internal destinations, but it merges rather than replaces: destination params win on collision, and request-only params are appended. On a request to a [named action](../../guide/pages-routing/actions-and-forms.md#named-actions), the action key (`?delete` in `POST /users/42?delete`) is not carried over, whether the action or middleware redirects. A redirect after which the browser sends the same request again keeps it: `307` and `308`, and `301` or `302` after a `PUT`, `PATCH` or `DELETE`.
 
 ```ts
 import { defineHandler } from 'void';

package/docs/reference/api/types.md

@@ -24,6 +24,7 @@ interface CloudEnv extends Env {
     STORAGE: R2Bucket;
     AI: Ai;
     SANDBOX: DurableObjectNamespace<import('void/sandbox').VoidPlatformSandbox>;
+    ASSETS: { fetch(request: Request): Promise<Response> };
     [key: string]: unknown;
   };
   Variables: CloudContextVariables;

package/docs/reference/cli/database.md

@@ -89,6 +89,21 @@ By default, targets the local database. Pass `--remote` to open Studio against t
 - **Direct Cloudflare PostgreSQL and MySQL projects**: use `DATABASE_URL` from the current shell.
 - **D1 projects**: remote Studio is not available. Use `void db execute --remote` to query your deployed D1 database.
 
+## `void db restore` {#void-db-restore}
+
+```
+void db restore --bookmark <bookmark> [--platform cloudflare] [--yes]
+void db restore --timestamp <iso-time> [--platform cloudflare] [--yes]
+```
+
+Restore the deployed D1 database of a direct Cloudflare deploy with D1 [Time Travel](https://developers.cloudflare.com/d1/reference/time-travel/). Before `void deploy --platform cloudflare` applies migrations, it prints the `--bookmark` that undoes them. `--timestamp` restores the state at an ISO 8601 time with `Z` or an offset instead, such as `2026-10-16T09:30:00Z`, with at most millisecond precision. Time Travel keeps 7 days of history on Workers Free and 30 days on Workers Paid. An older bookmark or time can no longer be restored: Cloudflare rejects it and the database stays unchanged. To undo an older migration, write a new migration that reverses it.
+
+If the project's saved destination is not Cloudflare and you deployed once with `void deploy --platform cloudflare`, pass `--platform cloudflare`; deploy prints the command with it.
+
+Restoring replaces the whole database and discards every write made after that point. Void names the database and asks before it restores. Pass `--yes` to skip the prompt in scripts and CI; without a terminal, the command stops unless `--yes` is set. Afterwards Void prints the `void db restore` command that undoes the restore.
+
+A restore also rewinds the record of applied migrations. Void lists the migration files the database no longer has applied; the next deploy applies them, so fix or remove the one that caused the problem first. Restoring does not change the deployed code: use [`void project rollback`](./project.md#void-project-rollback-deployid) if the live version needs the newer schema. After a one-off Cloudflare deploy, pass `--platform cloudflare` to `void project rollback` and `void deploy` as well.
+
 ## `void db rename-migrations` {#void-db-rename-migrations}
 
 Rename existing migrations from the old numeric prefix format (`0001_name.sql`) to timestamp-based format (`20260410161500_name.sql`). Updates local tracking table and remote records if logged in with a linked project. A project that deploys to Void must be linked first with `void project link`; otherwise the command stops without changes.

package/docs/reference/cli/platform-installation.md

@@ -24,6 +24,7 @@ void platform install [options] [--yes]
 | `--zone <domain>`                         | Cloudflare zone containing the application domain                                    |
 | `--dedicated-zone`                        | Add zone-wide catch-all routes; valid only when the app domain is the whole zone     |
 | `--no-dedicated-zone`                     | Skip zone-wide application catch-all routes                                          |
+| `--custom-domains`                        | Let projects add their own domains; needs a dedicated zone                           |
 | `--control-plane-domain <domain>`         | Optional API custom hostname; defaults to `workers.dev`                              |
 | `--no-control-plane-domain`               | Use the default `workers.dev` API hostname                                           |
 | `--dashboard-url <origin>`                | HTTPS origin of an optional dashboard deployed separately                            |
@@ -100,9 +101,9 @@ Use these commands to recover, update, pause, or remove an installation:
 
 ```sh
 void platform discover [--account <id>] [--installation <id-or-name>]
-void platform upgrade [id] [--runtime <path>] [--dashboard-url <origin>] [--plan] [--yes]
+void platform upgrade [id] [--runtime <path>] [--dashboard-url <origin>] [--custom-domains] [--plan] [--yes]
 void platform rollback [id] --runtime <earlier-path> [--from-runtime <current-path>] [--plan] [--yes]
-void platform repair [id] [--runtime <path>] [--dashboard-url <origin>] [--auth-config <path>] [--plan] [--yes]
+void platform repair [id] [--runtime <path>] [--dashboard-url <origin>] [--custom-domains] [--auth-config <path>] [--plan] [--yes]
 void platform disable [id] [--plan] [--yes]
 void platform enable [id] [--runtime <path>] [--plan] [--yes]
 void platform uninstall [id] [--plan] [--purge-data | --purge-resources] [--yes]
@@ -137,6 +138,8 @@ After discovery on another machine, set `VOID_PLATFORM_DATABASE_URL`. See [Manag
 
 Repair and upgrade preserve disabled state. New, resumed, and previously disabled installations block user traffic until all target Workers pass verification; the installer's health probes can still run. Routes and custom domains remain attached.
 
+If a platform Worker was changed outside Void, or has an active version without a Void deployment record, a command that deploys the platform Workers stops before it changes a platform Worker or pauses traffic, unless you agree in a terminal to replace the changes. See [Platform Workers changed outside Void](../../guide/platform/installation/maintenance.md#workers-changed-outside-void).
+
 `--runtime` selects a custom platform build. Relative paths resolve from your current directory. Void verifies the build before making changes; see [Platform Development](../../guide/platform/development/runtime.md#deploying-your-runtime) for creating one.
 
 Without `--runtime`, the CLI uses its packaged platform version.

package/docs/reference/cli/project.md

@@ -169,7 +169,7 @@ void project requests --range 24h
 ## `void project rollback [deployId]` {#void-project-rollback-deployid}
 
 ```
-void project rollback [deployId]
+void project rollback [deployId] [--platform cloudflare]
 ```
 
 Roll back to a previous deployment or Worker Version.
@@ -179,7 +179,9 @@ Roll back to a previous deployment or Worker Version.
 
 On a Void platform, you can select a retained deployment. On Cloudflare, use a complete Worker Version ID or an unambiguous prefix. Void activates that version at 100%. When both versions have complete trigger snapshots, it also restores the selected version's schedules, queues, workflows, routes, and custom domains. Otherwise, rollback keeps the current triggers and restores the code, including versions originally deployed outside Void.
 
-Rollback doesn't reverse database migrations. If older code may run against a newer schema, or migration metadata is missing, Void explains the risk and asks for confirmation.
+If the project's saved destination is not Cloudflare and you deployed once with `void deploy --platform cloudflare`, pass `--platform cloudflare` to roll back that Worker.
+
+Rollback doesn't reverse database migrations. If older code may run against a newer schema, or migration metadata is missing, Void explains the risk and asks for confirmation. On Cloudflare, undo D1 migrations with [`void db restore`](./database.md#void-db-restore) and the restore point that deploy printed before it applied them, within 7 days on Workers Free or 30 days on Workers Paid.
 
 ## `void project cancel [deployId]` {#void-project-cancel-deployid}
 

package/docs/reference/cli/setup.md

@@ -29,10 +29,27 @@ Resources recorded in `void.lock.json` without a matching definition appear sepa
 
 ```sh
 void init [--tsconfig] [--github] [--git | --no-git]
+          [--toolchain <name>] [--framework <name>] [--starter <name>] [--deploy <target>]
 ```
 
 Set up a new or existing Void project. In an empty directory, choose Vite+ or Vite, a framework, and a D1, PostgreSQL, MySQL, or Static Pages starter.
 
+To scaffold without prompts, for example from a script or a coding agent, pass the choices as flags. Without an interactive terminal, init stops and names the flag it needs instead of prompting.
+
+| Flag          | Values                                    |
+| ------------- | ----------------------------------------- |
+| `--toolchain` | `vite-plus`, `vite`                       |
+| `--framework` | `react`, `vue`, `svelte`, `solid`         |
+| `--starter`   | `sqlite`, `postgresql`, `mysql`, `static` |
+| `--deploy`    | `cloudflare`, `void`, `none`              |
+
+```sh
+void init --toolchain vite-plus --framework react --starter sqlite --deploy none
+npm create void@latest my-app -- --toolchain vite-plus --framework react --starter sqlite --deploy none
+```
+
+Cloudflare and Void platform setup still sign in interactively. Without a terminal, choose `--deploy none` and run `void connect` later.
+
 Vite+ projects install dependencies through `vp install`; no global Vite+ installation is required. Void preserves existing package-manager versions and lockfiles. New Vite+ projects without a package-manager configuration use pnpm without pinning a version.
 
 In an existing app, Void adds missing dependencies and scripts and updates the Vite config. If it cannot edit your config, it prints the snippet to add.

package/docs/reference/cli.md

@@ -47,6 +47,7 @@ Use this page as a command reference. If you are setting up a project for the fi
 | `void db seed`                    | Reset + seed local database                                                   |
 | `void db execute <sql>`           | Run SQL against the database (--remote for deployed)                          |
 | `void db studio`                  | Open Drizzle Studio (--remote for a deployed external database)               |
+| `void db restore --bookmark <b>`  | Restore the deployed D1 database to a restore point (direct Cloudflare)       |
 | `void secret put <name=value>`    | Set a production secret                                                       |
 | `void secret list`                | List production secrets                                                       |
 | `void secret sync <file>`         | Bulk upload secrets from dotenv file                                          |

package/docs/reference/config.md

@@ -141,6 +141,19 @@ Database backend. Omit for D1/SQLite (default). Set to `"pg"` or `"mysql"` for a
 | `"pg"`      | PostgreSQL via Hyperdrive; bring your own database      |
 | `"mysql"`   | MySQL via Hyperdrive; bring your own database           |
 
+Use an object to also set how Drizzle names columns declared without a name:
+
+```json
+{
+  "database": { "dialect": "pg", "casing": "snake_case" }
+}
+```
+
+| Key       | Values                                  | Description                                                                                                                                                                         |
+| --------- | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dialect` | `"sqlite"` (default), `"pg"`, `"mysql"` | Database backend. `"sqlite"` is D1                                                                                                                                                  |
+| `casing`  | `"snake_case"`, `"camelCase"`           | [Drizzle casing](https://orm.drizzle.team/docs/sql-schema-declaration#camel-and-snake-casing) for `void/db` queries and `void db` commands. Omit to use each key as its column name |
+
 When using an external database:
 
 - Add `DATABASE_URL` to `.env` for local development
@@ -512,7 +525,7 @@ Each binding accepts `true` (use default name), `false` (disable), or a string (
 
 Custom binding names work with `void/db`, `void/kv`, and `void/storage` during development and deployment. Custom AI names also work with `void/ai` on direct Cloudflare deploys; managed Workers AI uses the platform's proxy.
 
-`email` is a boolean feature switch. Set it to `true` to enable [email](../guide/email.md) and the `void dev` inbox without an import from `void/email`, or `false` to disable them. On a Void platform, sending uses the platform proxy. Direct Cloudflare setup records a `SEND_EMAIL` binding in `void.lock.json`; see [`email.from`](#email).
+`email` is a boolean feature switch. Set it to `true` to enable [email](../guide/email.md) and the local email inbox without an import from `void/email`, or `false` to disable them. On a Void platform, sending uses the platform proxy. Direct Cloudflare setup records a `SEND_EMAIL` binding in `void.lock.json`; see [`email.from`](#email).
 
 #### `inference.build`
 

package/docs/reference/resource-inference.md

@@ -22,6 +22,10 @@ Void automatically detects which Cloudflare resources your project uses by scann
 
 Auth detection also triggers when importing the `auth` specifier from `void/client` or a framework-specific client subpath such as `void/client/react` (but not when importing only `fetch`).
 
+Static bracket access such as `c.env['KV']` and destructured properties such as
+`const { DB, KV: cache } = c.env` are also detected. For keys chosen at runtime,
+use [explicit binding overrides](#explicit-binding-overrides).
+
 Durable state is inferred from files in `durable-objects/`. For example, `durable-objects/shopping-cart.ts` creates the `SHOPPING_CART` binding, exports `ShoppingCartDurableObject`, and records its migration. See [Durable State](../guide/durable-state.md).
 
 ## Scanned Directories

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "void",
-  "version": "1.1.11",
+  "version": "1.2.0",
   "description": "Full-stack framework and deployment CLI for Cloudflare Workers, powered by Vite.",
   "homepage": "https://void.cloud",
   "bugs": {
@@ -37,6 +37,7 @@
     "#self/sandbox": "./dist/runtime/sandbox.mjs",
     "#self/runtime/live-server": "./dist/runtime/live-server.mjs",
     "#self/runtime/fetch": "./dist/runtime/fetch.mjs",
+    "#self/runtime/fetch-server": "./dist/runtime/fetch-server.mjs",
     "#self/runtime/fetch-stream": "./dist/runtime/fetch-stream.mjs",
     "#self/runtime/route-url": "./dist/runtime/route-url.mjs",
     "#self/runtime/migration-handler": "./dist/runtime/migration-handler.mjs",
@@ -339,23 +340,23 @@
     }
   },
   "dependencies": {
-    "@cloudflare/build-output-utils": "^0.9.2",
-    "@cloudflare/codemods": "^0.5.0",
-    "@cloudflare/config": "^0.26.0",
-    "@cloudflare/sandbox": "^1.0.1",
+    "@cloudflare/build-output-utils": "^0.9.3",
+    "@cloudflare/codemods": "^0.5.1",
+    "@cloudflare/config": "^0.27.0",
+    "@cloudflare/sandbox": "^1.0.2",
     "@cloudflare/vite-plugin": "^1.64.0",
-    "@cloudflare/workers-auth": "^0.14.0",
-    "@cloudflare/workers-types": "^5.20261014.1",
-    "@napi-rs/keyring": "^2.1.1",
-    "@void/deploy-cloudflare": "1.1.11",
-    "@void/deploy-core": "1.1.11",
-    "@void/edge": "1.1.11",
-    "@void/isr": "1.1.11",
-    "@void/platform": "1.1.11",
-    "better-auth": "^1.7.7",
+    "@cloudflare/workers-auth": "^0.14.1",
+    "@cloudflare/workers-types": "^5.20261019.1",
+    "@napi-rs/keyring": "^2.1.2",
+    "@void/deploy-cloudflare": "1.2.0",
+    "@void/deploy-core": "1.2.0",
+    "@void/edge": "1.2.0",
+    "@void/isr": "1.2.0",
+    "@void/platform": "1.2.0",
+    "better-auth": "^1.7.11",
     "better-sqlite3": "^13.0.3",
     "blake3-jit": "^1.1.0",
-    "cf": "^1.0.0-beta.17",
+    "cf": ">=1.0.0-beta.18 <1.0.0-beta.19",
     "drizzle-arktype": "^0.1.3",
     "drizzle-kit": "^0.31.11",
     "drizzle-orm": "^0.45.4",
@@ -367,22 +368,22 @@
     "jiti": "^2.7.0",
     "jsonc-parser": "^3.3.1",
     "mime": "^4.1.1",
-    "miniflare": "5.20261012.0-beta",
+    "miniflare": "^5.20261012.1-beta",
     "minimatch": "^10.2.6",
     "mysql2": "^3.24.6",
     "pg": "^8.23.1",
-    "postal-mime": "^4.0.5",
+    "postal-mime": "^4.0.11",
     "proper-lockfile": "^4.1.2",
     "terminal-link": "^5.0.0",
     "yaml": "^2.9.1"
   },
   "devDependencies": {
-    "@electric-sql/pglite": "0.5.9",
+    "@electric-sql/pglite": "0.5.10",
     "@types/better-sqlite3": "^9.6.0",
     "@types/node": "^26.6.5",
     "@types/pg": "^8.23.1",
     "@types/proper-lockfile": "^4.1.4",
-    "@voidzero-dev/vite-plus-prompts": "1.2.0",
+    "@voidzero-dev/vite-plus-prompts": "1.3.0",
     "arktype": "^2.2.8",
     "ci-info": "^4.4.0",
     "estree-walker": "^3.0.3",
@@ -395,12 +396,12 @@
     "tinyglobby": "^0.2.17",
     "typescript": "7.0.2",
     "valibot": "^1.5.0",
-    "vite": "npm:@voidzero-dev/vite-plus-core@1.2.0",
-    "vite-plus": "1.2.0",
+    "vite": "npm:@voidzero-dev/vite-plus-core@1.3.0",
+    "vite-plus": "1.3.0",
     "zod": "^4.6.7"
   },
   "peerDependencies": {
-    "@void/md": "1.1.11",
+    "@void/md": "1.2.0",
     "arktype": ">=2.0.0",
     "valibot": ">=1.0.0-beta.7",
     "vite": "^8.0.0",

package/sandbox.Dockerfile

@@ -1,4 +1,4 @@
 FROM node:26.10.0-trixie-slim
-COPY --from=docker.io/cloudflare/sandbox:1.0.1 /usr/local/bin/sandbox-shim /usr/local/bin/sandbox-shim
+COPY --from=docker.io/cloudflare/sandbox:1.0.2 /usr/local/bin/sandbox-shim /usr/local/bin/sandbox-shim
 WORKDIR /workspace
 CMD ["sleep", "infinity"]

package/schema.json

@@ -392,9 +392,29 @@
       "additionalProperties": false
     },
     "database": {
-      "type": "string",
-      "enum": ["pg", "mysql"],
-      "description": "Database backend. Omit for D1 (SQLite, default). Set to \"pg\" for PostgreSQL or \"mysql\" for MySQL via Hyperdrive."
+      "description": "Database backend. Omit for D1 (SQLite, default). Set to \"pg\" for PostgreSQL or \"mysql\" for MySQL via Hyperdrive, or use an object to also set the column casing.",
+      "oneOf": [
+        {
+          "type": "string",
+          "enum": ["pg", "mysql"]
+        },
+        {
+          "type": "object",
+          "properties": {
+            "dialect": {
+              "type": "string",
+              "enum": ["sqlite", "pg", "mysql"],
+              "description": "Database backend. Defaults to \"sqlite\" (D1)."
+            },
+            "casing": {
+              "type": "string",
+              "enum": ["snake_case", "camelCase"],
+              "description": "Drizzle casing: how columns declared without a name are named in the database, for queries and generated migrations."
+            }
+          },
+          "additionalProperties": false
+        }
+      ]
     },
     "ai": {
       "type": "object",

package/dist/cf-build-output-BU3hqdHu.mjs

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

package/dist/client-DrdeJgHR.mjs

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

package/dist/deploy-CxNgEYr4.mjs

@@ -1,2 +0,0 @@
-import "./deploy-transport-nY3vLXPL.mjs";
-export { i as checkWranglerMigrationApplySet, t as parseRootWranglerConfig, r as runDeploy } from "./deploy-DsW-PrRQ.mjs";

package/dist/fetch-sAcwjzLO.mjs

@@ -1,18 +0,0 @@
-import { n as ofetch } from "./fetch-error-Dj3crt0e.mjs";
-import { t as interpolateRouteParams } from "./route-url-BjGv_KKY.mjs";
-//#region src/runtime/fetch.ts
-async function fetch(path, options) {
-	const url = interpolateRouteParams(path, options?.params);
-	return ofetch(url, {
-		method: options?.method ?? "GET",
-		body: options?.body,
-		query: options?.query,
-		headers: options?.headers,
-		signal: options?.signal,
-		baseURL: options?.baseURL,
-		retry: options?.retry,
-		timeout: options?.timeout
-	});
-}
-//#endregion
-export { fetch as t };

package/dist/gen-DsCukhuw.mjs

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

package/dist/help-DOFygYi4.mjs

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

package/dist/login-alAlxw4S.mjs

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

package/dist/migrate-D2odrAmh.mjs

@@ -1 +0,0 @@
-export { n as runMigrateCommand } from "./migrate-8rk56vV8.mjs";

package/dist/operator-cmd-D7toMPJ9.mjs

@@ -1 +0,0 @@
-export { a as runOperatorCommand } from "./operator-cmd-CA5QQyvE.mjs";

package/dist/platform-args-B_LrqEZB.mjs

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

package/dist/prepare-EVEbQ9n2.mjs

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

package/dist/resolve-project-PnhzMtY6.mjs

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

package/dist/serialize-BtQyaYoC.mjs

@@ -1,20 +0,0 @@
-//#region src/pages/script-json.ts
-const UNSAFE_SCRIPT_CHARS = /[<>&\u2028\u2029]/g;
-function escapeScriptJson(json) {
-	return json.replace(UNSAFE_SCRIPT_CHARS, (c) => {
-		return `\\u${c.charCodeAt(0).toString(16).padStart(4, "0")}`;
-	});
-}
-//#endregion
-//#region src/pages/serialize.ts
-/**
-* Escape JSON for embedding inside an inline `<script type="application/json">`
-* tag. Replaces `<`, `>`, `&`, U+2028, U+2029 with their `\uXXXX` JSON escape
-* sequences so the script tag cannot be closed early and the payload survives
-* `JSON.parse` on hydration.
-*/
-function serializePageData(pageObj) {
-	return escapeScriptJson(JSON.stringify(pageObj));
-}
-//#endregion
-export { escapeScriptJson as n, serializePageData as t };

package/dist/serialize-CfSwWfF2.d.mts

@@ -1,10 +0,0 @@
-//#region src/pages/serialize.d.ts
-/**
- * Escape JSON for embedding inside an inline `<script type="application/json">`
- * tag. Replaces `<`, `>`, `&`, U+2028, U+2029 with their `\uXXXX` JSON escape
- * sequences so the script tag cannot be closed early and the payload survives
- * `JSON.parse` on hydration.
- */
-declare function serializePageData(pageObj: unknown): string;
-//#endregion
-export { serializePageData as t };

package/dist/wrangler-DAdxHEzh.mjs

@@ -1 +0,0 @@
-export { b as readRootWranglerConfig } from "./wrangler-C9XSzrju.mjs";