@danxbot/ui 7.9.8 → 8.0.0

package/dist/types/components/Markdown.d.ts

@@ -0,0 +1,35 @@
+import type { MdCodeRenderer } from "../lib/syntax/markdown";
+export interface CodeBlockProps {
+    code: string;
+    language?: string | null;
+    filename?: string;
+    /** Still filling — suppresses the copy button, which would copy a fragment. */
+    streaming?: boolean;
+    className?: string;
+}
+/**
+ * A fenced code block, rendered through the shared `CodeEditor` viewer.
+ *
+ * `view="source"` is pinned rather than left to `CodeEditor`'s own default:
+ * left alone, a fence whose language is literally `markdown` would flip
+ * `CodeEditor` into ITS OWN rendered-preview mode, so a ```markdown block
+ * quoted inside a document would render as prose nested inside prose instead
+ * of the literal source the author fenced off. Every other language already
+ * defaults to `"source"`, so this only changes behaviour for that one case.
+ */
+export declare function CodeBlock({ code, language, filename, streaming, className }: CodeBlockProps): import("react").JSX.Element;
+export interface MarkdownProps {
+    children: string;
+    className?: string;
+    /** Defaults to a `CodeEditor`-backed viewer with a copy button. */
+    renderCode?: MdCodeRenderer;
+}
+/**
+ * Renders a complete markdown string as a document.
+ *
+ * This is the general-purpose entry point — the one nearly every consumer
+ * wants: a card description, a comment, a retro field, a plan record. It
+ * parses ONCE per `children` change and hands the tree straight to
+ * `MarkdownNodes`; there is no second parser, no block-splitting of its own.
+ */
+export declare const Markdown: import("react").NamedExoticComponent<MarkdownProps>;

package/dist/types/components/chat/StreamingMarkdown.d.ts

@@ -0,0 +1,11 @@
+import { type MarkdownProps } from "../Markdown";
+export interface StreamingMarkdownProps extends Omit<MarkdownProps, "children"> {
+    children: string;
+}
+/**
+ * Blocks are memoised individually by `MarkdownNodes`' own reconciliation —
+ * see `Markdown`. What THIS wrapper adds is memoising the balance pass itself,
+ * so a re-render that does not change `children` (a sibling state update
+ * elsewhere in the message list) never re-scans the text.
+ */
+export declare const StreamingMarkdown: import("react").NamedExoticComponent<StreamingMarkdownProps>;

package/dist/types/index.d.ts

