reflectdb 0.1.2 → 0.2.0

package/dist/cjs/transport/sse.d.cts

@@ -189,17 +189,51 @@ interface SseServerConfig {
 	* Default: 1 MB.
 	*/
 	maxMessageBytes?: number;
+	/**
+	* Return replies from the POST that produced them instead of assuming they
+	* can be streamed.
+	*
+	* Normally SSE is server→client only: a client POSTs a message and every
+	* reply — `hello_ack`, snapshots, op acks — comes back down the held stream.
+	* That works only while the POST and the stream are handled by the SAME
+	* process. On a serverless platform (Vercel, Lambda, Workers) they are two
+	* separate invocations, so those replies would be enqueued onto a stream the
+	* POST's process does not have, and the client would hang at the handshake.
+	*
+	* With this set, `collectReplies` runs a message and hands back what it
+	* produced so the HTTP handler can put it in the POST response body. The
+	* stream is then only used for what it is actually good at: pushing OTHER
+	* clients' changes. Pair it with `serverless: true` on the client transport.
+	*
+	* Off by default — a single-process server should keep streaming everything,
+	* and turning this on there would deliver each reply twice.
+	*/
+	serverless?: boolean;
 }
 declare function createSseServerTransport(cfg?: SseServerConfig): ServerTransport & {
 	handleSubscribe(clientId: string, controller: ReadableStreamDefaultController, lastEventId?: string): void;
 	handleMessage(clientId: string, message: ClientMessage): void;
 	handleDisconnect(clientId: string): void;
 	createEventStream(clientId: string, lastEventId?: string): ReadableStream;
+	collectReplies(clientId: string, message: ClientMessage, settle?: () => Promise<void>): Promise<ServerMessage[]>;
 };
 interface SseClientConfig {
 	eventUrl: string;
 	messageUrl: string;
 	headers?: Record<string, string>;
+	/**
+	* Read replies out of the POST response instead of waiting for them on the
+	* stream. Must match `serverless: true` on the server transport.
+	*
+	* Needed wherever the POST and the event stream are handled by different
+	* processes — Vercel, Lambda, Workers. There, replies to a POST are produced
+	* by a process that does not own this client's stream, so they can never be
+	* streamed and the handshake never completes.
+	*
+	* Leave it off for a single-process server: replies stream normally there,
+	* and turning it on would deliver every one of them twice.
+	*/
+	serverless?: boolean;
 }
 declare function createSseClientTransport(config: SseClientConfig): ClientTransport;
 export { SseClientConfig, SseServerConfig, createSseClientTransport, createSseServerTransport };

package/dist/cjs/transport/ws.cjs

@@ -1,4 +1,3 @@
-var import_node_module = require("node:module");
 var __defProp = Object.defineProperty;
 var __getOwnPropNames = Object.getOwnPropertyNames;
 var __getOwnPropDesc = Object.getOwnPropertyDescriptor;

package/dist/cjs/vanilla/index.cjs

@@ -1,4 +1,3 @@
-var import_node_module = require("node:module");
 var __defProp = Object.defineProperty;
 var __getOwnPropNames = Object.getOwnPropertyNames;
 var __getOwnPropDesc = Object.getOwnPropertyDescriptor;

package/dist/client/index.js

@@ -6,7 +6,7 @@ import {
 } from "../shared/esm-8qbr4y0d.js";
 import"../shared/esm-rw7jjtrv.js";
 import"../shared/esm-3tkwvysa.js";
-import"../shared/esm-k7kedp3y.js";
+import"../shared/esm-g5h4a88j.js";
 // src/client/storage/memory.ts
 function createMemoryStorage() {
   const rows = new Map;

package/dist/client/storage/indexeddb.js

@@ -1,4 +1,4 @@
-import"../../shared/esm-k7kedp3y.js";
+import"../../shared/esm-g5h4a88j.js";
 
 // src/client/storage/indexeddb.ts
 function createIndexedDBStorage(config) {

package/dist/core/index.js

@@ -18,7 +18,7 @@ import {
   isErrorReason,
   reasonFromError
 } from "../shared/esm-3tkwvysa.js";
-import"../shared/esm-k7kedp3y.js";
+import"../shared/esm-g5h4a88j.js";
 // src/core/schema.ts
 function view(opts) {
   return { __view: true, ...opts };