svelte-adapter-uws-extensions 0.5.2 → 0.5.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "svelte-adapter-uws-extensions",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "publishConfig": {
     "tag": "latest"
   },
@@ -154,7 +154,7 @@
     "node": ">=22.0.0"
   },
   "peerDependencies": {
-    "svelte-adapter-uws": "^0.5.2"
+    "svelte-adapter-uws": "^0.5.3"
   },
   "dependencies": {
     "ioredis": "^5.0.0"

package/redis/cursor.js

@@ -760,7 +760,23 @@ export function createCursor(client, options = {}) {
 			message(ws, { data, platform }) {
 				if (data && data.type === 'cursor' && data.topic && data.data !== undefined) {
 					tracker.update(ws, data.topic, data.data, platform);
+					return;
 				}
+				// Client-initiated reconnect-snapshot. The cursor plugin client
+				// sends `{type:'cursor-snapshot', topic}` on every status==='open'
+				// (initial connect + reconnect). Pre-fix, this text frame had no
+				// server handler and was a dead wire frame; the snapshot path
+				// only fired through `hooks.subscribe` -> `tracker.snapshot` when
+				// the ws subscribed to the `__cursor:{topic}` channel. With this
+				// branch, the snapshot also re-emits on the explicit frame so a
+				// reconnecting tab that resubscribes via `subscribe-batch` (which
+				// the adapter dedups when the topic is already in the user data
+				// set) still gets a fresh catalog + bulk.
+				if (data && data.type === 'cursor-snapshot' && typeof data.topic === 'string') {
+					tracker.snapshot(ws, data.topic, platform);
+					return;
+				}
+				_warnCursorHooksMessageShape(data);
 			},
 			close(ws, { platform }) {
 				return tracker.remove(ws, platform);
@@ -770,3 +786,40 @@ export function createCursor(client, options = {}) {
 
 	return tracker;
 }
+
+/**
+ * One-time dev-warn dedup for `cursor.hooks.message` shape misuse. The most
+ * common cause is wiring the hook against `createMessage({ onUnhandled })`
+ * which passes raw bytes, not a parsed envelope. The fix is to switch to
+ * `createMessage({ onJsonMessage(ws, msg, platform) { ... } })` (svelte-
+ * realtime >= 0.5.9 + svelte-adapter-uws >= 0.5.3), which forwards the
+ * parsed object directly.
+ */
+let _cursorHooksMessageBadShapeWarned = false;
+
+/**
+ * @param {any} data
+ */
+function _warnCursorHooksMessageShape(data) {
+	if (_cursorHooksMessageBadShapeWarned) return;
+	_cursorHooksMessageBadShapeWarned = true;
+	const got = data instanceof ArrayBuffer
+		? 'ArrayBuffer (raw bytes -- did you wire this from createMessage({onUnhandled}) ?)'
+		: Array.isArray(data)
+			? 'Array'
+			: data === null
+				? 'null'
+				: typeof data === 'object'
+					? 'object with data.type=' + String(data.type)
+					: typeof data;
+	console.warn(
+		'[redis/cursor] hooks.message called with unexpected shape (' + got + '). ' +
+		'Expected a parsed object {type:"cursor", topic, data} or ' +
+		'{type:"cursor-snapshot", topic}. ' +
+		'If you wired this from `createMessage({ onUnhandled })` and got raw bytes, ' +
+		'switch to `createMessage({ onJsonMessage(ws, msg, platform) { ... } })` ' +
+		'which forwards the parsed JSON envelope. ' +
+		'This warning fires once per process.\n' +
+		'  See: https://svti.me/cursor-hooks-message'
+	);
+}

package/redis/presence.js

@@ -522,8 +522,22 @@ export function createPresence(client, options = {}) {
 					pipe.hpexpire(topicHash, presenceTtlMs, 'FIELDS', 1, userKey);
 				}
 				if (activePlatform) {
-					const keys = [...data.keys()];
-					activePlatform.publish('__presence:' + topic, 'heartbeat', keys);
+					// Publish a `{userKey: data}` map (instead of a key-only
+					// array) so a client whose entry aged out between
+					// heartbeats can re-add it from the heartbeat alone.
+					// Pre-fix, the wire carried only `keys` and the client
+					// handler could only refresh `existing` entries; an
+					// entry the client swept (cross-replica relay latency,
+					// brief backpressure, JS thread saturation) could never
+					// be recovered without a presence_diff for that user.
+					// Older clients fall back gracefully: they see an
+					// object instead of an array and skip the legacy
+					// "refresh-existing" branch, but the next presence_diff
+					// or presence_state still reconciles them.
+					/** @type {Record<string, any>} */
+					const dataMap = {};
+					for (const [userKey, entry] of data) dataMap[userKey] = entry.data;
+					activePlatform.publish('__presence:' + topic, 'heartbeat', dataMap);
 				}
 			}
 		}
@@ -1360,6 +1374,26 @@ export function createPresence(client, options = {}) {
 				}
 				await tracker.join(ws, topic, platform);
 			},
+			message(ws, { data, platform }) {
+				// Client-initiated reconnect-snapshot. The presence plugin
+				// client sends `{type:'presence-snapshot', topic}` on every
+				// status==='open' (initial connect + reconnect). Re-emits
+				// `presence_state` to the requesting ws via `tracker.sync`,
+				// which is the same path that fires on a fresh subscribe.
+				// Symmetric to cursor's `cursor-snapshot` text frame.
+				//
+				// Without this, board-scoped presence stayed stale across
+				// reconnects: a tab that had joined via an RPC saw no
+				// presence_diff during the disconnect window, and on
+				// reconnect its in-memory map was whatever it last knew.
+				// Global presence accidentally self-healed because most
+				// apps call `presence.join('global')` from the `open` hook
+				// which fires on every reconnect; per-board presence does
+				// not have an equivalent auto-rejoin.
+				if (data && data.type === 'presence-snapshot' && typeof data.topic === 'string') {
+					tracker.sync(ws, data.topic, platform).catch(() => { /* surfaced via breaker */ });
+				}
+			},
 			async unsubscribe(ws, topic, { platform }) {
 				if (topic.startsWith('__presence:')) {
 					const realTopic = topic.slice('__presence:'.length);