@@ -64,6 +64,7 @@ export { Progress, Meter, ProgressRing, type ProgressProps, type MeterProps, typ
 export { Stat, StatRow, Sparkline, type StatProps, type StatRowProps, type SparklineProps, type StatSize, type StatTrend, type StatSentiment, } from "./components/Stat";
 export { DataTable, TableEmptyState, CellStack, type DataTableProps, type TableDensity, } from "./components/Table";
 export { CodeEditor, CodeEditorToolbar, CodeEditorCaption, CodeEditorCopyButton, CodeEditorWrapToggle, CodeEditorViewSwitch, type CodeEditorProps, type CodeEditorToolbarProps, type CodeEditorView, } from "./components/CodeEditor";
+export { Markdown, CodeBlock, type MarkdownProps, type CodeBlockProps } from "./components/Markdown";
 export { MarkdownEditor, type MarkdownEditorProps, type MarkdownEditorHandle, } from "./components/MarkdownEditor";
 export { ReadMore, readMoreVariants, type ReadMoreProps } from "./components/ReadMore";
 export { MarkdownSurface, type SurfaceOptions, type Splice } from "./lib/markdown/surface";
@@ -97,7 +98,7 @@ export { Chat, ChatPopover, type ChatProps, type ChatPopoverProps, type ChatSurf
 export { Message, MessagePartView, ToolCall, ChatMarker, type MessageProps, type MessageAction, type MessagePartViewProps, type ToolCallProps, type ChatMarkerProps, } from "./components/chat/Message";
 export { MessageScroller, type MessageScrollerProps, } from "./components/chat/MessageScroller";
 export { Composer, type ComposerProps } from "./components/chat/Composer";
-export { Markdown, CodeBlock, type MarkdownProps, type CodeBlockProps } from "./components/chat/Markdown";
+export { StreamingMarkdown, type StreamingMarkdownProps, } from "./components/chat/StreamingMarkdown";
 export { Attachment, AttachmentAction, AttachmentList, AttachmentPreview, type AttachmentProps, type AttachmentActionProps, type AttachmentListProps, type AttachmentPreviewProps, type AttachmentLayout, } from "./components/chat/Attachment";
 export { ModelSelector, type ModelSelectorProps, type ChatModel, } from "./components/chat/ModelSelector";
 export { EffortControl, DEFAULT_EFFORT_LEVELS, type EffortControlProps, type EffortLevel, } from "./components/chat/EffortControl";

package/dist/types/lib/syntax/markdown/index.d.ts

@@ -1,4 +1,4 @@
 export { parseMarkdown } from "./parse";
 export { markdown } from "./grammar";
-export { MarkdownNodes, MarkdownImage, sanitizeHref } from "./render";
+export { MarkdownNodes, sanitizeHref } from "./render";
 export type { MdNode, MdInline, MdListItem, MdCell, MdAlign, MdCodeRenderer } from "./types";

package/dist/types/lib/syntax/markdown/render.d.ts

@@ -6,33 +6,6 @@ export interface MarkdownNodesProps {
     renderCode: MdCodeRenderer;
 }
 export declare function MarkdownNodes({ nodes, renderCode }: MarkdownNodesProps): ReactNode;
-/**
- * An inline image, capped to a compact thumbnail and click-to-enlarge.
- *
- * A screenshot dropped into a markdown field (a card comment, a problem
- * statement, a plan record) is the most common image this renders, and an
- * uncapped one would blow past the width of any of those surfaces and,
- * worse, a TALL one (a full-page screenshot) would still run on forever even
- * with a width cap alone — hence a HEIGHT cap here, not a width cap, with
- * `w-auto` left free to shrink for a narrow source image.
- *
- * Clicking opens the full-resolution image in a `Dialog` rather than
- * navigating or replacing the thumbnail in place, so the surrounding prose
- * never loses its layout while the image is being inspected.
- */
-/**
- * Exported so `components/chat/Markdown.tsx` — the streaming chat renderer,
- * which does NOT go through this file's node tree/parser — can reuse the
- * exact same capped, click-to-enlarge treatment instead of forking it. Two
- * markdown renderers exist in this package on purpose (streaming vs.
- * document); a shared leaf component is how they stay visually identical
- * without duplicating the cap/dialog logic.
- */
-export declare function MarkdownImage({ src, alt, title }: {
-    src: string;
-    alt: string;
-    title?: string;
-}): ReactNode;
 /**
  * RULE TWO, the implementation: a link's scheme is checked before it is
  * rendered.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@danxbot/ui",
-  "version": "7.9.8",
+  "version": "8.0.0",
   "type": "module",
   "description": "Danxbot — a domain-agnostic React design system with motion as a first-class primitive.",
   "license": "MIT",

package/dist/types/components/chat/Markdown.d.ts

@@ -1,22 +0,0 @@
-export interface CodeBlockProps {
-    code: string;
-    language?: string;
-    filename?: string;
-    /** Still filling — suppresses the copy button, which would copy a fragment. */
-    streaming?: boolean;
-    className?: string;
-}
-export declare function CodeBlock({ code, language, filename, streaming, className }: CodeBlockProps): import("react").JSX.Element;
-export interface MarkdownProps {
-    children: string;
-    className?: string;
-}
-/**
- * Blocks are memoised individually.
- *
- * A response is re-parsed on every token, so without this the reconciler
- * rebuilds every finished paragraph each time a word lands at the bottom —
- * which is both wasteful and visible, because re-created DOM loses selection.
- * Someone highlighting a sentence while the answer continues keeps it.
- */
-export declare const Markdown: import("react").NamedExoticComponent<MarkdownProps>;