@lunora/nuxt 1.0.0-alpha.273 → 1.0.0-alpha.274

package/dist/module.json

@@ -1,5 +1,5 @@
 {
   "configKey": "lunora",
   "name": "@lunora/nuxt",
-  "version": "1.0.0-alpha.272"
+  "version": "1.0.0-alpha.273"
 }

package/dist/runtime/cloudflare.d.mts

@@ -1,3 +1,23 @@
+/**
+ * Resolve the Cloudflare per-request `env` (bindings) and `ExecutionContext`
+ * from a Nitro/H3 event, tolerating the two shapes Nitro has shipped.
+ *
+ * Legacy `event.context.cloudflare.{ env, context }` — surfaced by
+ * `nitro-cloudflare-dev` in `nuxt dev` and by older `cloudflare_module` builds,
+ * where `context` is the `ExecutionContext` (`waitUntil` / `passThroughOnException`).
+ *
+ * Newer `event.req.runtime.cloudflare.{ env, ctx }` — the Nitro runtime accessor
+ * (Nitro v2.10+ / Nuxt 4), where the `ExecutionContext` is `ctx`.
+ *
+ * Both are read defensively so the delegating handler works across the version
+ * range a scaffolded app might pin, in both dev and the deployed worker. When
+ * neither is present (no Cloudflare runtime — e.g. a Node preview), `env` is
+ * `undefined` and the caller surfaces a clear error.
+ *
+ * Typed against a structural `H3EventLike` rather than `nitropack`'s `H3Event`
+ * so this seam stays pure (no Nitro types needed) and unit-testable with a plain
+ * object — a real `H3Event` is still assignable here.
+ */
 import { ExecutionContextLike } from '@lunora/runtime';
 export type { ExecutionContextLike } from '@lunora/runtime';
 /** The `{ env, context|ctx }` payload Nitro attaches for the Cloudflare runtime. */

package/dist/runtime/cloudflare.d.ts

@@ -1,3 +1,23 @@
+/**
+ * Resolve the Cloudflare per-request `env` (bindings) and `ExecutionContext`
+ * from a Nitro/H3 event, tolerating the two shapes Nitro has shipped.
+ *
+ * Legacy `event.context.cloudflare.{ env, context }` — surfaced by
+ * `nitro-cloudflare-dev` in `nuxt dev` and by older `cloudflare_module` builds,
+ * where `context` is the `ExecutionContext` (`waitUntil` / `passThroughOnException`).
+ *
+ * Newer `event.req.runtime.cloudflare.{ env, ctx }` — the Nitro runtime accessor
+ * (Nitro v2.10+ / Nuxt 4), where the `ExecutionContext` is `ctx`.
+ *
+ * Both are read defensively so the delegating handler works across the version
+ * range a scaffolded app might pin, in both dev and the deployed worker. When
+ * neither is present (no Cloudflare runtime — e.g. a Node preview), `env` is
+ * `undefined` and the caller surfaces a clear error.
+ *
+ * Typed against a structural `H3EventLike` rather than `nitropack`'s `H3Event`
+ * so this seam stays pure (no Nitro types needed) and unit-testable with a plain
+ * object — a real `H3Event` is still assignable here.
+ */
 import { ExecutionContextLike } from '@lunora/runtime';
 export type { ExecutionContextLike } from '@lunora/runtime';
 /** The `{ env, context|ctx }` payload Nitro attaches for the Cloudflare runtime. */

package/dist/runtime/handler.d.mts

