jamdesk 1.1.195 → 1.1.196

package/dist/lib/frontmatter-text.d.ts

@@ -4,8 +4,14 @@
  * Frontmatter is whatever YAML decided, not what the author meant:
  * `description: 404` parses to a number and `description: 2026-01-01` to a
  * Date. Both reach surfaces that accept only strings — react-markdown asserts
- * on `children` and THROWS in development, `.trim()`/`.replace()` throw
- * outright, and `<meta name="description">` would carry `[object Object]`.
+ * on `children` and THROWS in development, and `.trim()`/`.replace()` throw
+ * outright.
+ *
+ * What this does NOT do is make every malformed shape presentable. A YAML
+ * mapping still coerces to `[object Object]` and a sequence to `a,b`, because
+ * the alternative — returning '' — hides an authoring mistake behind an empty
+ * page rather than a visibly wrong one. The contract is only that no input
+ * makes a caller throw.
  *
  * The same is true of a dereferenced OpenAPI spec, which is why ApiMarkdown
  * calls this too: the ISR loader runs SwaggerParser.dereference, NOT .validate

package/dist/lib/frontmatter-text.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"frontmatter-text.d.ts","sourceRoot":"","sources":["../../src/lib/frontmatter-text.ts"],"names":[],"mappings":"AAYA;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CAItD"}
+{"version":3,"file":"frontmatter-text.d.ts","sourceRoot":"","sources":["../../src/lib/frontmatter-text.ts"],"names":[],"mappings":"AAYA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,wBAAgB,eAAe,CAAC,KAAK,EAAE,OAAO,GAAG,MAAM,CActD"}

package/dist/lib/frontmatter-text.js

@@ -15,8 +15,14 @@
  * Frontmatter is whatever YAML decided, not what the author meant:
  * `description: 404` parses to a number and `description: 2026-01-01` to a
  * Date. Both reach surfaces that accept only strings — react-markdown asserts
- * on `children` and THROWS in development, `.trim()`/`.replace()` throw
- * outright, and `<meta name="description">` would carry `[object Object]`.
+ * on `children` and THROWS in development, and `.trim()`/`.replace()` throw
+ * outright.
+ *
+ * What this does NOT do is make every malformed shape presentable. A YAML
+ * mapping still coerces to `[object Object]` and a sequence to `a,b`, because
+ * the alternative — returning '' — hides an authoring mistake behind an empty
+ * page rather than a visibly wrong one. The contract is only that no input
+ * makes a caller throw.
  *
  * The same is true of a dereferenced OpenAPI spec, which is why ApiMarkdown
  * calls this too: the ISR loader runs SwaggerParser.dereference, NOT .validate
@@ -34,8 +40,17 @@
 export function frontmatterText(value) {
     if (value === null || value === undefined || value === '')
         return '';
-    if (value instanceof Date)
+    // An out-of-range Date still satisfies `instanceof`, and toISOString() throws
+    // RangeError on it — the one input that would make this function do the very
+    // thing it exists to prevent. js-yaml cannot produce one (its timestamp
+    // resolver builds through Date.UTC, which rolls over rather than going
+    // invalid) and JSON.parse produces no Dates at all, but a JS caller can:
+    // Firestore's Timestamp.toDate() on out-of-range seconds, or a reviver.
+    // Falling through yields "Invalid Date" — visibly wrong, which is the right
+    // failure for a coercion whose contract is that it never throws.
+    if (value instanceof Date && !Number.isNaN(value.getTime())) {
         return value.toISOString().slice(0, 10);
+    }
     return String(value);
 }
 //# sourceMappingURL=frontmatter-text.js.map

package/dist/lib/frontmatter-text.js.map

