cross-tab-worker-databus 0.20.97 → 0.21.0

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 ## [Unreleased]
 
+## [0.21.0] - 2026-09-22
+
+### Breaking
+- `subscribe("")`, `publish("")` and `publishBatch("")` now throw a `TypeError` instead of being accepted. This is the removal step of the cycle opened in `0.20.96`, which warned once per instance and changed nothing else; it follows the pre-1.0 policy, and no other behavior of those three calls moved. An empty topic routes as a literal channel that no transport can address, so the subscription it created could never receive anything and a publication to it was dropped without a trace — the call now fails where the mistake is made, the same way an invalid `replay.maxPerTopic` does. The guard runs as the first statement of each method, so a rejected call also starts no transport, registers no handler and writes no route record. `publishBatch("", [])` throws too: the argument is checked ahead of the documented empty-array no-op. **Migration:** pass a real channel name. Where the topic comes from user input or a config field, validate or fall back before calling — `input.trim() || 'demo.flow'`, which is what the bundled example pages do.
+
+### Changed
+- `examples/react` and `examples/vue` now resolve their topic as `topicInput.trim() || <default>`, matching what `examples/demo` already did, because their boxes feed a reactive subscription and would otherwise hand `""` straight to the bus. The failure mode the fallback prevents is measured rather than assumed: with it removed, the Vue page keeps rendering its *previous* topic while a `TypeError` escapes to `pageerror`, and the demo page lands on 错误 with an error-feed row that never mentions the field the user just emptied. Both pages are now driven in real browser tabs (`e2e/adapters.spec.ts`, `e2e/demo.spec.ts`), each arm of the guard killing a different mutant.
+- `docs/getting-started.md` (en + zh) claimed the browser suite covers both adapter pages. It covers the Vue page only — the React page loads React from `esm.sh`, so it cannot run where CI has no network, and it hand-wires the demo page's pattern rather than using the shipped `cross-tab-worker-databus/react` adapter (covered in jsdom by `tests/hooks.test.tsx`). The paragraph now says exactly that.
+
 ## [0.20.97] - 2026-09-22
 
 ### Added

package/dist/centrifuge.js

@@ -5,7 +5,7 @@ import {
   parseDataBusPublication,
   publicationMetadata,
   selectWorkerBackend
-} from "./chunk-IVTDQ2KD.js";
+} from "./chunk-EJDXU4DK.js";
 import {
   CENTRIFUGE_INPUT_TYPE,
   CENTRIFUGE_OUTPUT_TYPE,

package/dist/{chunk-IVTDQ2KD.js → chunk-EJDXU4DK.js}

@@ -403,6 +403,12 @@ function assertHeartbeatInterval(value) {
     `Centrifuge heartbeatIntervalMs must be a positive number or Infinity, got ${String(value)}.`
   );
 }
+function assertPublicTopic(operation, topic) {
+  if (topic !== "") return;
+  throw new TypeError(
+    `CrossTabDataBus.${operation}("") addresses a channel no transport can route; use a non-empty topic.`
+  );
+}
 function assertStructuredCloneable(value) {
   if (typeof structuredClone !== "function") return;
   try {
@@ -2340,7 +2346,7 @@ var DedupManager = class {
 };
 
 // src/core/version.ts
-var SDK_VERSION = true ? "0.20.97" : "";
+var SDK_VERSION = true ? "0.21.0" : "";
 
 // src/core/data-bus.ts
 var DEFAULT_REPLAY_MAX_PER_TOPIC = 100;
@@ -2431,10 +2437,6 @@ var CrossTabDataBus = class {
   // themselves demand: the failure path starts an on-demand reopen instead of
   // stranding them until some unrelated future operation arrives.
   recoveryWaiters = 0;
-  // Latch for the empty-topic deprecation warning so a hot publish path cannot
-  // fill the console. It is per-bus and never reset: the warning is about the
-  // caller's code, not about a transient runtime condition.
-  emptyTopicWarned = false;
   /** Monotonic generation incremented on every successful transport open.
    * Stays in lockstep with `lastSuccessAt` so callers can detect that the
    * transport has been reopened even if the timestamp window is short. */
@@ -2829,8 +2831,11 @@ var CrossTabDataBus = class {
    * unsubscribe function for convenience. During an explicit stop() the
    * registration is rejected through onError and a no-op cleanup is returned,
    * so a late subscriber cannot leak into a future restart.
+   * @throws {TypeError} when `topic` is `''` — no transport can address such a
+   *   channel, so the subscription could never receive anything.
    */
   subscribe(topic, handler, options) {
+    assertPublicTopic("subscribe", topic);
     if (this.stopping) {
       this.reportError(new Error(
         "CrossTabDataBus is stopping; subscribe() was not registered. Wait for stop() to resolve, then call start() before subscribing again."
@@ -2839,7 +2844,6 @@ var CrossTabDataBus = class {
       };
     }
     this.ensureStarted();
-    if (topic === "") this.warnEmptyTopic("subscribe");
     const handlers = this.topicHandlers.get(topic) ?? /* @__PURE__ */ new Set();
     const wasUnused = handlers.size === 0;
     handlers.add(handler);
@@ -2889,20 +2893,10 @@ var CrossTabDataBus = class {
   resetDedup() {
     this.dedupManager.reset();
   }
-  /** Warn (once per bus) that an empty topic is deprecated, without changing
-   * behavior yet. `''` flows through routing as a literal channel, so the
-   * subscription it creates can never be addressed by a transport: the message
-   * silently goes nowhere. A future minor rejects it at this boundary. */
-  warnEmptyTopic(operation) {
-    if (this.emptyTopicWarned) return;
-    this.emptyTopicWarned = true;
-    console.warn(
-      `cross-tab-worker-databus: ${operation}("") addresses a channel no transport can route. Use a non-empty topic; passing "" is planned to throw in a future minor.`
-    );
-  }
-  /** Publish a message to `topic`. The owning Worker delivers it to the transport. */
+  /** Publish a message to `topic`. The owning Worker delivers it to the transport.
+   * @throws {TypeError} when `topic` is `''`; see `subscribe()`. */
   publish(topic, data, options) {
-    if (topic === "") this.warnEmptyTopic("publish");
+    assertPublicTopic("publish", topic);
     this.ensureStarted();
     if (this.rejectPublishDuringStop("publish")) return;
     if (!this.cluster.publish(topic, data, options)) {
@@ -2917,11 +2911,14 @@ var CrossTabDataBus = class {
    * in one tick. Per-item dedup / replay / ordering is preserved; each item
    * may carry its own `messageId` / `timestamp` via `options`. Empty array is
    * a no-op; single-item array delegates to `publish()`.
+   * @throws {TypeError} when `topic` is `''`; see `subscribe()`. Checked before
+   *   the empty-array no-op, so `publishBatch('', [])` throws too — the topic is
+   *   the caller's bug regardless of whether anything is carried.
    */
   publishBatch(topic, items) {
+    assertPublicTopic("publishBatch", topic);
     this.ensureStarted();
     if (items.length === 0) return;
-    if (topic === "") this.warnEmptyTopic("publishBatch");
     if (this.rejectPublishDuringStop("publishBatch")) return;
     if (items.length === 1) {
       const first = items[0];
@@ -3550,4 +3547,4 @@ export {
   parseDataBusPublication,
   selectWorkerBackend
 };
-//# sourceMappingURL=chunk-IVTDQ2KD.js.map
+//# sourceMappingURL=chunk-EJDXU4DK.js.map