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

meta-language

v0.46.0

Published

JavaScript implementation of the meta-language links-network core

Readme

meta-language (JavaScript)

JavaScript npm Node.js Version License: Unlicense

JavaScript implementation of the meta-language links-network core. It is the JavaScript half of the meta-language multi-language project; the Rust crate lives in ../rust.

The package mirrors the Rust operation families used by the parity registry: parse, query, transform, substitute, serialize, snapshot, translate, and verify. It is intentionally dependency-light and uses links-notation for LiNo and link-cli-style substitution text plus peggy for generated parser modules.

Feature parity with the Rust crate is enforced by ../parity/language-features.json and the npm run check:parity gate (see Parity below).

Usage

import {
  LinkNetwork,
  LinkQuery,
  ParseConfiguration,
  ReplacementRule,
} from 'meta-language';

const network = LinkNetwork.parse(
  'const oldName = call(oldName);\n',
  'JavaScript',
  ParseConfiguration.default(),
);
const query = LinkQuery.fromSexpression(`
  (identifier) @target
  (#eq? @target "oldName")
`);

network.replace(
  network.find(query),
  ReplacementRule.capturedText('target', 'newName'),
);

console.log(network.reconstructText());
// const newName = call(newName);

Parity

Every feature in ../parity/language-features.json must be implemented in both Rust and JavaScript. npm run check:parity validates the manifest, confirms each cell's evidence files exist, and asserts the JavaScript API_OPERATIONS registry covers every operation family and API style. The same check runs in both js.yml and rust.yml, so a change to one language that is not mirrored in the other fails CI.

Development

npm ci
npm test
npm run check:parity
npm pack --dry-run