@ttt-productions/chat-react 0.12.15 → 0.13.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ttt-productions/chat-react",
-  "version": "0.12.15",
+  "version": "0.13.1",
   "description": "Chat React UI, hooks, and Firebase-client adapter for TTT Productions apps (realtime newest window + infinite older pagination)",
   "repository": {
     "type": "git",
@@ -60,14 +60,11 @@
     }
   },
   "dependencies": {
-    "@ttt-productions/chat-core": "^0.10.2",
-    "@ttt-productions/chat-schemas": "^0.9.4",
+    "@ttt-productions/chat-core": "^0.11.0",
+    "@ttt-productions/chat-schemas": "^0.10.0",
     "@ttt-productions/realtime-core": "^0.1.3",
-    "@ttt-productions/media-schemas": "^0.14.3",
     "@ttt-productions/ui-core": "^0.11.10",
-    "@ttt-productions/file-input": "^0.11.6",
     "@ttt-productions/upload-ui": "^0.7.5",
-    "@ttt-productions/media-viewer": "^0.10.6",
     "@ttt-productions/mobile-core": "^0.9.1",
     "@ttt-productions/firebase-helpers": "^0.12.3"
   },

package/src/styles/chat.css

@@ -96,121 +96,6 @@
   max-width: 280px;
 }
 
-/* --- Attachment states --- */
-
-/* Pending / URL-settling placeholder. Parchment-safe: a lightly tinted surface
-   with a subtle tokenized border (NOT the old opaque muted slab, which read as a
-   dark rectangle on the parchment chat canvas). It is a small inline status row —
-   deliberately NOT a media-sized box, so it never implies the file is viewable.
-   All colors are theme tokens; a restrained shimmer conveys "in progress". */
-.chat-attachment-pending {
-  position: relative;
-  overflow: hidden;
-  display: flex;
-  align-items: center;
-  gap: 0.5rem;
-  padding: 0.5rem 0.75rem;
-  border-radius: 0.375rem;
-  background-color: hsl(var(--muted) / 0.2);
-  border: 1px solid hsl(var(--border) / 0.6);
-  color: hsl(var(--muted-foreground));
-  font-size: 0.75rem;
-}
-
-/* Restrained left-to-right shimmer over the tinted surface. Tokenized, low-opacity,
-   and disabled under prefers-reduced-motion. The spinner remains the primary cue. */
-.chat-attachment-pending::after {
-  content: "";
-  position: absolute;
-  inset: 0;
-  background: linear-gradient(
-    90deg,
-    transparent 0%,
-    hsl(var(--muted-foreground) / 0.06) 50%,
-    transparent 100%
-  );
-  transform: translateX(-100%);
-  animation: chat-attachment-shimmer 1.8s ease-in-out infinite;
-  pointer-events: none;
-}
-
-@keyframes chat-attachment-shimmer {
-  100% {
-    transform: translateX(100%);
-  }
-}
-
-@media (prefers-reduced-motion: reduce) {
-  .chat-attachment-pending::after {
-    animation: none;
-  }
-}
-
-.chat-attachment-media {
-  max-width: 320px;
-  border-radius: 0.375rem;
-  overflow: hidden;
-}
-
-.chat-attachment-text-link {
-  display: inline-flex;
-  align-items: center;
-  gap: 0.375rem;
-  padding: 0.375rem 0.625rem;
-  border-radius: 0.375rem;
-  background-color: hsl(var(--muted));
-  color: hsl(var(--primary));
-  font-size: 0.8125rem;
-  text-decoration: none;
-  transition: opacity 0.15s;
-}
-
-.chat-attachment-text-link:hover {
-  opacity: 0.8;
-}
-
-/* Terminal-failure placeholder. A restrained, tokenized surface — a subtle border
-   and faint muted tint, NOT a destructive-red block (the failure is localized to
-   this attachment, so it must not make the whole bubble read as an error). */
-.chat-attachment-rejected {
-  display: flex;
-  align-items: flex-start;
-  gap: 0.5rem;
-  padding: 0.5rem 0.75rem;
-  border-radius: 0.375rem;
-  background-color: hsl(var(--muted) / 0.35);
-  border: 1px solid hsl(var(--border));
-  color: hsl(var(--muted-foreground));
-  font-size: 0.75rem;
-}
-
-.chat-attachment-rejected-icon {
-  margin-top: 0.05rem;
-  color: hsl(var(--muted-foreground));
-}
-
-.chat-attachment-rejected-body {
-  display: flex;
-  flex-direction: column;
-  gap: 0.05rem;
-  min-width: 0;
-}
-
-.chat-attachment-rejected-reason {
-  opacity: 0.85;
-}
-
-.chat-attachment-retry {
-  margin-left: auto;
-  flex-shrink: 0;
-}
-
-.chat-attachment-status-label {
-  margin-left: auto;
-  opacity: 0.7;
-  font-style: italic;
-}
-
 /* --- Composer --- */
 .chat-composer {
   display: flex;
@@ -219,30 +104,6 @@
   width: 100%;
 }
 
