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

@joelazar/pi-tuicr

v1.1.0

Published

Review the changes pi made in tuicr, then send the review comments back to pi

Readme

pi-tuicr

Review the diff pi just produced in tuicr, then hand your comments straight back to pi.

demo

The usual loop is annoying: pi writes code, you read the diff somewhere else, then you retype your objections into the chat. This extension closes that loop. /tuicr asks what you want to review, suspends pi's TUI and opens tuicr on that diff. Every comment you leave during that session gets collected, numbered, and prefilled into pi's editor when tuicr exits. You read it over, and press enter when you're happy.

Comments that were already in tuicr before you opened it are ignored, so an old review doesn't come back a second time.

Install

pi install npm:@joelazar/pi-tuicr

tuicr has to be on your PATH. The extension shells out to tuicr for the review UI and to tuicr review list / tuicr review comments for the JSON.

Usage

| Trigger | What it does | | -------------- | -------------------------------- | | /tuicr | Pick a diff, then load notes | | ctrl+shift+r | Same, without typing |

The picker offers:

| Choice | tuicr invocation | | ----------------------------- | ------------------------- | | Uncommitted changes | tuicr -w | | Branch vs base (+ uncommitted)| tuicr -r base..HEAD -w | | Branch vs base | tuicr -r base..HEAD | | Last commit | tuicr -r HEAD~1..HEAD | | Pick commits | tuicr (commit selector) | | Every tracked file | tuicr -A | | Custom revset... | tuicr -r <your revset> | | Pull request... | tuicr pr <target> |

The base branch is detected from origin/HEAD, falling back to origin/main, origin/master, main, master; if none exist those entries are hidden.

What lands in the editor looks like this:

I reviewed your changes in tuicr. Please address these comments:

1. `src/auth.ts:42` [BUG] - this throws when the token is missing
2. `src/auth.ts:88` - rename this to something less generic

If you left no comments, you get a notification and an untouched editor.

Notes

  • Only comments created during the session you just opened are sent back; anything already in tuicr is ignored.
  • If tuicr is missing or exits non-zero, the extension says so and stops rather than sending a half-built prompt.
  • Interactive TUI mode only.

License

MIT