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

@immediately-run/platform-constants

v0.1.0

Published

The single source of truth for cross-repo platform vocabulary (the .immediately.run cache-zip sidecar layout). Consumed by cli, sandbox, and site-main so a rename/extension touches ONE package, not N repos in lockstep (R3-104).

Downloads

260

Readme

@immediately-run/platform-constants

The single source of truth for cross-repo platform vocabulary — currently the .immediately.run cache-zip sidecar layout: the contribute-manifest path, the pre-transpiled-artifacts directory, the bundled-packages directory, and the "is this path platform infrastructure?" predicate.

Why this exists (R3-104)

These values used to be copied as raw string literals into three repos:

| Repo | Previously hard-coded | |---|---| | cli (cache-zip emitter) | MANIFEST_SIDECAR_ENTRY, .immediately.run/artifacts/…, .immediately.run/packages/… | | sandbox (bundler readers) | MANIFEST_SIDECAR_PATH, BUNDLED_PACKAGES_DIR | | site-main (contribute diff / integrity allowlist) | PLATFORM_SIDECAR_INFRA_PREFIX |

Because the literal was duplicated, the .tinkerable/.immediately.run/ rename had to land in all three repos in lockstep (cli #12 / sandbox #30 / site-main #117). Owning the vocabulary here means a future rename or extension is one edit + a version bump, and a consumer that hard-codes the literal again is caught by each repo's check-no-sidecar-literal drift gate (ways_of_working §7).

Exports

import {
  SIDECAR_DIR,            // ".immediately.run"            (root-relative, no leading slash)
  SIDECAR_PREFIX,         // ".immediately.run/"           (prefix form)
  CONTRIBUTE_MANIFEST_PATH,// ".immediately.run/contribute-manifest.json"
  ARTIFACTS_DIR,          // ".immediately.run/artifacts"
  PACKAGES_DIR,           // ".immediately.run/packages"
  isUnderSidecar,         // (path) => boolean  (accepts a leading "/" or "./")
} from "@immediately-run/platform-constants";

Develop

npm ci
npm run build   # tsc → dist/
npm test        # jest
npm run lint

Published to npm on push to main via trusted publishing (OIDC) — see .github/workflows/ci.yml.