-.chat-composer-file-preview {
-  display: flex;
-  align-items: center;
-  gap: 0.5rem;
-  padding: 0.375rem 0.5rem;
-  border-radius: 0.375rem;
-  background-color: hsl(var(--muted));
-  font-size: 0.8125rem;
-}
-
-.chat-composer-file-name {
-  flex: 1;
-  min-width: 0;
-  overflow: hidden;
-  text-overflow: ellipsis;
-  white-space: nowrap;
-}
-
-.chat-composer-upload-status {
-  display: flex;
-  align-items: center;
-  gap: 0.375rem;
-}
-
 /* Mention system — default chip styling. Consumers override via custom
    renderMention or by targeting .chat-mention-chip directly. */
 .chat-mention-chip {

package/dist/context/ChatAttachmentMediaContext.d.ts

@@ -1,37 +0,0 @@
-import * as React from "react";
-import type { MediaPreviewProps, MediaViewerType } from "@ttt-productions/media-viewer";
-import type { ChatAttachment } from "@ttt-productions/chat-core";
-/**
- * The media kinds chat actually renders through the injected component. Chat only ever
- * mounts it for image/video/audio attachments; text/markdown render as the package's own
- * download link and never reach this slot. Computed as the intersection of chat-core's
- * `ChatAttachment['type']` and media-viewer's `MediaViewerType`, so it stays in the chat +
- * media-viewer domains with no ttt-core dependency (ARCH-201) and tracks either union
- * automatically if a kind is added or removed.
- */
-export type ChatAttachmentMediaKind = Extract<ChatAttachment["type"], MediaViewerType>;
-/**
- * The component chat attachments render their media through. Defaults to the bare
- * media-viewer `MediaViewer` when no provider is present; the consuming app injects its own
- * wrapper (recovery adapter, diagnostics, telemetry — whatever the app's one display path
- * adds) so chat media rides the SAME display pipeline as every other surface. chat-react
- * stays app-agnostic: it renders whatever component it is handed with plain MediaPreview
- * props — except `type`, which is REQUIRED and narrowed to the kind chat provides, so the
- * consuming wrapper never has to narrow an all-optional classification (no dead
- * mime/name/'other' branch).
- */
-export type ChatAttachmentMediaComponent = React.ComponentType<Omit<MediaPreviewProps, "type"> & {
-    type: ChatAttachmentMediaKind;
-}>;
-export type ChatAttachmentMediaProviderProps = {
-    mediaComponent: ChatAttachmentMediaComponent;
-    children: React.ReactNode;
-};
-/**
- * Optional (unlike ChatAttachmentUrlProvider, which is required): without it,
- * attachments render through the package's own MediaViewer exactly as before.
- */
-export declare function ChatAttachmentMediaProvider(props: ChatAttachmentMediaProviderProps): React.JSX.Element;
-/** Nullable hook — consumers fall back to the package MediaViewer. */
-export declare function useChatAttachmentMediaComponent(): ChatAttachmentMediaComponent | null;
-//# sourceMappingURL=ChatAttachmentMediaContext.d.ts.map

package/dist/context/ChatAttachmentMediaContext.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ChatAttachmentMediaContext.d.ts","sourceRoot":"","sources":["../../src/context/ChatAttachmentMediaContext.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAC/B,OAAO,KAAK,EAAE,iBAAiB,EAAE,eAAe,EAAE,MAAM,+BAA+B,CAAC;AACxF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAEjE;;;;;;;GAOG;AACH,MAAM,MAAM,uBAAuB,GAAG,OAAO,CAAC,cAAc,CAAC,MAAM,CAAC,EAAE,eAAe,CAAC,CAAC;AAEvF;;;;;;;;;GASG;AACH,MAAM,MAAM,4BAA4B,GAAG,KAAK,CAAC,aAAa,CAC5D,IAAI,CAAC,iBAAiB,EAAE,MAAM,CAAC,GAAG;IAAE,IAAI,EAAE,uBAAuB,CAAA;CAAE,CACpE,CAAC;AAIF,MAAM,MAAM,gCAAgC,GAAG;IAC7C,cAAc,EAAE,4BAA4B,CAAC;IAC7C,QAAQ,EAAE,KAAK,CAAC,SAAS,CAAC;CAC3B,CAAC;AAEF;;;GAGG;AACH,wBAAgB,2BAA2B,CAAC,KAAK,EAAE,gCAAgC,qBAOlF;AAED,sEAAsE;AACtE,wBAAgB,+BAA+B,IAAI,4BAA4B,GAAG,IAAI,CAErF"}

package/dist/context/ChatAttachmentMediaContext.js

@@ -1,17 +0,0 @@
-"use client";
-import { jsx as _jsx } from "react/jsx-runtime";
-import * as React from "react";
-const ChatAttachmentMediaContext = React.createContext(null);
-/**
- * Optional (unlike ChatAttachmentUrlProvider, which is required): without it,
- * attachments render through the package's own MediaViewer exactly as before.
- */
-export function ChatAttachmentMediaProvider(props) {
-    const { mediaComponent, children } = props;
-    return (_jsx(ChatAttachmentMediaContext.Provider, { value: mediaComponent, children: children }));
-}
-/** Nullable hook — consumers fall back to the package MediaViewer. */
-export function useChatAttachmentMediaComponent() {
-    return React.useContext(ChatAttachmentMediaContext);
-}
-//# sourceMappingURL=ChatAttachmentMediaContext.js.map

package/dist/context/ChatAttachmentMediaContext.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ChatAttachmentMediaContext.js","sourceRoot":"","sources":["../../src/context/ChatAttachmentMediaContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AA4B/B,MAAM,0BAA0B,GAAG,KAAK,CAAC,aAAa,CAAsC,IAAI,CAAC,CAAC;AAOlG;;;GAGG;AACH,MAAM,UAAU,2BAA2B,CAAC,KAAuC;IACjF,MAAM,EAAE,cAAc,EAAE,QAAQ,EAAE,GAAG,KAAK,CAAC;IAC3C,OAAO,CACL,KAAC,0BAA0B,CAAC,QAAQ,IAAC,KAAK,EAAE,cAAc,YACvD,QAAQ,GAC2B,CACvC,CAAC;AACJ,CAAC;AAED,sEAAsE;AACtE,MAAM,UAAU,+BAA+B;IAC7C,OAAO,KAAK,CAAC,UAAU,CAAC,0BAA0B,CAAC,CAAC;AACtD,CAAC","sourcesContent":["\"use client\";\n\nimport * as React from \"react\";\nimport type { MediaPreviewProps, MediaViewerType } from \"@ttt-productions/media-viewer\";\nimport type { ChatAttachment } from \"@ttt-productions/chat-core\";\n\n/**\n * The media kinds chat actually renders through the injected component. Chat only ever\n * mounts it for image/video/audio attachments; text/markdown render as the package's own\n * download link and never reach this slot. Computed as the intersection of chat-core's\n * `ChatAttachment['type']` and media-viewer's `MediaViewerType`, so it stays in the chat +\n * media-viewer domains with no ttt-core dependency (ARCH-201) and tracks either union\n * automatically if a kind is added or removed.\n */\nexport type ChatAttachmentMediaKind = Extract<ChatAttachment[\"type\"], MediaViewerType>;\n\n/**\n * The component chat attachments render their media through. Defaults to the bare\n * media-viewer `MediaViewer` when no provider is present; the consuming app injects its own\n * wrapper (recovery adapter, diagnostics, telemetry — whatever the app's one display path\n * adds) so chat media rides the SAME display pipeline as every other surface. chat-react\n * stays app-agnostic: it renders whatever component it is handed with plain MediaPreview\n * props — except `type`, which is REQUIRED and narrowed to the kind chat provides, so the\n * consuming wrapper never has to narrow an all-optional classification (no dead\n * mime/name/'other' branch).\n */\nexport type ChatAttachmentMediaComponent = React.ComponentType<\n  Omit<MediaPreviewProps, \"type\"> & { type: ChatAttachmentMediaKind }\n>;\n\nconst ChatAttachmentMediaContext = React.createContext<ChatAttachmentMediaComponent | null>(null);\n\nexport type ChatAttachmentMediaProviderProps = {\n  mediaComponent: ChatAttachmentMediaComponent;\n  children: React.ReactNode;\n};\n\n/**\n * Optional (unlike ChatAttachmentUrlProvider, which is required): without it,\n * attachments render through the package's own MediaViewer exactly as before.\n */\nexport function ChatAttachmentMediaProvider(props: ChatAttachmentMediaProviderProps) {\n  const { mediaComponent, children } = props;\n  return (\n    <ChatAttachmentMediaContext.Provider value={mediaComponent}>\n      {children}\n    </ChatAttachmentMediaContext.Provider>\n  );\n}\n\n/** Nullable hook — consumers fall back to the package MediaViewer. */\nexport function useChatAttachmentMediaComponent(): ChatAttachmentMediaComponent | null {\n  return React.useContext(ChatAttachmentMediaContext);\n}\n"]}

