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

@quirelabs/rastra

v0.1.0

Published

An image toolkit for the browser: native decoders first, wasm only where the platform cannot.

Readme

rastra

An image toolkit for the browser. Native decoders first, wasm only where the platform cannot.

Status: 0.1, early. The API is frozen for 0.1 but not stable across 0.x.

Install

npm install rastra

Use

import { selectEncoder } from 'rastra';
import { probeCapabilities } from 'rastra/capability';

const report = await probeCapabilities();
const choice = selectEncoder('avif', report);

if (choice.available) {
  const bytes = await choice.encoder.encode({ data, width, height }, { quality: 70 });
}

choice.via is platform where the browser does the work and downloads nothing, or artifact where a wasm codec is fetched. choice.downloadBytes says what that costs before you commit to it. When it is not available you get what is missing rather than a failure later.

Serving the artifacts

Wasm codecs are separate files, served by your app with immutable caching:

import { setArtifactBase } from 'rastra';
setArtifactBase('/rastra/');

Copy node_modules/rastra/vendor/ to that path. Each artifact records its upstream source, version, licence and a hash per file in its artifact.json, and ARTIFACTS exposes the same records for generating a licence page.

Verifying it yourself

The capability report is built by decoding real fixtures and reading encoder output back, not by feature sniffing. Those fixtures are published, so you can re-run the same verification in your own browser:

import { FIXTURE_LOADERS, fixtureBytes } from 'rastra/fixtures';

Per-browser measurements from our own runs live in measurements/ in the repository, with the browser versions and dates they were taken.

Licence

MIT for the toolkit. Vendored codecs keep their own licences, recorded per artifact: Apache-2.0 for libavif, LGPL-3.0 for libheif. No GPL is shipped.