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 🙏

© 2024 – Pkg Stats / Ryan Hefner

pdfjs-serverless

v0.4.2

Published

Serverless build of PDF.js for Deno, workers, and other nodeless environments

Downloads

933

Readme

pdfjs-serverless

A redistribution of Mozilla's PDF.js for serverless environments, like Deno Deploy and Cloudflare Workers with zero dependencies. The whole export is about 1.4 MB (minified).

PDF.js Compatibility

[!NOTE] This package is currently using PDF.js v4.0.379.

Installation

Run the following command to add pdfjs-serverless to your project.

# pnpm
pnpm add pdfjs-serverless

# npm
npm install pdfjs-serverless

# yarn
yarn add pdfjs-serverless

Usage

Since PDF.js v4, the library migrated to ESM. Which is great. However, it also uses a top-level await, which is not supported by Cloudflare workers yet. Therefore, we have to wrap all named exports in a function that resolves the PDF.js library:

declare function resolvePDFJS(): Promise<typeof PDFJS>

So, instead of importing the named exports directly:

// This will NOT work at the moment
import { getDocument } from 'pdfjs-serverless'

We have to use the resolvePDFJS function to get the named exports:

import { resolvePDFJS } from 'pdfjs-serverless'

const { getDocument } = await resolvePDFJS()

[!NOTE] Once Cloudflare workers support top-level await, we can remove this wrapper and re-export all PDF.js named exports directly again.

🦕 Deno

import { resolvePDFJS } from 'https://esm.sh/pdfjs-serverless'

// Initialize PDF.js
const { getDocument } = await resolvePDFJS()
const data = Deno.readFileSync('sample.pdf')
const doc = await getDocument({
  data,
  useSystemFonts: true,
}).promise

console.log(await doc.getMetadata())

// Iterate through each page and fetch the text content
for (let i = 1; i <= doc.numPages; i++) {
  const page = await doc.getPage(i)
  const textContent = await page.getTextContent()
  const contents = textContent.items.map(item => item.str).join(' ')
  console.log(contents)
}

🌩 Cloudflare Workers

import { resolvePDFJS } from 'pdfjs-serverless'

addEventListener('fetch', (event) => {
  event.respondWith(handleRequest(event.request))
})

async function handleRequest(request) {
  if (request.method !== 'POST')
    return new Response('Method Not Allowed', { status: 405 })

  // Get the PDF file from the POST request body as a buffer
  const data = await request.arrayBuffer()

  // Initialize PDF.js
  const { getDocument } = await resolvePDFJS()
  const doc = await getDocument({
    data,
    useSystemFonts: true,
  }).promise

  // Get metadata and initialize output object
  const metadata = await doc.getMetadata()
  const output = {
    metadata,
    pages: []
  }

  // Iterate through each page and fetch the text content
  for (let i = 1; i <= doc.numPages; i++) {
    const page = await doc.getPage(i)
    const textContent = await page.getTextContent()
    const contents = textContent.items.map(item => item.str).join(' ')

    // Add page content to output
    output.pages.push({
      pageNumber: i,
      content: contents
    })
  }

  // Return the results as JSON
  return new Response(JSON.stringify(output), {
    headers: { 'Content-Type': 'application/json' }
  })
}

How It Works

First, some string replacements of the PDF.js library is necessary, i.e. removing browser context references and checks like typeof window. Additionally, we enforce Node.js compatibility (might sound paradox at first, bear with me), i.e. mocking the canvas module and setting the isNodeJS flag to true.

PDF.js uses a worker to parse and work with PDF documents. This worker is a separate file that is loaded by the main library. For the serverless build, we need to inline the worker code into the main library.

To achieve the final nodeless build, unenv does the heavy lifting by converting Node.js specific code to be platform-agnostic. This ensures that Node.js built-in modules like fs are mocked.

See the rollup.config.ts file for more information.

Inspiration

  • pdf.mjs, a nodeless build of PDF.js v2.

License

MIT License © 2023-PRESENT Johann Schopplich