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

@agent-ix/quire-wasm

v0.3.0

Published

WebAssembly bindings for quire-rs (parse, extract, validate) — powers spec-editor live preview.

Readme

quire-wasm

Discord

WebAssembly bindings for quire-rs — the parsing, extraction, and validation engine that powers the Filament/Quire spec-artifact ecosystem.

Purpose: give spec-editor and other browser/Node consumers the canonical parse/extract/validate pipeline so the editor agrees byte-for-byte with the quire CLI and the Python reference parser.

No render surface. The render/templating feature was removed from quire-rs (commit e0811a8). There is no render or renderFromBlob export; the module blob is { manifest, schemas } (no templates).

Public surface

import init, {
  parseDocument,
  extract,
  validate_archetype as validate,
  extractFromBlob,
  validateFromBlob,
} from "@agent-ix/quire-wasm";

await init(); // load the .wasm

const doc = parseDocument(md);

// Filesystem-rooted (Node target):
const records = extract("FR", "/path/to/module", md);
validate("FR", "/path/to/module", { id: "FR-001", /* ... */ }); // throws on violation

// In-memory module blob (browser / --target web):
const moduleBlob = {
  manifest: "<raw manifest.yaml text>",
  schemas: { "schemas/fr-frontmatter.schema.json": "<schema json>" },
};
const recs = extractFromBlob("FR", moduleBlob, md);
validateFromBlob("FR", moduleBlob, { id: "FR-001", /* ... */ });

Two shapes

  • Module-blob (extractFromBlob, validateFromBlob): pass an in-memory { manifest, schemas } object — the filesystem-free path used by --target web. Builds an inline Registry via quire_rs::Registry::from_inline_parts(manifest, schemas).
  • Filesystem-rooted (extract, validate_archetype): pass a moduleRoot path string. Works under wasm-pack --target nodejs (real fs) and any embedding that polyfills fs via WASI.

parseDocument is filesystem-free and works everywhere.

Install

npm install @agent-ix/quire-wasm   # from GitHub Packages

Build

make build       # wasm-pack build --target web --release  (browser)
make build-node  # wasm-pack build --target nodejs --release (Node)
make test        # wasm-pack test --node (extract/validate parity vs quire-rs)
make ci          # full local CI gate (fmt + lint + test + deny + audit)

wasm-pack is required: cargo install wasm-pack.

License

MIT