npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@satzstrom/primitives

v0.1.4

Published

React primitives for paginated Satzstrom documents

Readme

@satzstrom/primitives

React components and types for Satzstrom documents.

npm install @satzstrom/primitives react react-dom

The package includes document, page, flow, sequence, reference, footnote, and mathematics primitives. It contains no native renderer implementation.

Document metadata is optional and absent fields are omitted from the PDF. PDF/UA-1 output requires a usable title. In a custom PageMaster layout, Flow and Footnotes are the accessibility boundaries: layout branches outside it are hidden automatically unless an intentional branch uses aria-hidden="false".

Markdown

Markdown renders unstyled semantic HTML from GitHub Flavored Markdown. Inline and display formulas use the same KaTeX-backed Math primitive as JSX-authored formulas. Raw HTML and MDX are not supported. Use $x+y$ inline, $$ on separate lines for display math, and \$ for a literal dollar sign.

Use String.raw to keep LaTeX backslashes readable. Markdown follows standard indentation rules, so keep the template content flush left.

import { Document, Markdown, Page } from "@satzstrom/primitives";

export default function Report() {
  return (
    <Document title="Fibonacci" lang="en">
      <Page>
        <Markdown>{String.raw`
# Fibonacci

The relation is $F_n=F_{n-1}+F_{n-2}$.

$$
F_n=\left[\frac{1}{\sqrt 5}\varphi^n\right]
$$
`}</Markdown>
      </Page>
    </Document>
  );
}

Footnote accessibility text follows the language set on Document. Use Markdown.labels when a document needs different wording.

Footnote placement

Place one <Footnotes /> outside <Flow /> in your PageMaster layout, or inside a fixed <Page>. Footnotes require this placeholder. It accepts normal aside attributes, className and style, but no children. It is hidden when empty and inherits typography without a separator or fixed spacing.

A flex column with <Flow style={{ flex: 1, minHeight: 0 }} /> followed by <Footnotes style={{ maxHeight: "20%" }} /> shares a definite page height between text and notes. Give the parent a definite height for percentage limits. The layout controls appearance and maximum height; Satzstrom assigns and breaks the content. Long notes continue in the same PageMaster. Fixed Pages report overflow.

Markdown and JSX notes share numbering. Repeated Markdown calls link to the first note; backlinks return to the calls. Missing or multiple placeholders produce diagnostics.