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

pscat

v0.6.3

Published

A PostScript interpreter in WebAssembly: render PostScript to pixels in the browser or Node, step by step if you like

Readme

pscat

A PostScript interpreter compiled to WebAssembly. Render PostScript to pixels in a browser or in Node, all at once or step by step so you can watch the program draw. It is the engine behind the pscat playground, and the same interpreter as the pscat crate and command-line tool.

npm install pscat

Node 22 or later, or any current browser. It is ESM only, ships TypeScript types, and has no dependencies and no install scripts.

Render a page

import { createRenderer } from 'pscat';

const r = await createRenderer();
const page = r.render(`
  0.2 0.4 0.9 setrgbcolor 72 72 288 288 rectfill
  /Helvetica-Bold findfont 36 scalefont setfont
  1 setgray 100 200 moveto (Hello) show
`, { width: 432, height: 432, dpi: 144 });

page.width;   // 864 (432 points at 144 dpi)
page.data;    // Uint8ClampedArray, RGBA, row by row from the top (the ImageData layout)
page.output;  // what the program printed with = == print stack pstack

In a browser, r.paintTo(canvas) draws the page into a <canvas> (resizing it), and r.imageData() returns an ImageData.

Watch it draw

for (const _ of r.frames(source, { width: 612, height: 792, budget: 300 })) {
  r.paintTo(canvas);                        // the page so far
  await new Promise(requestAnimationFrame); // one frame per step
}

frames() runs budget PostScript objects per iteration. To drive it yourself, call r.begin(source, options) and then r.step(budget) until it returns false.

Errors

import { PostScriptError } from 'pscat';

try {
  r.render('1 2 bogus');
} catch (e) {
  if (e instanceof PostScriptError) {
    e.errorName; // 'undefined'
    e.command;   // 'bogus'
    e.line;      // 1
    e.report;    // '%%[ Error: undefined; OffendingCommand: bogus; Line: 1 ]%%'
    e.output;    // what the program printed before the error
  }
}

The renderer stays usable after an error, and the page drawn up to the error can still be read.

Libraries and fonts

The pscat PostScript libraries are built in, so (lib/artkit.ps) run, (lib/graph.ps) run and the rest work with no network requests. The library guides describe them.

The only built-in fonts are the Liberation faces behind the standard base fonts (Helvetica, Times, Courier and their bold and italic styles). Any other font is loaded with addFont, named by its font pack file stem:

const bytes = await (await fetch('/fonts/EBGaramond-Regular.ttf')).arrayBuffer();
r.addFont('EBGaramond-Regular', bytes);
r.render('/Garamond findfont 24 scalefont setfont 72 72 moveto (Garamond) show');

The aliases work as they do with installed packs (/Garamond, /Palatino-Roman and so on), and so does the face's own PostScript name. The Korean, Japanese and Thai faces (NotoSansKR-Regular, NotoSansJP-Regular, NotoSansThai-Regular, NanumBrushScript-Regular) read their strings as UTF-8 when registered under those names. The font files come from the fonts-* pack archives on the releases page, each with its own licence. Fonts are registered per renderer.

API

| | | |---|---| | createRenderer({ wasm }?) | Load the interpreter and return a Renderer. Each one is a separate interpreter. wasm overrides where the module comes from: a URL, a Response, bytes or a WebAssembly.Module (in Node, also a file path). By default it is the package's pscat.wasm, found through new URL('./pscat.wasm', import.meta.url). Bundlers that rewrite that pattern handle it; if yours does not (Vite's dependency pre-bundling, for one: add pscat to optimizeDeps.exclude), pass wasm the module's URL. | | render(source, { width, height, dpi }?) | Run a program to completion on a fresh page and return { width, height, data, output }. source is a string or a Uint8Array. The page is in points (default 612x792, US Letter) at dpi (default 72, one pixel per point). | | begin(source, options?) | Queue a program on a fresh page. | | step(budget = 5000) | Run up to budget objects. Returns true while there is more to do. | | frames(source, { budget, ...page }?) | A generator of begin plus one step per iteration. | | width, height | The page size in pixels. | | output | What the program has printed since begin. | | pixels() | A copy of the page as RGBA bytes. | | image() | { width, height, data, output } for the page as it is now. | | imageData() | The page as an ImageData (browsers and workers). | | paintTo(canvas) | Draw the page into a canvas or OffscreenCanvas. | | addFont(name, bytes) | Make a TrueType or OpenType font available to findfont. | | PostScriptError | Thrown by render and step. It has errorName, command, line, report and output. |

There is no file system and no clock: usertime and realtime read 0. The browser guide has more.

Licence

(MIT OR Apache-2.0) AND OFL-1.1. The code is MIT or Apache-2.0, at your option (LICENSE-MIT, LICENSE-APACHE). The SIL Open Font License 1.1 (LICENSE-OFL) covers the font data compiled into pscat.wasm: the Liberation fonts (fonts/LICENSE) and the typewriter outlines generated from Courier Prime. THIRD_PARTY_NOTICES.md lists every component, and THIRD_PARTY_LICENSES.html holds the licences of the Rust crates compiled into the module.

The package's version matches the pscat crate's.