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

@pithyjs/pidl-catalog

v0.1.0-beta.2

Published

Machine-readable component contracts for PithyJS — props, types, defaults, slots and a11y guarantees as JSON.

Readme

@pithyjs/pidl-catalog

Machine-readable component contracts for PithyJS.

A PIDL spec is a JSON document declaring a component's props, types, defaults, slots, events and accessibility guarantees. The catalog is what lets tooling reason about a component without reading its source: the props panels, the AI content projector and the registry generator all read these same files.

Coverage is partial and growing — IconButton, Tooltip, Popover, NavLink and ErrorBoundary have no spec yet.

Beta. Published under the beta tag alongside the rest of the PithyJS packages. The spec shape is still moving; pin an exact version.

Install

npm install @pithyjs/pidl-catalog@beta

What is in it

Specs ship at dist/specs/, organised by atomic level (atoms/, layout/, organisms/, sections/). Enumerate them from ALL_PIDL_SPECS rather than relying on a count in prose — this file cannot recount itself when a spec lands.

A spec's top level looks like this:

{
  "kind": "component",
  "id": "ui.button",
  "name": "Button",
  "level": "atom",
  "domain": "actions",
  "description": "...",
  "props": { /* name -> type, default, constraints */ },
  "events": { /* ... */ },
  "slots": { /* ... */ }
}

Usage

import { ALL_PIDL_SPECS } from '@pithyjs/pidl-catalog';

Design-intelligence tables are separate entry points, so importing one does not pull the others:

import { COLOR_PSYCHOLOGY_GUIDANCE } from '@pithyjs/pidl-catalog/color-psychology';
import { MUTATION_VOCABULARY } from '@pithyjs/pidl-catalog/mutation-vocabulary';
import { DESIGN_INTELLIGENCE_RULES } from '@pithyjs/pidl-catalog/design-intelligence';

Available subpaths: design-intelligence, mutation-vocabulary, and the *-psychology tables for color, typography, spacing, radius, shadows, motion and borders.

Why it exists

A component library documented only in prose forces every tool that consumes it to guess — at which props exist, which values are legal, and which accessibility rules are non-negotiable. PIDL makes those machine-checkable, so "the model never writes CSS" can be enforced by the build rather than asked for in a prompt.

License

MIT