Print

@wabbit/tome-print

Document assembly, a print-template registry, and Pandoc-driven PDF generation for structured reports (e.g. @wabbit/tome-deals' proposal/quote documents). domain layer per root ARCHITECTURE.md — zero @wabbit/* dependencies, consumed by @wabbit/tome-deals as an optional lazy layer (via hasLayer('@wabbit/tome-print'), not a hard import).

Install

pnpm add @wabbit/tome-print

No peer dependencies — this is a standalone Node package (document assembly + a CLI wrapper around two external binaries). It ships zero React and zero .tsx files.

External requirements — two system binaries, not one: the ./cli build path (tome-print bin → src/cli/build.ts) needs both:

1. Pandoc — Markdown → JSON AST (pandoc -t json). findPandoc() tries pandoc on PATH first, then known Windows install locations (%LOCALAPPDATA%\Pandoc\pandoc.exe, C:\Program Files\Pandoc\pandoc.exe); if none resolve, the CLI exits with an install-url error rather than a cryptic spawn failure.
2. WeasyPrint (Python) — HTML → PDF, invoked as a bare weasyprint shell command with no path-search fallback. If it's missing, build.ts catches the execSync failure and prints pip install weasyprint, then preserves the intermediate HTML at .tome-print-tmp/report.html next to the target PDF so the run isn't a total loss.

Neither binary is vendored by pnpm add — both are separate host installs.

60-second quickstart

import { registerPrintTemplate, assembleDocument, mapDocument, extractMeta } from '@wabbit/tome-print'

registerPrintTemplate('quote-line-item', (block, meta) => `<tr><td>${block.data.label}</td></tr>`)

const { meta, blocks } = mapDocument(pandocAst)         // ./mapper — frontmatter + AST → PrintBlock[]
const html = assembleDocument(blocks, meta, 'report.css') // ./document — 3 args: blocks, meta, CSS href for the <link>

CLI (Markdown → PDF via Pandoc + WeasyPrint, positional args — no subcommand, no flags):

pnpm exec tome-print ./report.md ./report.pdf   # output arg optional — defaults to <input-basename>.pdf beside the input

Set TOME_PRINT_WORDMARK=/abs/path/to/logo.svg before running the CLI to brand the editorial templates with a real wordmark; unset (or a missing file) falls back to a plain-text brand mark — the CLI warns but does not fail.

Public API

| Export | Subpath | Description | |---|---|---| | DocumentMeta, PrintBlock, PrintTemplate | ./types | Core shapes — PrintTemplate = (block, meta) => string | | registerPrintTemplate(slug, template) | ./registry | Register a template function for a block slug | | getPrintTemplate(slug), hasPrintTemplate(slug), getAllPrintTemplates() | ./registry | Registry lookups | | renderBlock(block, meta) | ./registry | Render one block via its registered template | | assembleDocument(blocks, meta, cssPath) | root (./document) | Walk a PrintBlock[] and assemble the final document HTML; cssPath is the stylesheet href written into the <link> tag (relative or absolute — the CLI resolves it to a temp-dir-local report.css before handing off to WeasyPrint) | | mapDocument(pandocAst) | root (./mapper) | Map a Pandoc AST to { meta, blocks } | | extractMeta(pandocAst) | root (./mapper/frontmatter) | Pull DocumentMeta out of a document's frontmatter | | renderInline, renderInlines | ./richtext | Inline-node renderers | | renderBlockNode, renderBlocks | ./richtext | Block-node renderers | | tome-print (bin) | ./cli | Pandoc-driven Markdown → PDF build CLI — parses <input.md> via pandoc -t json, maps the AST, assembles HTML, then renders to PDF | | Template registration side-effect | ./templates | import '@wabbit/tome-print/templates' registers every built-in template; assembleDocument also imports this internally |

Built-in templates (registered via ./templates's side-effect barrel)

editorial-opener, prose-section, pull-quote, signal-data-table, editorial-bridge, editorial-colophon, metric-strip, data-chart — one file per template under src/templates/, each calling registerPrintTemplate() at import time. A consumer's own block templates (e.g. a quote-line-item slug from a deal artifact) register the same way, either from an app-owned module imported once at startup or alongside ./templates's barrel.

Server / client posture

Not applicable — this package has no .tsx files and no React dependency at all. It's pure Node.js: Pandoc + WeasyPrint CLI orchestration (node:child_process, node:fs), AST mapping, and string-template rendering. Every export is safe to call from a build script, a Payload server hook, or a Node CLI; none of it can run in a browser bundle (it shells out to native binaries and touches the filesystem directly).

Extending

New print templates: registerPrintTemplate(slug, (block, meta) => htmlString), then import the registering module from ./templates's barrel so assembleDocument's internal import '@wabbit/tome-print/templates' picks it up as a side effect. New document sources beyond Pandoc AST would need a new ./mapper sibling implementing the same { meta, blocks } output shape consumed by assembleDocument.

Design history

• docs/superpowers/specs/2026-04-24-tome-print-layer-design.md — original design
• docs/claude-gotchas.md → Payload / Typing / Layer Design section — the cross-layer optional-lookup pattern @wabbit/tome-deals uses to reach this package (hasLayer() + lazy require(), never a static import) is documented under "Cross-layer runtime calls go through the layer registry, not dynamic import" and "registerLayer MUST use lazy require() in try/catch, never static import"