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

@panomapp/drs

v1.2.0

Published

Dependency Resolver — single config for local path vs registry dependency specifiers.

Readme

@panomapp/drs

Dependency Resolver — single drs.config.json for local file: vs registry specifiers across consumers.

Quickstart

Write drs.config.json with "defaults": { "mode": "auto" }, then:

# From monorepo root
npx drs build
# or
npm run drs:build

That is the only command you need for day-to-day work: updates consumer package.json files, builds local packages when needed, runs npm install in each consumer, and verifies drift.

What auto does

| Where | auto + layout: sibling | auto + layout: vendored | |-------|-----------------------------|-----------------------------| | Your machine (paths exist) | file:../local-package + build at source | file:./generated_modules/... + sync/build vendored copies | | CI (CI=true) | registry.version from config | vendored local paths (standalone repos) | | Machine, path missing | registry | registry |

No need to set DRS_MODE for the usual local vs CI split when using the default sibling layout.

Vendored layout

Set "defaults": { "layout": "vendored" } (or per-consumer "layout": "vendored") to copy local packages into each consumer's generated_modules/ directory, build them there, and rewrite package.json to file:./generated_modules/....

drs build with vendored layout:

  1. Builds source packages at the monorepo root (when needed)
  2. Syncs sources into {consumer}/generated_modules/
  3. Copies built dist/ artifacts into vendored copies
  4. Runs validation/build steps inside vendored packages (prebuilt, missing dist, etc.)
  5. Updates consumer package.json files and runs npm install

Package entry fields:

| Field | Purpose | |-------|---------| | to | Consumer slugs that receive vendored/source copies; others get registry.version | | only-source | When a consumer is in to, never fall back to registry | | prebuilt | Source is synced into generated_modules/; dist packages build at source and copy dist/; validation-only packages (pack:check) validate in the vendored copy |

Configure vendoring directory/excludes:

{
  "vendoring": {
    "dir": "generated_modules",
    "exclude": [".git", "node_modules", "dist"]
  }
}

Programmatic vendoring API:

import { loadConfig, getVendoringPlan, syncVendoredModules, buildVendoredModules } from '@panomapp/drs';

const config = loadConfig();
const plan = getVendoringPlan(config, '/path/to/consumer');
syncVendoredModules(config, '/path/to/consumer');
buildVendoredModules(config, '/path/to/consumer');

Incremental dev sync:

drs build --if-stale

Compares source trees against generated_modules/, checks for missing dist/, and skips the full build when everything matches.

Config

{
  "$schema": "./node_modules/@panomapp/drs/schema/drs.config.schema.json",
  "version": 1,
  "root": ".",
  "defaults": { "mode": "auto" },
  "packages": {
    "@panomapp/my-pkg": {
      "local": { "path": "packages/my-pkg", "build": "npm run build" },
      "registry": { "version": "^1.0.0" }
    }
  },
  "consumers": {
    "app": {
      "dir": "apps/my-app",
      "dependencies": ["@panomapp/my-pkg"]
    }
  }
}

Modes

| Mode | Behavior | |------|----------| | local | Always file:<path> (fails if path missing) | | registry | Always registry.version | | auto | CI → registry with sibling layout; vendored layout stays local in CI |

Environment (overrides)

| Variable | Description | |----------|-------------| | DRS_CONFIG | Path to config file | | DRS_MODE | Force global mode (local / registry / auto) | | DRS_PACKAGE_@panomapp__my-pkg | Per-package mode (/__) |

Example: everything local except one package from npm:

DRS_MODE=local DRS_PACKAGE_@panomapp__hsm-panom-contract=registry drs build

CLI

drs build [--dry-run] [--skip-install] [--verbose]
drs resolve [--print human|json]
drs apply [--dry-run] [--build] [--install]
drs check
drs init
drs docker

GitHub Actions

- uses: actions/checkout@v4
- run: npm ci && npm run build
  working-directory: panom-drs
- run: npm install
- run: npx drs build

auto detects CI and uses registry specifiers; npm install in consumers pulls from npm.

Programmatic API

import { loadConfig, build } from '@panomapp/drs';

const config = loadConfig();
const result = build(config);

Panom

Root drs.config.json. Primary script:

npm run drs:build

Legacy deps:link-local in frontend → npm run drs:build from repo root.

Publishing

cd panom-drs
npm test && npm run build
npm version minor   # or patch
npm publish --access public