@@ -1,3 +1,20 @@
+/**
+ * The Lunora ↔ Nitro delegation seam. Given a Lunora worker (the
+ * `defineApp().build()` app or a bare `createWorker(...)` result) and the
+ * Cloudflare runtime resolved off the request event, forward the inbound
+ * `Request` — RPC (`POST /_lunora/rpc`), WebSocket upgrade (`/_lunora/ws`), and
+ * the admin plane (`/_lunora/admin/*`) — straight to `worker.fetch`.
+ *
+ * This is the single-worker composition the void.cloud Nuxt approach uses,
+ * inverted: instead of Lunora owning the worker entry, Lunora is mounted
+ * inside* Nitro as a server route, and the `ShardDO` class is re-exported to
+ * the Cloudflare worker entrypoint via the project's root `worker.ts` wrapper.
+ *
+ * Kept framework-neutral (a `LunoraWorkerLike` + the resolved `env`/`ctx`, not
+ * an H3 event) so it can be unit-tested with a stub worker — no Nuxt or workerd
+ * boot required. The thin H3 adapter that reads `env`/`ctx` off the event and
+ * the raw `Request`/`Response` lives in the `[...].ts` route module.
+ */
 import { ExecutionContextLike } from '@lunora/runtime';
 export { NOOP_EXECUTION_CONTEXT } from '@lunora/runtime';
 /**

package/dist/runtime/handler.d.ts

@@ -1,3 +1,20 @@
+/**
+ * The Lunora ↔ Nitro delegation seam. Given a Lunora worker (the
+ * `defineApp().build()` app or a bare `createWorker(...)` result) and the
+ * Cloudflare runtime resolved off the request event, forward the inbound
+ * `Request` — RPC (`POST /_lunora/rpc`), WebSocket upgrade (`/_lunora/ws`), and
+ * the admin plane (`/_lunora/admin/*`) — straight to `worker.fetch`.
+ *
+ * This is the single-worker composition the void.cloud Nuxt approach uses,
+ * inverted: instead of Lunora owning the worker entry, Lunora is mounted
+ * inside* Nitro as a server route, and the `ShardDO` class is re-exported to
+ * the Cloudflare worker entrypoint via the project's root `worker.ts` wrapper.
+ *
+ * Kept framework-neutral (a `LunoraWorkerLike` + the resolved `env`/`ctx`, not
+ * an H3 event) so it can be unit-tested with a stub worker — no Nuxt or workerd
+ * boot required. The thin H3 adapter that reads `env`/`ctx` off the event and
+ * the raw `Request`/`Response` lives in the `[...].ts` route module.
+ */
 import { ExecutionContextLike } from '@lunora/runtime';
 export { NOOP_EXECUTION_CONTEXT } from '@lunora/runtime';
 /**

package/dist/runtime/server/lunora.d.mts

@@ -1,3 +1,24 @@
+/**
+ * Nitro server handler mounted at `/_lunora/**` by the `@lunora/nuxt` module
+ * (`addServerHandler`). It is the single-worker seam: every Lunora RPC,
+ * WebSocket upgrade, and admin request is forwarded to the project's Lunora
+ * worker, which runs *inside* the same Nitro/Cloudflare worker the rest of the
+ * Nuxt app deploys as.
+ *
+ * The worker instance is the project's composed app, imported through the
+ * `#lunora/app` virtual the module registers (it points at the app entry — by
+ * default `~/lunora/server`, where `defineApp().build()` lives and re-exports
+ * `ShardDO`). The same `ShardDO` is re-exported to the Cloudflare worker
+ * entrypoint via the project's root `worker.ts` wrapper (`wrangler.jsonc`'s
+ * `main`), so one deploy carries both the SSR handler and the Durable Object class.
+ *
+ * This file is only ever bundled by Nitro; `h3`'s `defineEventHandler` is its
+ * sole framework entry. We use a namespace import so the seam spans the h3
+ * v1 → v2 break: v1 exposes `toWebRequest(event)`, while the v2 web-standards
+ * rewrite removed it and carries the web `Request` directly as `event.req`. A
+ * static `import { toWebRequest }` would throw at module-eval under v2 (missing
+ * named export), so `resolveWebRequest` feature-detects it at runtime instead.
+ */
 import { QueryObject } from 'ufo';
 import { Hooks } from 'crossws';
 import { IncomingMessage, ServerResponse } from 'node:http';

package/dist/runtime/server/lunora.d.ts

@@ -1,3 +1,24 @@
+/**
+ * Nitro server handler mounted at `/_lunora/**` by the `@lunora/nuxt` module
+ * (`addServerHandler`). It is the single-worker seam: every Lunora RPC,
+ * WebSocket upgrade, and admin request is forwarded to the project's Lunora
+ * worker, which runs *inside* the same Nitro/Cloudflare worker the rest of the
+ * Nuxt app deploys as.
+ *
+ * The worker instance is the project's composed app, imported through the
+ * `#lunora/app` virtual the module registers (it points at the app entry — by
+ * default `~/lunora/server`, where `defineApp().build()` lives and re-exports
+ * `ShardDO`). The same `ShardDO` is re-exported to the Cloudflare worker
+ * entrypoint via the project's root `worker.ts` wrapper (`wrangler.jsonc`'s
+ * `main`), so one deploy carries both the SSR handler and the Durable Object class.
+ *
+ * This file is only ever bundled by Nitro; `h3`'s `defineEventHandler` is its
+ * sole framework entry. We use a namespace import so the seam spans the h3
+ * v1 → v2 break: v1 exposes `toWebRequest(event)`, while the v2 web-standards
+ * rewrite removed it and carries the web `Request` directly as `event.req`. A
+ * static `import { toWebRequest }` would throw at module-eval under v2 (missing
+ * named export), so `resolveWebRequest` feature-detects it at runtime instead.
+ */
 import { QueryObject } from 'ufo';
 import { Hooks } from 'crossws';
 import { IncomingMessage, ServerResponse } from 'node:http';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lunora/nuxt",
-  "version": "1.0.0-alpha.273",
+  "version": "1.0.0-alpha.274",
   "description": "Nuxt module for Lunora — single-worker composition (mounts /_lunora/* into Nitro) plus reactive-loader server helpers",
   "keywords": [
     "cloudflare",
@@ -51,8 +51,8 @@
     "access": "public"
   },
   "dependencies": {
-    "@lunora/client": "1.0.0-alpha.253",
-    "@lunora/runtime": "1.0.0-alpha.242",
+    "@lunora/client": "1.0.0-alpha.254",
+    "@lunora/runtime": "1.0.0-alpha.243",
     "@nuxt/kit": "^4.5.2"
   },
   "peerDependencies": {