@absolutejs/sync 1.6.0 → 1.7.1

package/dist/engine/sandbox.d.ts

@@ -12,13 +12,25 @@
  * - First call per mutation pays a Worker spawn + compile (~30 ms). Every
  *   subsequent call reuses the isolate and only spends ~0.5 ms creating a
  *   fresh context.
- * - Timeout terminates the isolate (v1 of isolated-jsc trade-off — the
- *   sandbox runner detects this and lazily re-spawns on the next call).
+ * - Timeout terminates the isolate (the sandbox runner detects this and
+ *   lazily re-spawns on the next call). On the FFI backend timeouts throw
+ *   a TerminationException without killing the isolate; sync's runner
+ *   treats both shapes the same.
  * - Each per-call context retains some JSC metadata until the isolate's
- *   next GC sweep. Empirically ~2 MB residual per call. For long-lived
- *   mutations choose `memoryLimit` ≥ 128 (the default 32 trips after a
- *   few dozen calls without pressure for GC). v2 will let us trigger
- *   sweep explicitly from the host; for now, size up.
+ *   next GC sweep. Empirically ~2 MB residual per call (Worker backend).
+ *   For long-lived mutations choose `memoryLimit` ≥ 128 (the default 32
+ *   trips after a few dozen calls without pressure for GC).
+ *
+ * **Backend default: `'auto'`** — isolated-jsc 0.4 added an async host-fn
+ * pump on the FFI backend (alternates Bun event-loop yields with JSC
+ * microtask drains, bounded by `Script.run`'s `timeout`), so the
+ * `actions.insert/update/delete/change` async References settle on FFI
+ * just like they do on Worker. `'auto'` picks FFI when libJSC is reachable
+ * (~300 KB cold heap, interrupt-driven CPU timeouts) and falls back to
+ * Worker (~46 MB cold heap, postMessage round-trips) otherwise. Pin to
+ * `'worker'` if you specifically need Web APIs (`URL`, `TextEncoder`,
+ * `WebSocket`) inside your handler — those live in the Bun-Worker
+ * environment, not the bare JSC C API.
  *
  * The runner is built lazily per-mutation: nothing is spawned until the
  * mutation actually runs for the first time. No engine teardown hook is
@@ -31,6 +43,20 @@ export type SandboxConfig = {
     memoryLimit?: number;
     /** Wall-clock cap per call (ms). Default 5000. */
     timeout?: number;
+    /**
+     * isolated-jsc backend. Defaults to `'auto'` (FFI when libJSC is
+     * reachable, Worker otherwise) since isolated-jsc 0.4 added async
+     * host-fn support on FFI — `actions.insert/update/delete/change`
+     * now settle on both backends.
+     *
+     * Pin to `'worker'` if your handler needs Web APIs (`URL`,
+     * `TextEncoder`, `WebSocket`) — those live in the Bun-Worker
+     * environment, not the bare JSC C API.
+     *
+     * Pin to `'ffi'` for hot-path read-only handlers (~300 KB cold heap
+     * vs ~46 MB on Worker, interrupt-driven CPU timeouts).
+     */
+    backend?: 'auto' | 'ffi' | 'worker';
 };
 /**
  * Build a lazy runner for one mutation's sandboxed source. The first call

package/dist/index.js

@@ -745,6 +745,7 @@ var wrap = (source) => `
 var compile = async (source, config) => {
   const { createIsolate } = await loadIsolatedJsc();
   const isolate = await createIsolate({
+    backend: config.backend ?? "auto",
     memoryLimit: config.memoryLimit ?? 32
   });
   const script = await isolate.compileScript(wrap(source));
@@ -2300,5 +2301,5 @@ export {
   createPresenceHub
 };
 
-//# debugId=50A2A8778F250B8064756E2164756E21
+//# debugId=A95C21B5786D64AE64756E2164756E21
 //# sourceMappingURL=index.js.map