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

@microscope-js/renderer-pdf

v0.1.5

Published

PDF renderer for microscope-js (uses pdfjs-dist)

Downloads

209

Readme

@microscope-js/renderer-pdf

npm Bundle Types Provenance

PDF renderer for microscope-js, powered by pdfjs-dist v5. All parsing + canvas painting happens inside a Web Worker — the main thread stays responsive.

Install

pnpm add @microscope-js/renderer-pdf

pdfjs-dist is a real dependency (not a peer) so consumers get a deduplicated copy.

Use

import { createRegistry, mount } from '@microscope-js/core';
import { pdfRenderer } from '@microscope-js/renderer-pdf';

const registry = createRegistry([pdfRenderer]);
const handle = await mount({ source: file, container, registry });

// renderer-specific capabilities
const cap = handle.capabilities as { pageCount: number; scrollToPage(n: number): void };
console.log(cap.pageCount);
cap.scrollToPage(42);

Options

Pass via mount({ options: { … } }) or <Viewer options={{ … }} />.

| Option | Default | Description | | ------------ | -------------------- | ------------------------------------------------------ | | maxBytes | 256 * 1024 * 1024 | Reject PDFs larger than this (MicroscopeError('TOO_LARGE')) | | maxPages | 5000 | Cap pages rendered — defends against PDF bombs | | scale | 1.25 | Canvas render scale (also DPR-aware for crisp text) | | workerSrc | bundled | Override pdf.worker.mjs URL (e.g. self-host on CDN) |

Capabilities exposed on the RenderHandle

interface PdfHandle extends RenderHandle {
  readonly capabilities: {
    pageCount: number;
    scrollToPage(n: number): void;
  };
}

Security model

  • pdfjs v5 disables runtime JS evaluation by default — no eval-style path is ever taken.
  • disableAutoFetch: true — never re-fetches over the network during render.
  • All rendering happens in the user's browser. The PDF byte stream never leaves the tab.
  • The worker is sandboxed to its own thread; a malformed PDF can't read the main page's DOM or globals.
  • maxBytes / maxPages defaults defend against pathological inputs ("PDF bombs").

Bundle notes

The pdfjs worker is loaded via new URL('pdfjs-dist/build/pdf.worker.mjs', import.meta.url). Webpack 5, Vite, and Next.js handle that asset-module pattern out of the box. If you ship behind a CDN, pass options.workerSrc to point at your own hosted copy.

See also

License

MIT