void 0.10.12 → 0.20.0

package/dist/index.d.mts

@@ -1,44 +1,71 @@
-import { n as HeadDescriptor } from "./head-nmvOgFjd.mjs";
-import { r as AuthUser } from "./auth-qgMlYp7Z.mjs";
-import { C as defer, E as ValidatorSlots, S as InferProps, T as HandlerInput, _ as defineQueue, a as CloudEnv, b as Deferred, c as QueueRetryOptions, d as TypedQueueHandler, f as VoidAssetRewriteError, g as defineMiddleware, h as defineHead, i as CloudContextVariables, l as RenderAssetTags, m as defineHandler, o as QueueBatch, p as basicAuth, r as CloudContext, s as QueueMessage, t as BasicAuthOptions, u as TypedHandler, v as defineRender, x as DeferredState, y as defineScheduled } from "./handler-Cjh8uM3Y.mjs";
+import { n as HeadDescriptor } from "./head-Do8P4puT.mjs";
+import { r as AuthUser } from "./auth-DkcFflXV.mjs";
+import { C as defer, E as ValidatorSlots, S as InferProps, T as HandlerInput, _ as defineQueue, a as CloudEnv, b as Deferred, c as QueueRetryOptions, d as TypedQueueHandler, f as VoidAssetRewriteError, g as defineMiddleware, h as defineHead, i as CloudContextVariables, l as RenderAssetTags, m as defineHandler, o as QueueBatch, p as basicAuth, r as CloudContext, s as QueueMessage, t as BasicAuthOptions, u as TypedHandler, v as defineRender, x as DeferredState, y as defineScheduled } from "./handler-D1hLsObx.mjs";
 import { QueueMap } from "./runtime/queues.mjs";
 import { PluginConfig } from "@cloudflare/vite-plugin";
 import { Plugin } from "vite";