package/dist/context/ChatAttachmentUrlContext.d.ts

@@ -1,25 +0,0 @@
-import * as React from "react";
-import type { ChatAttachment } from "@ttt-productions/chat-core";
-/**
- * Resolves a READY chat attachment to a display URL at render time. The
- * attachment doc stores only `mediaAssetId` (never a URL); the consuming app
- * injects a resolver that builds the protected-gateway URL (or an emulator
- * URL) from `attachment.mediaAssetId` + its variant scheme. chat-react stays
- * app-agnostic — it never knows about gateways, hosts, or Firebase.
- *
- * Return null when no URL can be built yet (e.g. missing assetId) — the
- * renderer shows nothing for that attachment body.
- */
-export type ChatAttachmentUrlResolver = (attachment: ChatAttachment) => string | null;
-export type ChatAttachmentUrlProviderProps = {
-    resolveAttachmentUrl: ChatAttachmentUrlResolver;
-    children: React.ReactNode;
-};
-/**
- * Wraps any chat tree that renders attachments. Required alongside
- * <ChatNameResolverProvider> for trees rendering <ChatShell>/<MessageList>.
- */
-export declare function ChatAttachmentUrlProvider(props: ChatAttachmentUrlProviderProps): React.JSX.Element;
-/** Strict hook — throws if no provider is wrapped (missing setup must surface). */
-export declare function useChatAttachmentUrlResolver(): ChatAttachmentUrlResolver;
-//# sourceMappingURL=ChatAttachmentUrlContext.d.ts.map

