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

@tomerlichtash/md-registry

v0.1.0

Published

Entity registry for markdown corpora: alias map, polymorphic byline resolution, unknown-ref policy, zod reference()

Readme

@tomerlichtash/md-registry

Entity registry for markdown corpora — the thing Astro's reference() does for content collections, but framework-free. One canonical record per entity (author, translator, subject), an alias map from display strings to ids, polymorphic byline resolution, and a per-call-site policy for unknown refs.

Core has zero dependencies and does no file I/O: it takes a plain entries array from any loader (@tomerlichtash/md-collections, your own, mocks).

import { createRegistry } from '@tomerlichtash/md-registry';

const people = createRegistry(entries, { nameField: 'name', aliasField: 'aka' });

// frontmatter `author:` may be a legacy free string, an id, or a list of ids
people.resolveDisplay(page.author, { join: ' & ', override: page.display_author });
people.idsOf(page.author);                    // → ['ada-quill']

// unknown-ref policy per call site
people.resolveRef('rio-marsh', { onUnknown: 'error' });        // typo fails the build
people.resolveRef('rio-marsh', { onUnknown: 'passthrough' });  // legacy strings flow through
people.resolveRef('rio-marsh', { onUnknown: 'unresolved' });   // placeholder for unknowable identities

Names can be plain strings or per-locale records ({ en, fr }); pass defaultLocale and/or a locale per call. An alias shared by two entities resolves to both — the combined-credit split. The building blocks (buildAliasMap, resolveDisplay, idsOf) are also exported as pure functions.

./reference — zod helper

import { reference } from '@tomerlichtash/md-registry/reference';

refs: z.array(reference(() => people)); // parse-time build fail on a typo'd id

zod is a peer dependency of this subpath only. Only want validation? z.string().refine((id) => knownIds.has(id)) covers it without this package.