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

@dbx-tools/devkit

v0.1.96

Published

Readme

@dbx-tools/devkit

Scaffold, formatting, codegen, verification, build, and release helpers for Bun + workspaces monorepos. It wraps the shared tsdown config for building and a Bun-based publish flow; devkit keeps only the workspace automation that is orthogonal to writing package code.

Installation

bun add -d @dbx-tools/devkit

Then point your root package.json scripts at the devkit bin for the helper commands you want:

{
  "scripts": {
    "format": "devkit format",
    "build": "devkit build",
    "codegen": "devkit codegen",
    "verify": "devkit verify",
    "create": "devkit create",
    "release": "devkit release",
    "tag": "devkit tag",
  },
}

Commands

| Command | What it does | | ------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | devkit format | syncpack format, regroup lifecycle hooks, then prettier --write. | | devkit build | Compile every publishable package with the shared tsdown config. | | devkit codegen | Regenerate each package's generated/ zod tree from the .d.ts inputs its package.json declares. | | devkit verify | Fail on imports of sibling packages not declared as dependencies. | | devkit create [--plugin\|--shared] <slug> | Scaffold a new package under packages/<slug>/. | | devkit release [--dry-run] | Build, then publish each package with a stamped (complete) manifest. | | devkit tag [patch\|minor\|major] | Version bump, commit, tag, push, and create a GitHub Release. --notes-since v0.1.75 widens the notes baseline; default is the previous tag. --no-ai-notes skips Codex release notes. | | devkit agent [prompt] | Run ucode codex exec (-t / --timeout seconds). Prompt via args or stdin. Requires ucode codex --version. |

Typecheck stays a plain tsc call:

tsc --noEmit -p tsconfig.json

Configuration

Configuration is optional. Everything is auto-derived from the workspace; the only knobs live under a devkit key in the root package.json:

{
  "devkit": {
    "scope": "@acme", // npm scope used by `create` (default: most common scope in the workspace)
    "repo": "acme/widgets", // owner/name for release links (default: the `origin` git remote)
  },
}

Each package's optional codegen.inputs field is read by convention.

Library API

The same commands are exported as functions for projects that want to compose their own automation:

import { build, codegen, create, release, tag, verify } from "@dbx-tools/devkit";

await build();
await codegen();
await verify();
await create({ slug: "example" });
await release({ dryRun: true });
await tag({ bump: "patch", publish: false });

Also exported: format, plus the workspace helpers (discoverPackages, discoverPackageJsons, writeJson, getProject, sh, git, ...).

License

Apache-2.0