pdfme/packages/jsx

@pdfme/jsx

Small JSX authoring layer for creating pdfme templates from stacking layout primitives.

/** @jsxImportSource @pdfme/jsx */
import { Document, MultiVariableText, Page, Stack, Text, renderToTemplate } from '@pdfme/jsx';

const { template, inputs } = await renderToTemplate(
  <Document margin={{ x: 12, y: 16 }}>
    <Page>
      <Stack gap={4}>
        <Text size={18}>Invoice</Text>
        <Text name="customerName">Alice</Text>
        <MultiVariableText
          name="message"
          text="Hello **{name}**, status: `{status}`"
          values={{ name: 'Alice **literal**', status: 'draft' }}
          textFormat="inline-markdown"
        />
      </Stack>
    </Page>
  </Document>,
);

This package emits regular pdfme Template and inputs values. It does not depend on React; it provides its own jsx-runtime and jsx-dev-runtime. renderToTemplate is async because automatic text height measurement may need font data.

MVP constraints

• Text and MultiVariableText heights are measured with pdfme's text/rich text wrapping helpers when height is omitted. Pass an explicit height when you need a fixed field box.
• Text textFormat="inline-markdown" is read-only only. Editable Text values use plain content.
• MultiVariableText uses text or children as the template string and stores values as the JSON input. Variable names are inferred from {name} placeholders and can also be passed with variables.
• Image uses src as its initial content and is intended to be self-closing.
• Svg uses svg or children as its initial content.
• With name, Image and Svg become input-backed schemas; without name, they are read-only content.
• Rectangle, Ellipse, and Line are static visual schemas for backgrounds, dividers, and simple shapes.
• Document is the root component for document-level settings and repeated static content. It can contain Header, Footer, Static, and Page children.
• Document props are defaults, not deep-merged style objects. If a Page specifies margin, size, orientation, or font, that Page value replaces the Document value for that prop. The generated blank basePdf.padding comes from the resolved margin of the first rendered page.
• Header and Footer render read-only content into blank basePdf.staticSchema. Header uses the top margin area and Footer uses the bottom margin area, so body content stays inside the Page margin frame.
• Static is a lower-level repeated overlay that uses full-page coordinates. It is useful for watermarks and other fixed page-coordinate content. Custom basePdf is not supported when document static content is present.

<Document size="A4" margin={{ x: 16, y: 18 }}>
  <Header>
    <Text height={8}>Header</Text>
  </Header>
  <Footer>
    <Text height={8}>Footer</Text>
  </Footer>
  <Page>
    <Text height={8}>Body</Text>
  </Page>
</Document>

• Header, Footer, and Static must be direct children of Document. They are intentionally not allowed inside Page, because they render into document-level staticSchema and are repeated on every page.
• Multiple Static blocks with the same placement are concatenated in declaration order. Top blocks start at the top of the page; bottom blocks are stacked together in declaration order and anchored to the page bottom, so the last bottom block sits at the page edge. If static content overlaps the header/footer/body areas, pdfme will draw the schemas in static schema order.
• Static content currently accepts read-only Stack, Row, Box, Spacer, Text, Image, Svg, Rectangle, Ellipse, and Line content. MultiVariableText, List, Table, input-backed schemas, and PageBreak are rejected.
• Absolute can be used inside Page, Header, Footer, top Static, or Box as a small manual placement escape hatch. It uses the parent layout frame as its coordinate origin and does not advance the surrounding stack/row flow. When width or height is omitted, it uses the remaining parent frame size from x / y. Direct Stack / Row support is intentionally left for later; wrap with an explicit-size Box when you need a local manual-placement frame inside flow content.

<Page margin={12}>
  <Text height={8}>Body starts here</Text>
  <Absolute x={120} y={0} width={60}>
    <Text height={6}>Top-right note</Text>
  </Absolute>
</Page>

• Layout children can use margin. Stack and Row support alignItems for simple cross-axis alignment without trying to implement full CSS/Flexbox.
• Stack and Row support justifyContent="start" | "center" | "end" | "space-between" for main-axis spacing. Stack uses this most predictably with an explicit height; Row uses it most predictably with an explicit width.
• Stack defaults to alignItems="stretch" to preserve full-width stacking. Use an explicit child width when you want alignItems="center" or "end" to visibly move that child.
• Row defaults to alignItems="start" and intentionally does not support cross-axis stretch yet.
• Row children can use flexGrow or flex as a grow weight. If width is also set, it is used as the basis before remaining width is distributed. flex is only a short alias for flexGrow, not the CSS flex shorthand.

<Row width={120}>
  <Text width={20} flex={1}>A</Text>
  <Text width={20} flex={3}>B</Text>
</Row>
// A width: 40, B width: 80

• flexGrow={0} without width produces a zero-width Row child.
• PageBreak is supported only along a Page / Stack / Box layout path. It is rejected inside Row, leaf schemas, List, and Table.
• All Page nodes in one renderToTemplate call must use the same page size, orientation, and margin because a pdfme blank basePdf has one shared size and padding.
• Table columnWeights are relative column width weights, not millimeter widths. They are normalized to pdfme headWidthPercentages, for example columnWeights={[70, 30]}. Missing or invalid weights default to 1, so pass one weight per column when you need exact ratios. Earlier beta builds used widths; use columnWeights going forward.