@nimbus-sh/worker 0.2.3 → 0.4.0

package/dist/session/ctx-exports.d.ts

@@ -1,16 +0,0 @@
-/**
- * ctx-exports.ts — leaf module holding the ctx.exports reference.
- *
- * Isolated from src/index.ts so helpers (notably src/loaders/loader-pool.ts)
- * can read `ctx.exports` without transitively importing the Durable Object
- * classes. Keeping this a leaf (no imports) lets the pool be unit-tested in
- * a plain Node/Bun process.
- *
- * The fetch handler in src/index.ts calls `setCtxExports(ctx.exports)` on
- * the first request; callers like NimbusLoaderPool read via `getCtxExports()`.
- * If the pool is constructed before the first fetch (unlikely) it just gets
- * null — the caller decides how to degrade.
- */
-export declare function setCtxExports(value: any): void;
-export declare function getCtxExports(): any;
-//# sourceMappingURL=ctx-exports.d.ts.map

package/dist/session/ctx-exports.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ctx-exports.d.ts","sourceRoot":"","sources":["../../src/session/ctx-exports.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAIH,wBAAgB,aAAa,CAAC,KAAK,EAAE,GAAG,GAAG,IAAI,CAG9C;AAED,wBAAgB,aAAa,IAAI,GAAG,CAEnC"}

package/dist/session/ctx-exports.js

@@ -1,22 +0,0 @@
-/**
- * ctx-exports.ts — leaf module holding the ctx.exports reference.
- *
- * Isolated from src/index.ts so helpers (notably src/loaders/loader-pool.ts)
- * can read `ctx.exports` without transitively importing the Durable Object
- * classes. Keeping this a leaf (no imports) lets the pool be unit-tested in
- * a plain Node/Bun process.
- *
- * The fetch handler in src/index.ts calls `setCtxExports(ctx.exports)` on
- * the first request; callers like NimbusLoaderPool read via `getCtxExports()`.
- * If the pool is constructed before the first fetch (unlikely) it just gets
- * null — the caller decides how to degrade.
- */
-let _ctxExports = null;
-export function setCtxExports(value) {
-    if (_ctxExports)
-        return; // first-write-wins, same as the prior inline impl
-    _ctxExports = value;
-}
-export function getCtxExports() {
-    return _ctxExports;
-}

package/dist/session/ws-hibernation-config.d.ts

@@ -1,64 +0,0 @@
-/**
- * ws-hibernation-config.ts — W9 (CF research §C.3 + §C.4) configuration
- * for setWebSocketAutoResponse + setHibernatableWebSocketEventTimeout.
- *
- * Why a dedicated module:
- *   - NimbusSession's constructor is already crowded; the calls have
- *     specific failure modes (workerd version dependence, optional
- *     globals) that deserve isolation.
- *   - Unit-testable in Node by passing a mock ctx — the constructor
- *     itself can't be (it pulls cloudflare:workers).
- *
- * What this does, in order:
- *   1. setWebSocketAutoResponse(WebSocketRequestResponsePair('ping','pong'))
- *      — vite HMR clients ping every 30s and idle xterm tabs ping per
- *      minute. Without auto-response, every ping wakes the actor from
- *      hibernation: ~2880 wakes/day per idle tab. After this, zero
- *      billable wakes for matched ping/pong frames. Auto-response config
- *      survives hibernation per the STOR/Durable Objects WebSocket
- *      Primer (wiki page id 1372566651).
- *   2. setHibernatableWebSocketEventTimeout(5000) — bound a single
- *      hibernation message handler. Long-running work runs in facets
- *      with their own CPU budget; the supervisor's WS handlers should
- *      enqueue then return. 5 s recommended in CF research §C.3.
- *
- * Both calls are gated on try/catch:
- *   - workerd builds before mid-2024 don't expose either method.
- *   - WebSocketRequestResponsePair is a workerd global; absent in Node.
- * Failure is reported honestly via the return value so /api/_diag/memory
- * can show whether the runtime supported the configuration.
- */
-/**
- * Recommended hibernation event timeout (ms). 5 s per CF research §C.3
- * — long enough for the heaviest non-facet WS message handler observed
- * in W5 telemetry (~120 ms p99 for a heavy autocomplete request), short
- * enough to bound a runaway handler before it pins the actor.
- */
-export declare const NIMBUS_HIBERNATION_EVENT_TIMEOUT_MS = 5000;
-/** Public ping/pong contract — clients send `ping`, receive `pong`. */
-export declare const WS_AUTO_RESPONSE_REQUEST = "ping";
-export declare const WS_AUTO_RESPONSE_RESPONSE = "pong";
-export interface WsHibernationConfigResult {
-    /** True iff `setWebSocketAutoResponse` ran without throwing. */
-    autoResponseConfigured: boolean;
-    /**
-     * The timeout (in ms) we successfully set, or null if the call wasn't
-     * available / threw. Reported separately from autoResponseConfigured
-     * so a partial-support workerd shows the partial truth.
-     */
-    timeoutSetMs: number | null;
-    /** Optional error message — human-readable, never thrown. */
-    autoResponseError?: string;
-    timeoutError?: string;
-}
-/**
- * Configure WS hibernation behaviours on a DurableObjectState. Idempotent
- * — safe to call multiple times. Returns a result that NimbusSession
- * surfaces via /api/_diag/memory under the `hib` key.
- *
- * The `ctx` parameter is structurally typed (anything with the right
- * methods works) so this module stays Node-testable. In production the
- * caller passes the real `this.ctx` from NimbusSession's constructor.
- */
-export declare function configureWsHibernation(ctx: any): WsHibernationConfigResult;
-//# sourceMappingURL=ws-hibernation-config.d.ts.map

