jamdesk 1.1.207 → 1.1.208

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jamdesk",
-  "version": "1.1.207",
+  "version": "1.1.208",
   "description": "CLI for Jamdesk — build, preview, and deploy documentation sites from MDX. Dev server with hot reload, 50+ components, OpenAPI support, AI search, and Mintlify migration",
   "keywords": [
     "jamdesk",

package/vendored/components/mdx/CodeGroup.tsx

@@ -1,4 +1,12 @@
-'use client';
+// Deliberately NOT 'use client'. CodeGroup reads its children as elements, so
+// it must see them BEFORE React Server Components renders them. As a client
+// component it received what MdxPreBlock (a server component) had already
+// turned each fence into: a bare <pre> for an untitled fence, but a whole
+// titled CodePanel for a titled one. Nothing below recognises the latter, so
+// in production every titled fence fell out of the tab strip. Run on the
+// server, it gets the raw MdxPreBlock elements, the same shape its tests
+// build. The browser half lives in CodePanel, which stays a client component.
+// Pinned by the directive test in __tests__/components/CodeGroup.test.tsx.
 
 import { ReactNode, ReactElement, Children, Fragment, cloneElement, isValidElement, memo } from 'react';
 import { CodePanel, CodePanelTab } from '../ui/CodePanel';
@@ -161,8 +169,10 @@ const CODE_FENCE_MARKER = 'jdCodeFenceMarker';
  * the child is not a fence at all.
  *
  * Two layers have to be peeled, and the pre-fix filter (`child.type ===
- * 'pre'`) saw through neither, which is why no <CodeGroup> in production
- * ever rendered a tab strip:
+ * 'pre'`) saw through neither, so no <CodeGroup> rendered a tab strip
+ * outside RSC (the editor preview, tests). Under RSC it only ever caught
+ * untitled fences, as host <pre> elements; see the note at the top of the
+ * file:
  *
  *  1. Compiled MDX hands each fence over wrapped in a single-child
  *     Fragment, not as the fence element directly.
@@ -194,6 +204,21 @@ function unwrapCodeFence(child: ReactNode): ReactElement | null {
   return null;
 }
 
+/**
+ * Whether MdxPreBlock will render this fence as its own captioned panel.
+ * Mirrors MdxPreBlock's `if (!dataTitle)` branch exactly, and only for the
+ * marked MdxPreBlock element: a hand-built host <pre> never takes that
+ * branch, whatever attributes it carries.
+ */
+function isTitledMdxFence(block: ReactElement): boolean {
+  const { type } = block;
+  return (
+    typeof type === 'function' &&
+    (type as unknown as Record<string, unknown>)[CODE_FENCE_MARKER] === true &&
+    Boolean((block.props as PreProps)['data-title'])
+  );
+}
+
 /**
  * Children that are neither code fences nor the blank text nodes MDX emits
  * between block children. These are rendered after the panel so a
@@ -237,6 +262,17 @@ export const CodeGroup = memo(function CodeGroup({ children }: CodeGroupProps) {
     return <div>{children}</div>;
   }
 
+  // A lone titled fence keeps the caption-only panel production has always
+  // shown for it, through the same fallback as above. While CodeGroup was a
+  // client component it never recognised a titled fence, so this is the only
+  // rendering such a group has ever had; tabbing it would add a one-tab
+  // language strip under the caption on every page that wraps a single
+  // titled fence in <CodeGroup>. Fence titles become tab labels only where
+  // there is more than one fence to switch between.
+  if (codeBlocks.length === 1 && isTitledMdxFence(codeBlocks[0])) {
+    return <div>{children}</div>;
+  }
+
   const extras = allChildren.filter(isRenderableExtra);
 
   // Extract title from first code block (only shown for single blocks)