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

@schlessera/brain-render-template

v0.30.1

Published

Shared markdown/HTML → print-ready document shell for brain-kit (used by the UI's /api/render and the CLI's `brain render`)

Readme

@schlessera/brain-render-template

The shared document shell brain-kit wraps around content before it is rendered to PNG or PDF. Markdown in, a single self-contained HTML document out — inline CSS, system fonts, no external requests.

It is deliberately tiny and pure: marked and a stylesheet, no browser, no filesystem, no network. The rendering itself lives in @schlessera/brain-render-puppeteer.

Two callers share it, which is the point — a page shared from the app and a PDF produced on the command line are byte-identical for identical input:

  • @schlessera/brain-ui-serverPOST /api/render
  • @schlessera/brainbrain render

Usage

import { buildHtmlDocument } from "@schlessera/brain-render-template";

const html = buildHtmlDocument({
  content: "# Trip plan\n\nDay one: arrive.",
  contentType: "markdown",
  title: "Trip plan",
});

| Option | Default | Meaning | |---|---|---| | content | — | Markdown source or a fragment of HTML | | contentType | — | "markdown" parses; "html" passes through | | title | "Shared from Brain" | <title>, escaped | | allowHosts | [] | Image hosts the renderer will resolve |

Remote images

The renderer denies the page network access, so a remote <img> would render as a broken-image box. Those are replaced with a visible placeholder instead:

<span class="remote-image">[Matterhorn at dawn — not embedded]</span>

data: URIs are always left alone. To let specific hosts through, pass allowHosts and give the renderer the same list — this option only stops the placeholdering; it does not grant the page any access on its own.

Print behaviour

The stylesheet includes a @media print block that keeps tables, blockquotes, code blocks and diagrams from splitting across pages, and keeps headings with the content that follows them.