@@ -1 +1 @@
-{"version":3,"file":"frontmatter-text.js","sourceRoot":"","sources":["../../src/lib/frontmatter-text.ts"],"names":[],"mappings":"AAAA,gDAAgD;AAChD,EAAE;AACF,uEAAuE;AACvE,EAAE;AACF,+EAA+E;AAC/E,6EAA6E;AAC7E,4EAA4E;AAC5E,4EAA4E;AAC5E,yEAAyE;AACzE,8EAA8E;AAC9E,4EAA4E;AAE5E;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,eAAe,CAAC,KAAc;IAC5C,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,KAAK,SAAS,IAAI,KAAK,KAAK,EAAE;QAAE,OAAO,EAAE,CAAC;IACrE,IAAI,KAAK,YAAY,IAAI;QAAE,OAAO,KAAK,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;IACnE,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC;AACvB,CAAC"}
+{"version":3,"file":"frontmatter-text.js","sourceRoot":"","sources":["../../src/lib/frontmatter-text.ts"],"names":[],"mappings":"AAAA,gDAAgD;AAChD,EAAE;AACF,uEAAuE;AACvE,EAAE;AACF,+EAA+E;AAC/E,6EAA6E;AAC7E,4EAA4E;AAC5E,4EAA4E;AAC5E,yEAAyE;AACzE,8EAA8E;AAC9E,4EAA4E;AAE5E;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,UAAU,eAAe,CAAC,KAAc;IAC5C,IAAI,KAAK,KAAK,IAAI,IAAI,KAAK,KAAK,SAAS,IAAI,KAAK,KAAK,EAAE;QAAE,OAAO,EAAE,CAAC;IACrE,8EAA8E;IAC9E,6EAA6E;IAC7E,wEAAwE;IACxE,uEAAuE;IACvE,yEAAyE;IACzE,wEAAwE;IACxE,4EAA4E;IAC5E,iEAAiE;IACjE,IAAI,KAAK,YAAY,IAAI,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC,EAAE,CAAC;QAC5D,OAAO,KAAK,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC;IAC1C,CAAC;IACD,OAAO,MAAM,CAAC,KAAK,CAAC,CAAC;AACvB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jamdesk",
-  "version": "1.1.195",
+  "version": "1.1.196",
   "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/markdown-classes.ts

@@ -91,13 +91,25 @@ export const API_DESCRIPTION_PROSE = [
  * tempting to read as redundant — the page already wraps its content in
  * `.prose` (render-doc-page.tsx `proseClasses`), so every `.prose <descendant>`
  * rule reaches the element anyway — but `.prose` also sets `font-size` on the
- * element it matches (themes/jam/variables.css, themes/pulsar/variables.css),
+ * element it matches (themes/jam, themes/pulsar, themes/halo),
  * and that is a different question from inheritance: the div carries `text-sm`,
  * and `.prose` only outranks it by being UNLAYERED where Tailwind utilities sit
  * in `@layer utilities`. Drop the class and `text-sm` wins, taking the
- * operation description from 16px to 14px on the default theme. The themes that
- * set no `.prose` font-size (base, nebula, halo) are the reason `text-sm` has to
- * stay too — it is the fallback, not the intended size.
+ * operation description from 16px to 14px on jam (the default), pulsar and
+ * halo. `text-sm` has to stay too: base and nebula set no `.prose` font-size
+ * at all, so for them it is the size that actually renders.
+ *
+ * Audit those rules with a selector-agnostic search, not `^\.prose` — jam and
+ * halo write theirs as `body[data-theme="..."] .prose`, and an anchored grep
+ * reports both as clean.
+ *
+ * Font-size is not all of it, either. Below 1024px `.api-page-layout .prose`
+ * (themes/base.css) switches this element to `display: flex; flex-direction:
+ * column`, so its paragraph margins stop collapsing and start adding. That
+ * predates the consolidation — the old inline string carried `prose` too — but
+ * it means the class is a layout switch as well as a type size, and removing
+ * it changes the narrow-viewport rendering on every theme, not just the three
+ * that set a `.prose` font-size.
  *
  * `prose-sm` and `dark:prose-invert` went with the inline version and are not
  * coming back: they are Tailwind Typography modifiers and this build has no

package/vendored/lib/frontmatter-text.ts

@@ -16,8 +16,14 @@
  * Frontmatter is whatever YAML decided, not what the author meant:
  * `description: 404` parses to a number and `description: 2026-01-01` to a
  * Date. Both reach surfaces that accept only strings — react-markdown asserts
- * on `children` and THROWS in development, `.trim()`/`.replace()` throw
- * outright, and `<meta name="description">` would carry `[object Object]`.
+ * on `children` and THROWS in development, and `.trim()`/`.replace()` throw
+ * outright.
+ *
+ * What this does NOT do is make every malformed shape presentable. A YAML
+ * mapping still coerces to `[object Object]` and a sequence to `a,b`, because
+ * the alternative — returning '' — hides an authoring mistake behind an empty
+ * page rather than a visibly wrong one. The contract is only that no input
+ * makes a caller throw.
  *
  * The same is true of a dereferenced OpenAPI spec, which is why ApiMarkdown
  * calls this too: the ISR loader runs SwaggerParser.dereference, NOT .validate
@@ -34,6 +40,16 @@
  */
 export function frontmatterText(value: unknown): string {
   if (value === null || value === undefined || value === '') return '';
-  if (value instanceof Date) return value.toISOString().slice(0, 10);
+  // An out-of-range Date still satisfies `instanceof`, and toISOString() throws
+  // RangeError on it — the one input that would make this function do the very
+  // thing it exists to prevent. js-yaml cannot produce one (its timestamp
+  // resolver builds through Date.UTC, which rolls over rather than going
+  // invalid) and JSON.parse produces no Dates at all, but a JS caller can:
+  // Firestore's Timestamp.toDate() on out-of-range seconds, or a reviver.
+  // Falling through yields "Invalid Date" — visibly wrong, which is the right
+  // failure for a coercion whose contract is that it never throws.
+  if (value instanceof Date && !Number.isNaN(value.getTime())) {
+    return value.toISOString().slice(0, 10);
+  }
   return String(value);
 }

package/vendored/workspace-package-lock.json

@@ -2925,9 +2925,9 @@
       "license": "MIT"
     },
     "node_modules/electron-to-chromium": {
-      "version": "1.5.412",
-      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.412.tgz",
-      "integrity": "sha512-z4rMe3esBzlzovKHj4gxJnsCGZRK5l4baUvm+gCGJBPE+gsyUMKsuU9tnEUtI1dOebXz1ytAPGjvXhmQ7rIPwA==",
+      "version": "1.5.413",
+      "resolved": "https://registry.npmjs.org/electron-to-chromium/-/electron-to-chromium-1.5.413.tgz",
+      "integrity": "sha512-F1XPKvt7HVfly5WND90ec16nFsdr4g5x/cVUP3EqjeyXynupabGDqpMa84wwvuYGDnldXLBz6DLXyZXWO9TPvw==",
       "license": "ISC"
     },
     "node_modules/enhanced-resolve": {
@@ -4446,9 +4446,9 @@
       }
     },
     "node_modules/mermaid": {
-      "version": "11.17.0",
-      "resolved": "https://registry.npmjs.org/mermaid/-/mermaid-11.17.0.tgz",
-      "integrity": "sha512-Jo9N377Wb4MSnHFPTbLi2SxFpsQl4eVHoxnW5U1Md9EazvgMp3s+4ohDxr81YNTgbn5Kj7HJ3yslrSJ52kwpbA==",
+      "version": "11.17.1",
+      "resolved": "https://registry.npmjs.org/mermaid/-/mermaid-11.17.1.tgz",
+      "integrity": "sha512-G1BP6qU4BRwEGk2SdsxgDk1cSuApimT32Nkb52YRSv+856FrmB8qo28BaNk9Ee8Fvuon3OxpXDJ4L6cD5AykXg==",
       "license": "MIT",
       "dependencies": {
         "@braintree/sanitize-url": "^7.1.2",