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

qipdo

v0.1.0

Published

Run a chain of QIP components on input

Readme

qipdo

qipdo runs a chain of QIP Content components on input: each component's output becomes the next one's input. It is qipx run without the subcommand. It requires Node.js 22 or newer.

echo '<b>hi</b>' | npx qipdo qip.dev text/html/html-escape.wasm
npx qipdo qip.dev -i page.md text/markdown/markdown-basic.wasm -o page.html
npx qipdo --dry-run qip.dev text/markdown/markdown-basic.wasm

Options

| Option | Meaning | | --- | --- | | -i, --input <path> | Read input from a file instead of stdin | | -F, --form <name=value> | Add a form field, or a typed related part with -i (repeatable) | | -o, --output <path> | Write output to a file instead of stdout | | -u, --uniform <name=value> | Set a uniform on the preceding component (repeatable) | | --max-memory <bytes> | Reject modules whose declared memory exceeds bytes | | --strict-capacities | Fail when a step's output capacity exceeds the next step's input capacity | | --dry-run | Check the chain without reading input or rendering | | -h, --help | Show help | | --version | Show the qipdo version |

Hosts

Dotted DNS names such as qip.dev before the first component are hosts. Options may come before or after them, so qipdo --dry-run qip.dev a.wasm and qipdo qip.dev --dry-run a.wasm are the same. The last positional argument is always a component.

A relative .wasm path is read locally if it exists; a missing one is downloaded from the hosts in order over HTTPS and saved, as qipx does. This applies to components and to -F @path and -F '<path' fields.

Capacities

Every component has a fixed input and output capacity. By default a step may declare a larger output capacity than the next step's input capacity: --dry-run prints a note, and a run fails only when the real intermediate output doesn't fit. --strict-capacities turns the mismatch into an error before anything runs.

qipdo is its own implementation with no dependencies. It shares a test suite with qipx run and the Rust qipx, so all three behave the same.

Documentation: https://qip.dev/docs/content-component