package/dist/context/ChatAttachmentUrlContext.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"ChatAttachmentUrlContext.d.ts","sourceRoot":"","sources":["../../src/context/ChatAttachmentUrlContext.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAC/B,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,4BAA4B,CAAC;AAEjE;;;;;;;;;GASG;AACH,MAAM,MAAM,yBAAyB,GAAG,CAAC,UAAU,EAAE,cAAc,KAAK,MAAM,GAAG,IAAI,CAAC;AAItF,MAAM,MAAM,8BAA8B,GAAG;IAC3C,oBAAoB,EAAE,yBAAyB,CAAC;IAChD,QAAQ,EAAE,KAAK,CAAC,SAAS,CAAC;CAC3B,CAAC;AAEF;;;GAGG;AACH,wBAAgB,yBAAyB,CAAC,KAAK,EAAE,8BAA8B,qBAO9E;AAED,mFAAmF;AACnF,wBAAgB,4BAA4B,IAAI,yBAAyB,CAQxE"}

package/dist/context/ChatAttachmentUrlContext.js

@@ -1,21 +0,0 @@
-"use client";
-import { jsx as _jsx } from "react/jsx-runtime";
-import * as React from "react";
-const ChatAttachmentUrlContext = React.createContext(null);
-/**
- * Wraps any chat tree that renders attachments. Required alongside
- * <ChatNameResolverProvider> for trees rendering <ChatShell>/<MessageList>.
- */
-export function ChatAttachmentUrlProvider(props) {
-    const { resolveAttachmentUrl, children } = props;
-    return (_jsx(ChatAttachmentUrlContext.Provider, { value: resolveAttachmentUrl, children: children }));
-}
-/** Strict hook — throws if no provider is wrapped (missing setup must surface). */
-export function useChatAttachmentUrlResolver() {
-    const resolver = React.useContext(ChatAttachmentUrlContext);
-    if (!resolver) {
-        throw new Error("[chat-react] ChatAttachmentUrlProvider is required. Wrap your ChatShell tree with <ChatAttachmentUrlProvider>.");
-    }
-    return resolver;
-}
-//# sourceMappingURL=ChatAttachmentUrlContext.js.map

