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

@runbit/devtools

v0.1.1

Published

Zero-instrumentation observability. The runtime already emits every event — devtools folds them into per-run traces.

Readme

@runbit/devtools

Zero-instrumentation observability. The runtime already emits every event — devtools folds them into per-run traces.

npm install @runbit/devtools
import { runtime } from "@runbit/runtime";
import { devtools } from "@runbit/devtools";

const app = runtime();
app.use(devtools());   // that's the whole setup

await app.run(assistant, input);

Prints the full timeline when a run ends:

Trace 7323a0e7  (ok, 1240ms)
  +0ms      runtime:start
  +2ms      agent:start  "Weather in Tokyo?"
  +5ms      llm:request  model=gpt-4o-mini
  +820ms    llm:response  model=gpt-4o-mini tokens=120→30
  +825ms    tool:start  weather
  +826ms    tool:end  weather
  +1240ms   runtime:end
  ── 2 LLM · 1 tool · 355 tokens · $0.0001

API

  • devtools({ log, price }) — a plugin; price(model, usage) computes cost.
  • .traces() / .trace(runId) / .last() — read traces programmatically.
  • .print(runId?) — print a timeline.
  • .onTrace(cb) — hook each finished run (send to OpenTelemetry, Langfuse, a UI, …).

No tracing SDK, no external service. The runtime knew everything already.


Part of Runbit — the AI Runtime. Everything executes through one small, event-driven runtime; agents, workflows, RAG, and observability are packages on top.