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

@aigamo/catalog

v0.0.1-alpha.76

Published

Shared pnpm catalog for @aigamo projects, generated from hydrangean-diva's pnpm-workspace.yaml.

Readme

@aigamo/catalog

The shared pnpm catalog for @aigamo projects.

catalog.json is generated from frontend/pnpm-workspace.yaml — that workspace file is the single source of truth. This package just snapshots the catalog so other repositories can consume the same dependency versions.

Consuming it

In any repo, run one command:

pnpm dlx @aigamo/catalog && pnpm install

That's it. It brings your pnpm-workspace.yaml catalog: block up to the shared versions (creating the block if needed), then pnpm install applies them. Run the same command again whenever you want to pick up newer versions.

It only touches deps your repo actually uses — a dep counts as used if it's already in your catalog, or referenced via catalog: in any package.json:

  • for each used dep, takes the shared version (adds if missing, updates if changed), so a fresh repo just needs to reference catalog: and sync,
  • never adds shared deps you don't use,
  • keeps your own project-specific entries,
  • removes nothing; leaves minimumReleaseAge, allowBuilds, packages, ordering and comments untouched.

Why a command and not automatic on install? pnpm doesn't run a dependency's install scripts unless you allow-list them, and a catalog change only takes effect on the next pnpm install anyway — so one explicit command is both simpler and less surprising.

CI check (optional)

pnpm dlx @aigamo/catalog --check writes nothing and exits non-zero when your catalog is out of sync, so CI can fail if someone forgot to run the sync. The raw data is also exported at @aigamo/catalog/catalog.json if you'd rather script it yourself.

Regenerating locally

pnpm --filter @aigamo/catalog build

The publish workflow runs pnpm build before nx release publish, so a publish always ships the current catalog.