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

@autono/open-pdf

v0.14.0

Published

Runtime and CLI for open-pdf — live real-PDF preview, click-to-comment inspector, and export to PDF or editable Word.

Readme

@autono/open-pdf

Runtime and CLI for open-pdf — the PDF framework built for agents. Documents are React components; the dev server renders them to real PDF bytes on every save, so the preview you see in the browser is the file you ship.

Install

Most workspaces get this installed by the scaffolder:

npm create @autono/open-pdf@latest my-docs

Use this package directly only when wiring up an existing workspace by hand:

pnpm add @autono/open-pdf

To update an existing workspace to the latest version (and sync its agent skills):

npx open-pdf update

What's inside

  • Dev server + viewer — renders actual PDF bytes (Takumi engine in a web worker) with sub-second re-renders on save. Doc list, page navigation, download.
  • Inspect mode — press i, click any element on the page to see its exact source line and leave a comment. Comments persist as @pdf-comment markers in the source, ready for a coding agent to apply.
  • Vite plugin — discovers docs/<id>/index.tsx, exposes docs via virtual modules, hot-reloads on add/remove.
  • Export CLI — the same bytes as the preview, headless. --format docx produces an editable Word file (real text, not page images); --format md produces Markdown. The viewer's Export menu offers all three.
  • Agent skills — file-based skills (create-doc, apply-comments, …) that sync into workspaces; no MCP server required.

CLI

Once installed, the open-pdf bin is available in the workspace:

| Command | Description | | --- | --- | | open-pdf dev | Start the dev server. Flags: -p, --port <port>, --host [host], --open, --no-skills-check. | | open-pdf build | Build a static site. Flags: --out-dir <dir> (defaults to dist). | | open-pdf preview | Preview the production build. Flags: -p, --port <port>, --host [host], --open. | | open-pdf export [docs...] | Render docs to files: PDF (same bytes as the preview), editable DOCX, or Markdown. Flags: --out-dir <dir> (defaults to export), --format <pdf\|docx\|md>. | | open-pdf sync:skills | Sync built-in agent skills into this workspace. Flags: --dry-run. | | open-pdf update | Update @autono/open-pdf to the latest version and sync skills. Flags: --force, --no-skills. |

Authoring

A document is one folder under docs/ with an index.tsx that default-exports a React component. Style with Tailwind via the tw prop; content flows and the engine paginates.

import { PageNumber, TotalPages } from '@autono/open-pdf';
import type { PageOptions } from '@autono/open-pdf';

export const pageOptions: PageOptions = {
  size: 'a4',
  margin: { top: 56, bottom: 72 },
  footer: (
    <span tw="flex w-full justify-end text-[10px]">
      Page <PageNumber /> of <TotalPages />
    </span>
  ),
};

export default function Doc() {
  return (
    <main tw="flex flex-col">
      <h1 tw="text-[30px] font-bold">Hello, open-pdf</h1>
      <p tw="mt-4">This paragraph is real PDF text.</p>
    </main>
  );
}

export const meta = { title: 'Hello' };

Exports

import {
  PageNumber,        // resolved by the PDF engine in header/footer bands
  TotalPages,
  TargetPageNumber,
  type DocComponent,
  type DocMeta,
  type DocModule,
  type PageOptions,
  type PageFont,
  type PageMarginSide,
  type OpenPdfConfig,
} from '@autono/open-pdf';

The Vite plugin is exposed under a subpath for advanced setups:

import { createViteConfig } from '@autono/open-pdf/vite';

Config

Create open-pdf.config.ts in the workspace root (all fields optional):

import type { OpenPdfConfig } from '@autono/open-pdf';

const openPdfConfig: OpenPdfConfig = {
  docsDir: 'docs',
  port: 5173,
  base: '/', // set to '/my-docs/' to host the built site under a subpath
};

export default openPdfConfig;

Docs

Full documentation: docs.openpdf.sh

License

MIT