cross-tab-worker-databus 0.21.13 → 0.21.15

package/dist/{chunk-4HW6PYIR.js → chunk-VQJIMGJN.js}

@@ -2410,7 +2410,7 @@ var DedupManager = class {
 };
 
 // src/core/version.ts
-var SDK_VERSION = true ? "0.21.13" : "";
+var SDK_VERSION = true ? "0.21.15" : "";
 
 // src/core/data-bus.ts
 var DEFAULT_REPLAY_MAX_PER_TOPIC = 100;
@@ -3626,4 +3626,4 @@ export {
   parseDataBusPublication,
   selectWorkerBackend
 };
-//# sourceMappingURL=chunk-4HW6PYIR.js.map
+//# sourceMappingURL=chunk-VQJIMGJN.js.map

package/dist/cjs/centrifuge.cjs

@@ -2539,7 +2539,7 @@ var DedupManager = class {
 };
 
 // src/core/version.ts
-var SDK_VERSION = true ? "0.21.13" : "";
+var SDK_VERSION = true ? "0.21.15" : "";
 
 // src/core/data-bus.ts
 var DEFAULT_REPLAY_MAX_PER_TOPIC = 100;
@@ -4006,11 +4006,13 @@ var CentrifugeWorkerTransport = class {
   // `isCurrentBackend()` compares worker/port/localSession identity as well.
   // Only the asynchronous credential bridge reads the counter: a provider may
   // settle after the backend it was answering is gone. Worker error events need
-  // no such check, but not for the reason this note used to give — `stop()`
-  // bumps at `:189` and removes the listeners at `:193-194`, so the generation
-  // moves on *before* the removal, not after. The containment is that both
-  // happen in one synchronous task, together with `handlers = null`, and no
-  // message or error event can be delivered to this object mid-task.
+  // no such check, but not for the reason this note used to give — the top of
+  // `stop()` bumps the counter and only then removes the listeners, so the
+  // generation moves on *before* the removal, not after, while `onWorkerFailed()`
+  // removes them without touching the counter at all. The containment in both
+  // cases is that they happen in one synchronous task, together with
+  // `handlers = null`, and no message or error event can be delivered to this
+  // object mid-task.
   generation = 0;
   get diagnosticsBackend() {
     return this.backend ?? "uninitialized";