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

donobu

v6.0.1

Published

Set a project up for Donobu (@donobu/test) with `npx donobu init`, then run its CLI.

Readme

donobu

The public entry point for Donobu, the AI-powered browser-testing library. The library itself, @donobu/test, is served from Donobu's private npm registry, so a fresh project needs a little setup before it can install the package or the coding-agent skill that ships inside it. This package is that setup:

npx donobu@latest init

The @latest matters: a bare npx donobu reuses whatever the npx cache or a global install already has, which may be the legacy 5.x library.

What init does

Idempotent, so re-run it whenever something is off.

  1. Writes the two .npmrc lines that route @donobu/* to the private registry. The auth line reads the key from DONOBU_API_KEY in the form the project's package manager understands: pnpm gets a :-unset fallback, because pnpm discards the whole file when the variable is missing, while npm, bun, and yarn get plain ${DONOBU_API_KEY}, because they do not expand the fallback form and would send it literally as the token.
  2. Makes sure .gitignore covers .env.
  3. Finds your Donobu API key in the environment or the project's .env. Without one it stops here, with instructions, and exits with code 2. Keys are created at https://www.donobu.com/home/keys.
  4. Installs @donobu/test as a devDependency with the project's package manager (detected from the packageManager field or the lockfile).
  5. Sets "prepare": "donobu skills install || exit 0" so the agent skill refreshes on every install. An existing prepare script is left alone and reported.
  6. Hands off to the installed CLI: donobu skills install writes the skill to .claude/skills/donobu and .agents/skills/donobu, and donobu status confirms the cloud identity behind the key.

Your key is written to .env (git-ignored) for the Donobu CLI to read. Note that package managers read .npmrc substitutions from the shell environment, not from .env, so export DONOBU_API_KEY before pnpm install and add it as a secret in CI.

Every other command

donobu <anything else> runs the @donobu/test CLI installed in the project: donobu test, donobu heal, donobu status, and the rest. Once the library is installed, npx donobu resolves to it directly.

Do not add this package to a project's dependencies. It is meant for npx, pnpm dlx, or a global install, and it shares the donobu bin name with the library.

For coding agents

Paste this into Claude Code, Codex, or any other agent working in the project:

Set up Donobu in this project by running `npx donobu@latest init` and
following its output. If it stops for an API key, tell me and wait; do not search for a key
or ask me to paste one into this conversation. When init finishes, read the
installed skill at .claude/skills/donobu/SKILL.md before writing or running
tests. Use no other installation method.