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

@arvoretech/pi-monitor

v1.0.0

Published

PI extension that watches a background process and pushes matching output lines to the agent as notifications (no polling)

Downloads

171

Readme

@arvoretech/pi-monitor

Watch a long-running background process and push each matching output line to the agent as a notification — no polling. Inspired by Claude Code's Monitor tool, with stderr + exit-code capture and flood protection on top.

How it works

monitor_start → spawn(command, shell) → readline(stdout/stderr)
                        │
              line matches include/exclude filter
                        │
        pi.sendUserMessage(line, { deliverAs: "steer" })  → agent reacts mid-conversation

The agent keeps working and is interrupted only when a matching line arrives. Monitors are session-scoped and are killed on session_shutdown.

Tools

  • monitor_start — start a background monitor. Params: id, command, cwd?, include? (regex), exclude? (regex), captureStderr? (default true), reportExit? (default true), deliverAs? (steer | followUp, default steer), maxEventsPerWindow? (default 40 / 60s).
  • monitor_stop — stop by id, or all: true.
  • monitor_list — list running monitors with uptime and event counts.

Command

  • /monitors — abre o painel de logs (monitores ativos + eventos recentes). Esc fecha.

Footer

Enquanto houver monitores rodando, um item aparece no rodapé (1 monitor ativo · /monitors p/ logs). Ele some sozinho quando o último monitor termina, e pode ser escondido pela extensão widget-wrangler (/wrangle).

Notes vs Claude Code Monitor

  • Captures stderr and exit code (Claude's forwards stdout only, so silent failures look healthy).
  • Filter is applied in-process via include/exclude regex to avoid flooding context.
  • Flood guard: a monitor emitting more than maxEventsPerWindow matching lines per 60s window auto-stops and tells the agent to restart with a tighter filter.
  • Pipe-buffering caveat still applies to your command: use grep --line-buffered when filtering upstream.

Usage

Add to .pi/settings.json:

{ "packages": ["npm:@arvoretech/pi-monitor"] }

Then ask in natural language:

Run docker compose up --build in the background and tell me the moment any line contains "error" or when a service reports "healthy".