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

@avodado/export

v0.2.9

Published

Export an Avodado Document to HTML or PDF.

Downloads

5,411

Readme

@avodado/export

HTML and PDF export for Avodado documents. Browser concerns are isolated here, not in @avodado/core or @avodado/render.

Install

pnpm add @avodado/export @avodado/core
npx playwright install chromium      # one-time, only if you need PDF

playwright is an optionalDependency so installing without Chromium stays light for HTML-only consumers. For PDF you can also let it self-provision: call toPdf(doc, { autoInstallBrowser: true }) (or use installChromium()) to download the matching Chromium on first use — this is what the avo CLI does, so versions never drift.

Usage

import { parseDocument } from '@avodado/core';
import { toHtml, toPdf } from '@avodado/export';

const doc = parseDocument(markdown, 'orders');
const html = toHtml(doc);             // string
const pdf = await toPdf(doc, { format: 'A4' });  // Uint8Array
await writeFile('orders.pdf', pdf);

API

  • toHtml(doc) — delegates to @avodado/render. Returns a standalone HTML string.
  • toPdf(input, opts?)input is a Document or pre-rendered HTML string. Launches headless Chromium via Playwright, sets the HTML, prints to PDF. Browser closed in finally.
  • isChromiumAvailable()Promise<boolean>. True only if playwright is installed AND the Chromium binary exists on disk. Use to gate optional PDF code paths.

PDF options

toPdf(doc, {
  format: 'A4' | 'Letter',           // default A4
  margin: { top, right, bottom, left },
});