@eshal-bot/chat-widget 0.2.1 → 0.2.2

package/dist/chat-widget-markdown-chunk.js

@@ -91200,7 +91200,46 @@
     };
   }
 
-  const WidgetCitationContext = /*#__PURE__*/React.createContext(null);
+  /**
+   * WidgetCitationContext - the message's `sources` array + download handler,
+   * supplied by `<MessageBubble>` and consumed by every `<CitationPill>` that
+   * `rehypeCitations` renders inside the ReactMarkdown output.
+   *
+   * EV-2904 - WHY THIS LIVES IN ITS OWN MODULE, BEHIND A GLOBAL SINGLETON
+   * ---------------------------------------------------------------------
+   * The vanilla/IIFE build (`chat-widget.min.js` - the `<script src=...>`
+   * snippet customers actually install) ships the markdown pipeline as a
+   * SEPARATE IIFE bundle, `chat-widget-markdown-chunk.min.js`, injected at
+   * runtime by vanilla/lazyChunkLoader.js. Per rollup.config.js, `react` is
+   * the ONLY module the two bundles share (via the `__eshalChatWidgetReact`
+   * global) - every other module, including this one, is bundled a SECOND
+   * time into the chunk.
+   *
+   * The provider (`MessageBubble.jsx`) lives in the main bundle; the consumer
+   * (`CitationPill.jsx`) is pulled in by `MarkdownRenderer.jsx` and therefore
+   * lives in the chunk. With a plain `createContext(null)` in each bundle,
+   * those are two DIFFERENT context objects: the pill's `useContext` finds no
+   * matching Provider above it, falls back to the default `null`, and
+   * `CitationPill` returns `null` (its "rendered outside a chat" guard). The
+   * result is that citations silently vanish on the installed widget - no
+   * error, no raw `[N]` leak - while the Testing Lab and the ESM/UMD builds
+   * (single module graph) render them fine.
+   *
+   * Stashing the context object on a `window` key makes it a true
+   * cross-bundle singleton: whichever bundle evaluates first creates it, the
+   * other reuses it, so provider and consumer always agree. Safe for the
+   * single-graph builds too - the second import just re-reads the same
+   * object, which is exactly what a plain module-level `createContext` did.
+   *
+   * `createContext` must come from the one shared React instance for hooks to
+   * work at all; rollup.config.js already guarantees that via the
+   * `__eshalChatWidgetReact` global, so the object created here is valid in
+   * both bundles.
+   */
+  const GLOBAL_KEY = "__eshalChatWidgetCitationContext";
+  const globalScope = typeof window !== "undefined" ? window : typeof globalThis !== "undefined" ? globalThis : undefined;
+  const WidgetCitationContext = globalScope ? globalScope[GLOBAL_KEY] || (globalScope[GLOBAL_KEY] = /*#__PURE__*/React.createContext(null)) : /*#__PURE__*/React.createContext(null);
+
   function decodeName(name) {
     if (!name) return "";
     try {