package/dist/session/ws-hibernation-config.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ws-hibernation-config.d.ts","sourceRoot":"","sources":["../../src/session/ws-hibernation-config.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,mCAAmC,OAAO,CAAC;AAExD,uEAAuE;AACvE,eAAO,MAAM,wBAAwB,SAAS,CAAC;AAC/C,eAAO,MAAM,yBAAyB,SAAS,CAAC;AAEhD,MAAM,WAAW,yBAAyB;IACxC,gEAAgE;IAChE,sBAAsB,EAAE,OAAO,CAAC;IAChC;;;;OAIG;IACH,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;IAC5B,6DAA6D;IAC7D,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,YAAY,CAAC,EAAE,MAAM,CAAC;CACvB;AAED;;;;;;;;GAQG;AACH,wBAAgB,sBAAsB,CACpC,GAAG,EAAE,GAAG,GACP,yBAAyB,CAqC3B"}

package/dist/session/ws-hibernation-config.js

@@ -1,89 +0,0 @@
-/**
- * ws-hibernation-config.ts — W9 (CF research §C.3 + §C.4) configuration
- * for setWebSocketAutoResponse + setHibernatableWebSocketEventTimeout.
- *
- * Why a dedicated module:
- *   - NimbusSession's constructor is already crowded; the calls have
- *     specific failure modes (workerd version dependence, optional
- *     globals) that deserve isolation.
- *   - Unit-testable in Node by passing a mock ctx — the constructor
- *     itself can't be (it pulls cloudflare:workers).
- *
- * What this does, in order:
- *   1. setWebSocketAutoResponse(WebSocketRequestResponsePair('ping','pong'))
- *      — vite HMR clients ping every 30s and idle xterm tabs ping per
- *      minute. Without auto-response, every ping wakes the actor from
- *      hibernation: ~2880 wakes/day per idle tab. After this, zero
- *      billable wakes for matched ping/pong frames. Auto-response config
- *      survives hibernation per the STOR/Durable Objects WebSocket
- *      Primer (wiki page id 1372566651).
- *   2. setHibernatableWebSocketEventTimeout(5000) — bound a single
- *      hibernation message handler. Long-running work runs in facets
- *      with their own CPU budget; the supervisor's WS handlers should
- *      enqueue then return. 5 s recommended in CF research §C.3.
- *
- * Both calls are gated on try/catch:
- *   - workerd builds before mid-2024 don't expose either method.
- *   - WebSocketRequestResponsePair is a workerd global; absent in Node.
- * Failure is reported honestly via the return value so /api/_diag/memory
- * can show whether the runtime supported the configuration.
- */
-/**
- * Recommended hibernation event timeout (ms). 5 s per CF research §C.3
- * — long enough for the heaviest non-facet WS message handler observed
- * in W5 telemetry (~120 ms p99 for a heavy autocomplete request), short
- * enough to bound a runaway handler before it pins the actor.
- */
-export const NIMBUS_HIBERNATION_EVENT_TIMEOUT_MS = 5000;
-/** Public ping/pong contract — clients send `ping`, receive `pong`. */
-export const WS_AUTO_RESPONSE_REQUEST = 'ping';
-export const WS_AUTO_RESPONSE_RESPONSE = 'pong';
-/**
- * Configure WS hibernation behaviours on a DurableObjectState. Idempotent
- * — safe to call multiple times. Returns a result that NimbusSession
- * surfaces via /api/_diag/memory under the `hib` key.
- *
- * The `ctx` parameter is structurally typed (anything with the right
- * methods works) so this module stays Node-testable. In production the
- * caller passes the real `this.ctx` from NimbusSession's constructor.
- */
-export function configureWsHibernation(ctx) {
-    const result = {
-        autoResponseConfigured: false,
-        timeoutSetMs: null,
-    };
-    // Step 1: auto-response.
-    const Pair = globalThis.WebSocketRequestResponsePair;
-    if (typeof ctx?.setWebSocketAutoResponse === 'function' && typeof Pair === 'function') {
-        try {
-            const pair = new Pair(WS_AUTO_RESPONSE_REQUEST, WS_AUTO_RESPONSE_RESPONSE);
-            ctx.setWebSocketAutoResponse(pair);
-            result.autoResponseConfigured = true;
-        }
-        catch (e) {
-            result.autoResponseError = e?.message || String(e);
-        }
-    }
-    else if (typeof Pair !== 'function') {
-        result.autoResponseError = 'WebSocketRequestResponsePair global not available';
-    }
-    else {
-        result.autoResponseError = 'ctx.setWebSocketAutoResponse not available';
-    }
-    // Step 2: hibernation event timeout. Independent of auto-response —
-    // a workerd that lacks the global may still support the timeout
-    // method, and vice versa.
-    if (typeof ctx?.setHibernatableWebSocketEventTimeout === 'function') {
-        try {
-            ctx.setHibernatableWebSocketEventTimeout(NIMBUS_HIBERNATION_EVENT_TIMEOUT_MS);
-            result.timeoutSetMs = NIMBUS_HIBERNATION_EVENT_TIMEOUT_MS;
-        }
-        catch (e) {
-            result.timeoutError = e?.message || String(e);
-        }
-    }
-    else {
-        result.timeoutError = 'ctx.setHibernatableWebSocketEventTimeout not available';
-    }
-    return result;
-}