@marketrix.ai/widget 4.0.113 → 4.0.114

package/dist/src/components/views/ChatView.d.ts

@@ -20,7 +20,9 @@
  *
  * `useScreenShare` (this file's only other consumer) owns the screen-share lifecycle: the in-transcript
  * permission card, the browser picker, the live share message, and ending a share. `useLatest` keeps a
- * value readable from a callback that must not be re-created (the polling interval below, mounted once).
+ * value readable from a callback that must not be re-created (the polling interval below, mounted once);
+its refs are listed in that effect's deps for the linter, but since `useRef` identity never changes,
+listing them cannot re-arm the interval.
  * The hook returns `requestScreenAccess` — posting a request card carrying the queued turn, no-oping if
  * one is already open — plus that card's Allow/Deny handlers, the toolbar dialog's Allow/Dismiss
  * handlers, and `toggleScreenShareRef`, a toggle stopping a live share or opening that dialog.

package/dist/src/context/WidgetProviders.d.ts

@@ -13,10 +13,14 @@
  * mounted before the read, its first effect would overwrite the stored transcript on every remount.
  * `previewMode` skips init entirely: no chat session is minted, no stream opened, nothing persisted.
  *
- * The init effect's deps are empty on purpose — once per mount — and `cancelled` drops the connect when
- * a StrictMode double-invoke or an unmount cleans up before the chat_id resolves. A failed connect is
- * logged only, since `StreamClient` owns the backoff reconnect; a failed init is logged AND surfaced
- * through `uiActions.setError`.
+ * The init effect lists `previewMode`, `uiActions` and `chatActions` for the linter, but runs once per
+ * mount in practice — `uiActions` is a `useMemo([])` and `chatActions` bottoms out in `commit`
+ * (`useCallback([])`), both stable for the component's lifetime, and `previewMode` is fixed by the
+ * caller. `cancelled` drops the connect when a StrictMode double-invoke or an unmount cleans up before
+ * the chat_id resolves. `streamClient.connect` never rejects — it catches internally and owns its own
+ * backoff reconnect and warn-level log — so the call here is fire-and-forget; a failed INIT (the
+ * snapshot restore or `getOrCreateChatId`) is the one thing this bridge logs and surfaces through
+ * `uiActions.setError`.
  */
 import React from 'react';
 export declare const PortalContainerContext: React.Context<HTMLElement | null>;

package/dist/src/utils/log.d.ts

@@ -0,0 +1,2 @@
+export declare function logWarn(message: string, cause?: unknown): void;
+export declare function logError(message: string, cause?: unknown): void;