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

@build-qube/papyra-pdfjs

v0.7.1

Published

A pdf.js engine for papyra's viewer, for pages that cannot run papyra's wasm

Readme

@build-qube/papyra-pdfjs

A pdf.js engine for papyra's PDF viewer.

papyra's own engine renders in WebAssembly with shared memory, so its page has to be cross-origin isolated. Some pages never are — an Android or iOS WebView, an app that embeds third-party content, a host that cannot set headers. This engine runs the same viewer on pdf.js there.

Install

npm install @build-qube/papyra-pdfjs @build-qube/papyra pdfjs-dist

@build-qube/papyra (0.5.0 or later) and pdfjs-dist are peer dependencies, so the app holds one copy of each; pdf.js is not loaded until the first document opens.

Use

Name it in the viewer's engine provider. With a list, the first engine that can run on the page wins — papyra's where the page is isolated, pdf.js everywhere else:

import { defaultPdfEngine } from '@build-qube/papyra/engine';
import { PdfjsEngine } from '@build-qube/papyra-pdfjs';
import { PdfEngineProvider } from '@/components/pdf-engine';

const pdfjs = new PdfjsEngine({
  workerSrc: new URL('pdfjs-dist/build/pdf.worker.mjs', import.meta.url).toString(),
});

<PdfEngineProvider engine={[defaultPdfEngine, pdfjs]}>{app}</PdfEngineProvider>;

Or call it directly, like any papyra engine:

const doc = await pdfjs.open(file);
const page = await pdfjs.render(doc, 0, { fitWidth: 800 }).promise; // ImageBitmap
for await (const match of pdfjs.search(doc, 'invoice')) console.log(match.page);

document passes options to every getDocument — standardFontDataUrl, cMapUrl and wasmUrl tell pdf.js where to find the fonts, character maps and decoders it does not bundle. pdfjs swaps the module, for the legacy build.

How it differs from papyra's engine

  • Pages are ImageBitmaps rendered into an OffscreenCanvas; paintToCanvas takes them as they are.
  • Text positions are exact at the edges of each pdf.js text item and evenly spread inside it, since pdf.js reports one width per item. Search and highlights work; a highlight in the middle of a word can be a little off.
  • No structure tree (tagged-PDF reading order), so the viewer hides that panel. undecodedGlyphs is always 0: pdf.js does not report text it could not decode.
  • A render nobody is waiting for any more is cancelled part-way through.
  • fingerprint is papyra's content hash, so a document has the same key on both engines.