adapter-memory

Run procedures in process while retaining the HTTP transport's JSON semantics. This is useful for integration tests without starting an HTTP server.

import { createMemoryLink } from "@cablejs/adapter-memory";
import { createClient } from "@cablejs/client";
import { c } from "@cablejs/contract";
import { implement } from "@cablejs/core";
import { z } from "zod";

const api = c.contract({
  greet: c.query({ input: z.string(), output: z.string() }),
});
const procedures = implement(api)
  .context<{ prefix: string }>()
  .procedures({
    greet: ({ input, ctx }) => `${ctx.prefix}, ${input}`,
  });
const client = createClient<typeof api>({
  links: [createMemoryLink(procedures, () => ({ prefix: "Hello" }))],
});

await client.greet.query("Ada");

The context factory runs once per call. Requests and results round-trip through the same JSON codecs as HTTP, including omitted void inputs and outputs. Declared errors are preserved; the server runtime sanitizes undeclared errors.

createMemoryHost(channel, implementation, options) runs the durable channel engine against structured-clone storage, a manual clock, and browser-compatible in-memory sockets. host.flush() drains socket and background work, host.advanceTime(ms) runs due alarms, and host.hibernate() constructs fresh engine handlers over the same storage, alarm, attachments, and live sockets.

Pass one ManualClock and MemoryHostRegistry to several hosts when a test needs deterministic cross-host timers and peer calls. MemoryStorage is also exported for focused storage tests; its transactions serialize callers and commit only when the callback succeeds.