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

@arhen/pi-add-code-diagnostic

v1.0.3

Published

pi extension: repo-scoped typecheck/lint diagnostics for coding agents (LSP-equivalent, no servers).

Readme

@arhen/pi-add-code-diagnostic

npm version license

Install

Requires the pi coding agent — install it first: npm install -g @earendil-works/pi-coding-agent.

pi install npm:@arhen/pi-add-code-diagnostic

LSP-equivalent diagnostics for coding agents — no language servers, no JSON-RPC, no server lifecycle. One configured command per repo, run by the agent loop itself.

How it works

  • Tier 1 — per-file lint on write/edit. If the repo config has fileCheck (e.g. eslint ${file}), it runs silently in the background after each agent write/edit. Never blocks.
  • Tier 2 — global check at agent settle. Runs the repo's check command (e.g. tsc --noEmit) once per session, then after any agent edit. Errors surface as a followUp message; triggerTurn re-engages the agent to fix them, so the agent keeps working until the tree is clean.
  • Discovery, one message per session. Repo has no config yet → the agent is asked to inspect the repo, propose a check/fileCheck, self-test it, confirm with you, and write the config. off or enabled: false = silent forever.
  • Fail-open everywhere. A broken command never blocks the agent. 3 crashing runs auto-disable the config. Aborted agent runs skip the check.
  • Loop guard. The same error report with no edits since → shown only, no re-trigger.

Config

Per repo root at ~/.pi/repos/<root-sanitized>.json:

{ "check": "tsc --noEmit", "fileCheck": "eslint ${file}", "enabled": true }

Commands are split on whitespace (no shell pipes/&&) and run with a 120s timeout from the repo root.

Commands

  • /diagnostic — status: root, check cmd, fileCheck, enabled, testedAt, lastExit
  • /diagnostic run — run the global check now
  • /diagnostic clear — delete the repo config; discovery re-runs

License

MIT.