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

@imprentajs/react

v0.1.0-alpha.11

Published

Declare an Imprenta document in React.

Readme

@imprentajs/react

Declare a PDF or a spreadsheet as React components. A real reconciler, not a tree walk: components, hooks and context all work, and what comes out is Imprenta's IR rather than HTML.

npm i @imprentajs/react@alpha
import { B, Document, Table, Text, render } from '@imprentajs/react/pdf';

const Invoice = ({ number, items }) => (
  <Document margin={40}>
    <Text size={22}><B>FACTURA</B></Text>
    <Text size={11}><B>{number}</B></Text>
    <Table
      columns={[{ width: 46 }, { width: 'auto' }, { width: 90, align: 'end' }]}
      header={{ cells: [{ text: 'Ref.' }, { text: 'Concepto' }, { text: 'Importe' }] }}
      rows={items.map((i) => ({ cells: [{ text: i.ref }, { text: i.concept }, { text: i.total }] }))}
    />
  </Document>
);

const ir = await render(<Invoice number="FV-2026-00418" items={items} />);

Hand that IR to @imprentajs/pdf.

One import path per format

@imprentajs/react/pdf and @imprentajs/react/xlsx are separate sets of elements on purpose. A page is measured and painted by the engine; a sheet is a value and a type that Excel draws later. A shared <Text> would carry props that silently do nothing in one of the two, which is the failure this design refuses.

It depends on React and nothing else

Not on the engine. A document can be declared anywhere — a browser, a worker, a machine where the engine is not installed — and rendered somewhere else entirely.

Tailwind

className works. No CSS is involved at any point: a class is looked up and a number or a colour comes out. A class the page cannot honour — flex, hover:, w-1/2 on a box — is an error by name at render time, not a document that quietly came out wrong.

Status

Alpha. It works and is built test-first, but the API is not settled.

Apache-2.0 · github.com/imprenta-project/imprenta