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

@bluewombat/implementer

v0.9.0

Published

Transformer: runs one Task — Builder, then Gates — until validated, escalated, or interrupted.

Readme

Implementer

Transformer: runs one Task in an existing workspace. It launches the Builder, then the Gate sequence it was given (possibly empty), and loops Attempts until the run is validated, escalated, or interrupted.

Behavioural contract: SPECS.md.

Stack

Repository stack — TypeScript, Node 24.20, Biome, node:test. See docs/DEVELOPMENT.md.

Setup

From the repository root:

nvm use
npm install

Commands

| Task | Command | | --------- | ---------------- | | Lint | npm run lint | | Format | npm run format | | Typecheck | npm run tsc | | Test | npm test | | Build | npm run build |

Binary after build: dist/cli.js (package bin name implementer).

Run

Workspace must already exist. Example with no Gates:

npm run build
node dist/cli.js \
  --id task-1 \
  --intention "do the work" \
  --workspace /absolute/path/to/workspace \
  --builder -- node /path/to/builder.js \
  --builder-timeout-ms 60000 \
  --max-attempts 3

Each child has its own ceiling: --builder-timeout-ms (required), and --gate-timeout-ms before each --gate. There is no Attempt clock and no Task clock.

Progress is JSON lines on stdout (status, attempt-started, builder-finished, gate-finished, attempt-finished, run-finished). Exit codes: 0 validated, 1 escalated, 2 invalid-invocation, 130 interrupted.

Import

Same Transformer, in process. cli.ts is an adapter over this function — it reads argv and stdin, calls runImplementer, and maps the outcome to an exit code. Nothing the CLI can do is unreachable from here.

import { runImplementer } from "@bluewombat/implementer";

const result = await runImplementer({
  invocation,                       // same shape the CLI builds from argv
  write: (line) => events.push(line), // progress as values, not stdout
});

src/index.ts exports runImplementer, its RunOptions / RunResult, ProgressWriter, and this Transformer's domain types.

Layout

SPECS.md                 behavioural contract
README.md                how to build and run
src/
  cli.ts                 entry
  types.ts               Transformer-owned types
  args/                  CLI parsing
  loop/                  pure Attempt-loop decisions
  status/                Status labels and --on-status
  progress/              JSON-line progress writer
  child/                 spawn, Builder, Gate
  run/                   invocation orchestration
fixtures/                fake Builder / Gate scripts for tests

Sources stay colocated: helpers used once live next to their caller.