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

questline

v0.1.1

Published

Durable, crash-safe work queue and TUI for CLI coding agents (claude, pi, codex, …): leases with fencing, heartbeats, retries with backoff, dependencies, priorities, scheduling, dedupe, per-attempt telemetry.

Readme

⚒ questline

A durable, crash-safe work queue and TUI for CLI coding agents — Claude Code, pi, codex, or anything with a print mode. Queue tasks, run them through your agent, and never lose work to a crashed session.

  • Leases with fencing — every claim gets a versioned lease; a dead worker's stale writes are rejected, so work never runs twice or gets clobbered.
  • Heartbeats + reclamation — if a process dies, its lease expires and any other session picks the work up (at-least-once).
  • Bounded retries with exponential backoff, priorities, dependencies (a quest waits for the quests it depends on), not-before scheduling, and idempotent dedupe keys.
  • Per-attempt telemetry kept in SQLite: who ran it, how long, what happened.
  • Daemon mode drains the queue continuously (one scheduler per project, enforced by a scheduler lease — run it on two machines against a shared disk and only one drains).
  • Zero-dependency TUI dashboard: filters, search, details, run/retry/cancel.

Install

npm install -g questline     # needs node >= 22

Quick start

cd your-project
questline add build "Write unit tests for src/parser.ts" --name tests
questline run                # claims + executes via your agent, prints result
questline dash               # TUI: ↑↓ select · ←→ filter · / search · ⏎ details · r/R/x

Queue several and let the daemon drain them:

questline add explore "Map this codebase" --priority 5
questline add build "Fix the flaky test" --max-attempts 3
questline add review "Review the diff" --depends q-abc12345
questline daemon             # runs everything, respecting priority/deps/backoff

The executor: bring your own agent

By default quests run through Claude Code: claude -p "<task>". Configure any agent in ~/.questline/config.json (global) or <project>/.questline.json (per project):

{
  "executor": { "command": ["claude", "-p", "{task}"], "timeoutMs": 900000 },
  // or: { "command": ["pi", "--mode", "text", "{task}"] }
  // or: { "command": ["codex", "exec", "{task}"] }
  "executors": {                       // optional per-role override
    "review": { "command": ["claude", "-p", "--model", "opus", "{task}"] }
  }
}

Placeholders: {task} (includes context), {context}, {project}, {role}. The command runs with the quest's project as cwd; stdout is the stored result; exit 0 = done, non-zero or timeout = failed (and retried if the quest has attempts left).

Commands

| | | |---|---| | add <role> "task" | --name --priority N --context TEXT --depends id1,id2 --max-attempts N --not-before ISO --dedupe-key KEY --retain | | list / show <id> | queue table (--json) / full detail with result and telemetry | | run [id] | claim next eligible (or a specific quest) and execute now | | daemon | drain continuously; Ctrl-C releases cleanly | | dash | interactive TUI | | cancel / retry / consume <id> | cancel queued work / requeue failed work with one more attempt / release a retained result's dedupe key | | events / runs <id> | audit journal / per-attempt telemetry | | health | DB integrity + queue counts |

Config reference

{
  "dbPath": "~/.questline/quests.sqlite",  // point at pi's journal to share its queue
  "maxHistory": 500,
  "leaseTtlMs": 120000,
  "heartbeatMs": 30000,
  "maxAttempts": 1,                          // default per-quest retry budget
  "backoffBaseMs": 30000,
  "scheduler": { "pollMs": 5000, "maxConcurrent": 2 },
  "executor": { "command": ["claude", "-p", "{task}"], "timeoutMs": 900000 }
}

Quests are per-project (keyed by the directory you run commands in), stored in one SQLite database (WAL). Compatible with the pi-fairy-tales quest journal — set dbPath to ~/.pi/agent/fairy-tales-quests.sqlite and questline and pi share one queue.

License

MIT