svelte-adapter-uws-extensions 0.5.10 → 0.6.0-next.2

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "svelte-adapter-uws-extensions",
-  "version": "0.5.10",
+  "version": "0.6.0-next.2",
   "publishConfig": {
-    "tag": "latest"
+    "tag": "next"
   },
   "description": "Redis and Postgres extensions for svelte-adapter-uws - distributed pub/sub, replay buffers, presence tracking, rate limiting, groups, and DB change notifications",
   "author": "Kevin Radziszewski",
@@ -154,7 +154,7 @@
     "node": ">=22.0.0"
   },
   "peerDependencies": {
-    "svelte-adapter-uws": "^0.5.8"
+    "svelte-adapter-uws": "^0.6.0-next.5"
   },
   "dependencies": {
     "ioredis": "^5.0.0"
@@ -163,6 +163,7 @@
     "pg": "^8.0.0"
   },
   "devDependencies": {
+    "svelte-adapter-uws": "^0.6.0-next.5",
     "vitest": "^4.0.18",
     "ws": "^8.0.0"
   },

package/postgres/idempotency.js

@@ -123,9 +123,13 @@ export function createIdempotencyStore(client, options = {}) {
 	// callers that need the table to exist before they start polling can
 	// `await idempotency.ready()`. Subsequent ensureTable() calls are
 	// no-ops via the migrated flag.
-	const readyPromise = autoMigrate
-		? ensureTable().catch((err) => { throw err; })
-		: Promise.resolve();
+	const readyPromise = autoMigrate ? ensureTable() : Promise.resolve();
+	// A caller that never awaits ready() must not crash the process if this
+	// eager migration rejects (e.g. the table is dropped concurrently): the
+	// failure is non-fatal because acquire() / clear() / purge() each re-run
+	// ensureTable() and surface the error on first real use. An explicit
+	// ready() awaiter still observes the rejection - it receives readyPromise.
+	readyPromise.catch(() => {});
 
 	function validateKey(idempotencyKey) {
 		if (typeof idempotencyKey !== 'string' || idempotencyKey.length === 0) {