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

parsanol

v0.10.3

Published

PARG artifact runtime for TypeScript — checksum-verified artifact load, wasm parse, bindings, schema-driven materialization

Readme

parsanol

The PARG artifact runtime for TypeScript: load a checksum-verified .parg artifact, parse through the parsanol wasm engine, apply the artifact's bindings, and materialize schema-driven models.

The engine is the vendored parsanol wasm build (vendor/parsanol-wasm/, nodejs target) — no grammar code lives here; the baked artifact is the contract.

Usage

import { PargRuntime } from "parsanol";

// PARG_ARTIFACT_DIR (or an explicit dir) holds the baked artifacts.
const rt = PargRuntime.load("iso", undefined, process.env.PARG_ARTIFACT_DIR);

const bound = rt.parseAndBind("ISO 5537:2025");   // bound capture map
const shape = rt.parseShape("ISO 5537:2025");     // parsanol-shape tree
const text = rt.renderString("ISO 5537:2025");    // F6 render

Construction throws unless the artifact's embedded checksum verifies.

Vendored engine freshness

vendor/parsanol-wasm/BUILT_FROM records the parsanol-rs commit the wasm was built from; scripts/check-wasm-freshness.sh fails when parsanol-rs has moved. Refresh with npm run refresh-wasm.

Conformance

PargRuntime parses with the same wasm binary the Rust and Ruby engines validate against, so artifact-level conformance is inherited: any baked artifact that passes its embedded tests on the other engines passes here identically. Run the runtime tests with PARG_ARTIFACT_DIR=<artifacts> npm test (the artifact-gated case skips when no artifacts dir is set).