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

@intx/hub-common

v0.5.0

Published

Shared utilities for the Interchange hub packages

Readme

@intx/hub-common

Utilities shared across the hub packages. This package has a generic name and is therefore at risk of becoming a junk drawer. A new module belongs here only if it satisfies all of the following:

  1. It is genuinely needed by more than one of the hub packages (@intx/hub-api, @intx/hub-sessions, or future hub packages). Code used by exactly one package belongs in that package.
  2. It encodes hub-schema-owner knowledge that does not belong in @intx/types. For example, the id prefix table here is the identity namespace of the hub's database schema, so it lives with the schema owner. By contrast, a generic hex encoder belongs in @intx/types (and in fact @intx/types already owns one); do not duplicate it here.
  3. It is not session-plane logic, HTTP-surface logic, or a database concern -- those have dedicated packages.
  4. It depends only on node built-in modules. External dependencies signal that the code probably wants a more specific home.

If this package grows beyond a handful of small modules, that is a signal to find the real boundary, not to keep adding here.

See LAYOUT.md for the package layout this fits into.