package/dist/context/ChatAttachmentUrlContext.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"ChatAttachmentUrlContext.js","sourceRoot":"","sources":["../../src/context/ChatAttachmentUrlContext.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAC;;AAEb,OAAO,KAAK,KAAK,MAAM,OAAO,CAAC;AAe/B,MAAM,wBAAwB,GAAG,KAAK,CAAC,aAAa,CAAmC,IAAI,CAAC,CAAC;AAO7F;;;GAGG;AACH,MAAM,UAAU,yBAAyB,CAAC,KAAqC;IAC7E,MAAM,EAAE,oBAAoB,EAAE,QAAQ,EAAE,GAAG,KAAK,CAAC;IACjD,OAAO,CACL,KAAC,wBAAwB,CAAC,QAAQ,IAAC,KAAK,EAAE,oBAAoB,YAC3D,QAAQ,GACyB,CACrC,CAAC;AACJ,CAAC;AAED,mFAAmF;AACnF,MAAM,UAAU,4BAA4B;IAC1C,MAAM,QAAQ,GAAG,KAAK,CAAC,UAAU,CAAC,wBAAwB,CAAC,CAAC;IAC5D,IAAI,CAAC,QAAQ,EAAE,CAAC;QACd,MAAM,IAAI,KAAK,CACb,gHAAgH,CACjH,CAAC;IACJ,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC","sourcesContent":["\"use client\";\n\nimport * as React from \"react\";\nimport type { ChatAttachment } from \"@ttt-productions/chat-core\";\n\n/**\n * Resolves a READY chat attachment to a display URL at render time. The\n * attachment doc stores only `mediaAssetId` (never a URL); the consuming app\n * injects a resolver that builds the protected-gateway URL (or an emulator\n * URL) from `attachment.mediaAssetId` + its variant scheme. chat-react stays\n * app-agnostic — it never knows about gateways, hosts, or Firebase.\n *\n * Return null when no URL can be built yet (e.g. missing assetId) — the\n * renderer shows nothing for that attachment body.\n */\nexport type ChatAttachmentUrlResolver = (attachment: ChatAttachment) => string | null;\n\nconst ChatAttachmentUrlContext = React.createContext<ChatAttachmentUrlResolver | null>(null);\n\nexport type ChatAttachmentUrlProviderProps = {\n  resolveAttachmentUrl: ChatAttachmentUrlResolver;\n  children: React.ReactNode;\n};\n\n/**\n * Wraps any chat tree that renders attachments. Required alongside\n * <ChatNameResolverProvider> for trees rendering <ChatShell>/<MessageList>.\n */\nexport function ChatAttachmentUrlProvider(props: ChatAttachmentUrlProviderProps) {\n  const { resolveAttachmentUrl, children } = props;\n  return (\n    <ChatAttachmentUrlContext.Provider value={resolveAttachmentUrl}>\n      {children}\n    </ChatAttachmentUrlContext.Provider>\n  );\n}\n\n/** Strict hook — throws if no provider is wrapped (missing setup must surface). */\nexport function useChatAttachmentUrlResolver(): ChatAttachmentUrlResolver {\n  const resolver = React.useContext(ChatAttachmentUrlContext);\n  if (!resolver) {\n    throw new Error(\n      \"[chat-react] ChatAttachmentUrlProvider is required. Wrap your ChatShell tree with <ChatAttachmentUrlProvider>.\"\n    );\n  }\n  return resolver;\n}\n"]}