@uniweb/press 0.4.8 → 0.4.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/press",
-  "version": "0.4.8",
+  "version": "0.4.10",
   "description": "Press your React components into downloadable files — Word, Excel, PDF. Registration-based pattern with lazy-loaded format adapters.",
   "type": "module",
   "exports": {

package/src/adapters/docx.js

@@ -510,6 +510,9 @@ function irToInlineChildren(node) {
             // a TextRun so the OOXML parent is <w:r>.
             return [new TextRun({ children: [new DocxTab()] })]
         case 'externalHyperlink':
+        // A plain <a href> from same-source JSX — same destination, same
+        // emitter. See the href note in ir/parser.js.
+        case 'a':
             return [irToExternalHyperlink(node)]
         case 'internalHyperlink':
             return [irToInternalHyperlink(node)]
@@ -612,10 +615,13 @@ function irToTextRunPair(node) {
 }
 
 function irToExternalHyperlink(node) {
+    // `link` is the data-* spelling (data-link); `href` arrives from a plain
+    // <a href>. Same destination either way.
+    const destination = node.link || node.href || ''
     const children = (node.children || []).flatMap(irToInlineChildren)
     return new ExternalHyperlink({
-        children: children.length ? children : [new TextRun({ text: node.link || '' })],
-        link: node.link || '',
+        children: children.length ? children : [new TextRun({ text: destination })],
+        link: destination,
     })
 }
 

package/src/adapters/epub.js

@@ -31,6 +31,7 @@
 import JSZip from 'jszip'
 import { parseFragment } from 'parse5'
 import { fetchAssets } from '../assets/fetch.js'
+import { MATH_CSS } from './math-css.js'
 
 // ============================================================================
 // Public API
@@ -625,4 +626,5 @@ pre {
   overflow: auto;
   white-space: pre-wrap;
 }
+${MATH_CSS}
 `

package/src/adapters/math-css.js

@@ -0,0 +1,45 @@
+/**
+ * @fileoverview The CSS a Temml-produced MathML document needs to lay out.
+ *
+ * Math arrives as MathML, which browsers render natively — so it is tempting
+ * to conclude, as this pipeline's own comments once did, that it carries no
+ * CSS dependency at all. It does, for two separate reasons:
+ *
+ * 1. **Temml emits class hooks and expects a stylesheet to define them.**
+ *    `tml-left` / `tml-right` carry the `&` column alignment of an `aligned`
+ *    environment, and `tml-jot` carries its extra row spacing. With nothing
+ *    defining them, a derivation's `=` signs do not line up and its rows sit
+ *    flush against each other. The declarations below are Temml's own, from
+ *    `Temml-Local.css`.
+ *
+ * 2. **`mtd` gets no vertical padding from the browser.** Temml's stylesheet
+ *    only *adjusts* row spacing for jot and small, on the stated assumption
+ *    that "default mtd top padding is 0.5ex per MathML-Core and user-agent
+ *    CSS". Measured in Chrome 2026-07, a pristine `mtd` gets 0px — so a
+ *    `pmatrix` or `cases`, which carries no `tml-*` class at all, renders with
+ *    its rows touching. Shipping Temml's stylesheet verbatim fixes the
+ *    derivation and leaves the matrix broken; the `math mtd` rule below is the
+ *    part Temml does not have.
+ *
+ * ── Why this is a string and not an imported stylesheet ──
+ *
+ * These adapters run in browser hosts as well as Node ones (see the host-
+ * supplied asset loaders in `assets/fetch.js`), so press cannot read a file at
+ * runtime, and it does not depend on `@uniweb/kit`. The same declarations
+ * therefore live in `kit/src/prose-tokens.css` for the browser lane.
+ *
+ * That is a duplicate, and duplicates drift — so it is pinned mechanically
+ * rather than by comment: `framework/_contracts/math-css-parity.test.js`
+ * parses both and fails when they disagree. Change one, change the other, or
+ * the contract test names it.
+ */
+
+export const MATH_CSS = `/* Temml's own class hooks — without these an aligned environment neither
+   aligns nor breathes. */
+.tml-right { text-align: right; }
+.tml-left { text-align: left; }
+.tml-sml-pad { padding-left: 0.05em; }
+/* Row spacing. The browser gives mtd no vertical padding, so state the
+   MathML-Core default here; Temml's own CSS only adjusts it for jot. */
+math mtd { padding-top: 0.5ex; padding-bottom: 0.5ex; }
+math mtable.tml-jot mtd { padding-top: 0.7ex; padding-bottom: 0.7ex; }`

package/src/adapters/pagedjs.js

@@ -231,6 +231,8 @@ export const DEFAULT_POLYFILL_URL =
  * book PDF without a custom foundation stylesheet. Foundations override by
  * passing `options.stylesheet`.
  */
+import { MATH_CSS } from './math-css.js'
+
 export const DEFAULT_STYLESHEET = `
 /* Hidden metadata block — the DOM carries it for CSS string-set / string() */
 [data-pagedjs-metadata] { display: none; }
@@ -292,4 +294,5 @@ blockquote {
 }
 ul, ol { margin: 0.5em 0 0.75em 1.5em; }
 figure { break-inside: avoid; }
+${MATH_CSS}
 `

package/src/adapters/typst.js

@@ -374,6 +374,7 @@ function blockNodeToTypst(node) {
             return inlineNodeToTypst(node)
 
         case 'link':
+        case 'a':
             return inlineNodeToTypst(node)
 
         case 'math':
@@ -526,7 +527,7 @@ function inlineNodeToTypst(node) {
         return text
     }
 
-    if (node.type === 'link') {
+    if (node.type === 'link' || node.type === 'a') {
         const href = node.href || ''
         const inner = inlineChildrenToTypst(node.children || [])
         return `#link(${quoteTypstString(href)})[${inner}]`

package/src/ir/parser.js

@@ -103,6 +103,22 @@ function nodeToIR(node) {
     const properties = attributesToProperties(node.attrs || [])
     const children = collectChildren(node)
 
+    // A plain <a href> carries its destination in a normal HTML attribute, not
+    // a data-* one, so attributesToProperties drops it. Foundations reach this
+    // shape by writing an ordinary anchor in JSX that serves both the browser
+    // preview and the compile input — the same-source property principles.md
+    // §8 asks us to pursue. Without the href the adapters still emit the link
+    // TEXT and silently lose the destination, which is precisely the
+    // preview/output drift that principle exists to eliminate.
+    //
+    // Only `href` is lifted, and only for an anchor: it is the one plain
+    // attribute whose document meaning is unambiguous. The IR stays data-*
+    // driven everywhere else.
+    if (type === 'a' && properties.href === undefined) {
+        const href = getAttr(node, 'href')
+        if (href) properties.href = href
+    }
+
     const obj = { type, ...properties }
 
     if (type === 'text') {