-
+//#region src/router/parse-filename.d.ts
+type RouteEnvironment = "dev" | "prod";
+//#endregion
 //#region src/index.d.ts
 /**
-* Decide whether to inject a Workers AI binding into the built wrangler config.
-*
-* Build-only: dev/miniflare has no local Workers AI, so serve must never bind
-* `env.AI` (dev uses the P2 `__VOID_TOKEN` proxy path instead).
-*
-* `!resolvedAi` is load-bearing: mergeBindings' return is defu-merged over the
-* resolved root-wrangler config and wins, so skipping when the user already
-* declared an `ai` binding avoids clobbering theirs. `!resultAi` is harmless
-* defense-in-depth (nothing else in mergeBindings sets `result.ai`).
-*/
-declare function shouldBindWorkersAi(command: string, needsAI: boolean, resolvedAi: unknown, resultAi: unknown): boolean;
+ * Decide whether to inject a Workers AI binding into the built wrangler config.
+ *
+ * Builds use the production binding. During dev, a project explicitly saved
+ * with the direct Cloudflare destination uses Cloudflare's remote binding;
+ * managed and unsaved projects keep using the Void HTTPS proxy.
+ *
+ * `!resolvedAi` is load-bearing: mergeBindings' return is defu-merged over the
+ * resolved root-wrangler config and wins, so skipping when the user already
+ * declared an `ai` binding avoids clobbering theirs. `!resultAi` is harmless
+ * defense-in-depth (nothing else in mergeBindings sets `result.ai`).
+ */
+export declare function shouldBindWorkersAi(command: string, needsAI: boolean, resolvedAi: unknown, resultAi: unknown, directCloudflareDev?: boolean): boolean;
+/**
+ * Decide whether to inject the `void dev` email-inbox loopback var.
+ *
+ * The dev inbox buffer lives in the Vite dev server's Node process;
+ * `sendEmail` runs in workerd and reaches it by fetching the inbox capture
+ * endpoint through the worker's assets binding, which
+ * `@cloudflare/vite-plugin` wires straight into the dev server's middleware
+ * stack. The var carries that binding's NAME (`ASSETS` for a Void app, or
+ * whatever a Class A framework's own wrangler config declares) and its
+ * presence is what arms the dev path at runtime — so it must never reach a
+ * production build's `wrangler.json`, exactly like the `__VOID_TOKEN`
+ * credential gate.
+ *
+ * Gated on `routeEnvironment`, not on `command`: `vite preview` also reports
+ * `command: 'serve'`, but it runs the BUILT worker whose assets binding is a
+ * real asset directory rather than a dev-server loopback. `routeEnvironment`
+ * is the existing `command === 'serve' && !isPreview` distinction.
+ *
+ * Without an assets binding there is no loopback, so injecting the var would
+ * only arm a path that must then fail; gate on it instead.
+ */
+export declare function shouldInjectEmailDevInboxVar(routeEnvironment: RouteEnvironment, needsEmail: boolean | undefined, assetsBinding: string | undefined): boolean;
+/** Resolve the runtime Workers AI binding, preserving a root Wrangler declaration. */
+export declare function resolveWorkersAiBindingName(resolvedAi: unknown, configuredName?: string): string;
 /**
-* Void plugin — the main entry point.
-*
-* Composes:
-* 1. Routing plugin (file-based routing from routes/ and middleware/)
-* 2. Migration plugin (auto-apply .sql migrations on dev startup)
-* 3. @cloudflare/vite-plugin (workerd runtime, HMR, builds)
-*
-* Binding inference runs synchronously here so results are available
-* before the Cloudflare plugin initializes.
-*
-* If the user has a `wrangler.jsonc` / `wrangler.json` in their project root,
-* the Cloudflare plugin reads it and provides the resolved config to our
-* config function. Bindings already defined there (with real IDs for
-* production deployment) are preserved — we only add inferred bindings
-* that are missing. This allows `vite build && wrangler deploy` to work
-* for deploying directly to Cloudflare without the Void platform.
-*/
-declare function voidPlugin(options?: {
+ * Void plugin — the main entry point.
+ *
+ * Composes:
+ * 1. Routing plugin (file-based routing from routes/ and middleware/)
+ * 2. Migration plugin (auto-apply .sql migrations on dev startup)
+ * 3. @cloudflare/vite-plugin (workerd runtime, HMR, builds)
+ *
+ * Binding inference runs synchronously here so results are available
+ * before the Cloudflare plugin initializes.
+ *
+ * If the user has a `wrangler.jsonc` / `wrangler.json` in their project root,
+ * the Cloudflare plugin reads it and provides the resolved config to our
+ * config function. Bindings already defined there (with real IDs for
+ * production deployment) are preserved — we only add inferred bindings
+ * that are missing. This allows `vite build && wrangler deploy` to work
+ * for deploying directly to Cloudflare without the Void platform.
+ */
+export declare function voidPlugin(options?: {
   persistTo?: string;
   auxiliaryWorkers?: PluginConfig["auxiliaryWorkers"];
 }): Array<Plugin>;
 //#endregion
-export { type AuthUser, type BasicAuthOptions, type CloudContext, type CloudContextVariables, type CloudEnv, type Deferred, type DeferredState, type HandlerInput, type HeadDescriptor, type InferProps, type QueueBatch, type QueueMap, type QueueMessage, type QueueRetryOptions, type RenderAssetTags, type TypedHandler, type TypedQueueHandler, type ValidatorSlots, VoidAssetRewriteError, basicAuth, defer, defineHandler, defineHead, defineMiddleware, defineQueue, defineRender, defineScheduled, shouldBindWorkersAi, voidPlugin };
+export { type AuthUser, type BasicAuthOptions, type CloudContext, type CloudContextVariables, type CloudEnv, type Deferred, type DeferredState, type HandlerInput, type HeadDescriptor, type InferProps, type QueueBatch, type QueueMap, type QueueMessage, type QueueRetryOptions, type RenderAssetTags, type TypedHandler, type TypedQueueHandler, type ValidatorSlots, VoidAssetRewriteError, basicAuth, defer, defineHandler, defineHead, defineMiddleware, defineQueue, defineRender, defineScheduled };