svelte-adapter-uws 0.2.19 → 0.2.20

package/README.md

@@ -737,12 +737,21 @@ The WebSocket upgrade is an HTTP request. The browser treats it like any other r
 
 Available in server hooks, load functions, form actions, API routes, and WebSocket hooks (`hooks.ws`).
 
-### `platform.publish(topic, event, data)`
+### `platform.publish(topic, event, data, options?)`
 
 Send a message to all WebSocket clients subscribed to a topic.
 
 Topic and event names are validated before being written into the JSON envelope -- quotes, backslashes, and control characters will throw. This prevents JSON injection when names are built from dynamic values like user IDs (`platform.publish(\`user:\${id}\`, ...)`). The validation is a single-pass char scan and adds no measurable overhead.
 
+In cluster mode, the message is automatically relayed to all other workers. Pass `{ relay: false }` to skip the relay when the message originates from an external pub/sub source (Redis, Postgres LISTEN/NOTIFY, etc.) that already delivers to every process:
+
+```js
+// Redis subscriber running on every worker -- relay would cause duplicates
+sub.on('message', (channel, payload) => {
+  platform.publish(channel, 'update', JSON.parse(payload), { relay: false });
+});
+```
+
 ```js
 // src/routes/todos/+page.server.js
 export const actions = {
@@ -2085,7 +2094,9 @@ If a worker crashes, it is automatically restarted with exponential backoff. On
 
 ### WebSocket + clustering
 
-`platform.publish()` is automatically relayed across all workers via the primary thread, so subscribers on any worker receive the message. This is built in  - no external pub/sub needed.
+`platform.publish()` is automatically relayed across all workers via the primary thread, so subscribers on any worker receive the message. This is built in -- no external pub/sub needed.
+
+If you add your own cross-process messaging (Redis, Postgres LISTEN/NOTIFY, etc.), pass `{ relay: false }` to prevent duplicate delivery -- your external source already fans out to every worker, so the built-in relay would double it.
 
 Per-worker limitations (acceptable for most apps):
 - `platform.connections`  - returns the count for the local worker only

package/files/handler.js

@@ -239,11 +239,14 @@ const platform = {
 	 * Auto-wraps in a { topic, event, data } envelope that the client store understands.
 	 * No-op if no clients are subscribed - safe to call unconditionally.
 	 */
-	publish(topic, event, data) {
+	publish(topic, event, data, options) {
 		const envelope = '{"topic":' + esc(topic) + ',"event":' + esc(event) + ',"data":' + JSON.stringify(data) + '}';
 		const result = app.publish(topic, envelope, false, false);
-		// Relay to other workers via main thread (no-op in single-process mode)
-		if (parentPort) {
+		// Relay to other workers via main thread (no-op in single-process mode).
+		// Pass { relay: false } when the message originates from an external
+		// pub/sub source (Redis, Postgres, etc.) that already fans out to
+		// every process -- relaying would cause duplicate delivery.
+		if (parentPort && (!options || options.relay !== false)) {
 			parentPort.postMessage({ type: 'publish', topic, envelope });
 		}
 		return result;

package/index.d.ts

@@ -340,6 +340,9 @@ export interface Platform {
 	 * @param topic - Topic string (e.g. `'todos'`, `'user:123'`, `'org:456'`)
 	 * @param event - Event name (e.g. `'created'`, `'updated'`, `'deleted'`)
 	 * @param data - Payload (will be JSON-serialized)
+	 * @param options - Optional. Pass `{ relay: false }` to skip cross-worker relay
+	 *   (use this when the message comes from an external pub/sub source like Redis
+	 *   or Postgres that already delivers to every process).
 	 *
 	 * @example
 	 * ```js
@@ -350,7 +353,7 @@ export interface Platform {
 	 * }
 	 * ```
 	 */
-	publish(topic: string, event: string, data?: unknown): boolean;
+	publish(topic: string, event: string, data?: unknown, options?: { relay?: boolean }): boolean;
 
 	/**
 	 * Send a message to a single WebSocket connection.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "svelte-adapter-uws",
-  "version": "0.2.19",
+  "version": "0.2.20",
   "description": "SvelteKit adapter for uWebSockets.js - high-performance C++ HTTP server with built-in WebSocket support",
   "author": "Kevin Radziszewski",
   "license": "MIT",

package/vite.js

@@ -100,9 +100,10 @@ export default function uws(options = {}) {
 	 * @param {string} topic
 	 * @param {string} event
 	 * @param {unknown} [data]
+	 * @param {{ relay?: boolean }} [_options] - Accepted for API parity with production; ignored in dev (single-process).
 	 * @returns {boolean}
 	 */
-	function publish(topic, event, data) {
+	function publish(topic, event, data, _options) {
 		const envelope = '{"topic":' + esc(topic) + ',"event":' + esc(event) + ',"data":' + JSON.stringify(data) + '}';
 		let sent = false;
 		for (const [ws, topics] of subscriptions) {