2.5.1

Support specifying Web browser flags

Control underlying Chromium flags via the following environment variable:

CHROMIUM_ARGS

2.5.0

Refactored code base, new /url endpoint, support setting PDF Information Dictionary

1. Switch from pdfjs to pdf-lib, since pdf-lib allows reading the Information Dictionary from existing documents, so we can automatically reuse those possibly set by Puppeteer#pdf (such as the title, derived from that of the HTML Document)

2. Add support for setting information from the PDF Information Dictionary:

   • title
   • author
   • subject
   • keywords
   • creator
   • producer
   • creationDate
   • modificationDate

3. Introduce /url endpoint to consume one or more URLs to generate pages from

4. Implement better error handling

5. Prepare the terrain for a future option to print as an image rather than a PDF

New Contributors

• @wiggisser made their first contribution in #28

Full Changelog: 2.4.0...2.5.0

2.4.0

What's Changed

• Build font information cache files on start-up
• Update runtime to Node 25
• Update dependencies to address potential vulnerabilities

Full Changelog: 2.3.2...2.4.0

2.3.1

• Improve QoL for maintainers
• Offer control over Web browser instance recycling
• Fix a couple of browser management hiccups

Full Changelog: 2.3.0...2.3.1

2.3.0

Perform merging in-memory for multi-page documents.

• Tidy up implementation
  • Use chaining for express app composition
  • Leverage express' built-in error handling mechanism
  • Move print to shared-browser.ts
  • Hand-roll .gitignore
  • Remove decommissioned rc file
• Drop tmp dependency
• Reinstate compose.sh
  • Use docker/buildx to build images for both amd and arm architectures
  • Update target registry to ghcr.io
  • Update pre-build procedure (to none!)
  • Update shebang to use /usr/bin/env
  • Fix resetting of shell output colour

Full Changelog: 2.2.0...2.3.0

2.2.0

• Minimise browser memory footprint
  • Lazily spawn chromium,
  • share its instance between requests,
  • debounce its teardown by 30 seconds
• Switch to using TypeScript
• Set up linting

2.1.2

Update all dependencies, simplify setup to lessen maintenance burden.

• Update chromium to latest stable version
• Polish codebase
• Update all deps
• Switch from node:alpine to node:slim
• Switch from npm to pnpm
• Don't bother with minifying/bundling code
• Keep browser open between prints
• Manually sanitise relevant query parameters

2.1.1

Ensure adequate .pdf extension for generated document

Only append the .pdf extension to the generated file name if it's missing.

What's Changed

• Fix double .pdf extension by @redbaron-gt in #11

Full Changelog: 2.1.0...2.1.1

2.1.0

Supporting both ARM and AMD architectures

With this version, we now offer images for both ARM and AMD architectures.
The image is now based on node:current-alpine and leverages chromium rather than google-chrome.

2.0.0

Breaking change from version 1.x.x:

The /multiple endpoint used to expect the request body to be a JSON object with a single pages property that would map to a JSON array of strings containing your HTML content for each page to be printed.
That endpoint now expects the JSON array directly.

• version 1.x.x

  {
    "pages": [
      "<h1>First Page</h1>",
      "<h1>Second Page</h1>"
    ]
  }

• version 2.x.x

  [
    "<h1>First Page</h1>",
    "<h1>Second Page</h1>"
  ]