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

@tplog/hasapi

v0.3.0

Published

One-shot installer that adds curated extensions to the Pi coding agent.

Readme

hasapi

One command to set up the Pi coding agent the way I like it — a curated set of extensions, installed globally.

Quick start

npx -y @tplog/hasapi

The -y flag skips npx's first-run install confirmation. Without it, an uncached or non-interactive run can fail with sh: hasapi: command not found.

It will:

  1. Install pi for you if it isn't on PATH yet.
  2. Install the curated pi extensions (pi install <source>).

Install is idempotent — extensions already in your pi settings are skipped.

Commands

| Command | What it does | | --- | --- | | npx -y @tplog/hasapi | Install the curated pi extensions | | npx -y @tplog/hasapi status | Show which extensions are installed | | npx -y @tplog/hasapi remove | Remove the hasapi extensions | | npx -y @tplog/hasapi doctor | Check your environment for common problems |

What gets installed

Extensions (pi install):

  • npm:pi-markdown-preview — Markdown preview
  • npm:pi-notify — desktop notifications
  • npm:@aliou/pi-processes — background process management
  • npm:@plannotator/pi-extension — planning and annotation workflow
  • npm:pi-mcp-adapter — MCP server integration
  • npm:@narumitw/pi-goal — goal tracking
  • npm:@juicesharp/rpiv-pi — skill-based dev workflow (research → design → plan → implement → validate)
  • npm:context-mode — context-mode tooling
  • npm:@narumitw/pi-btw — side-chat popover
  • npm:pi-generative-ui — generative UI
  • npm:glimpseui — native UI widgets and dialogs
  • npm:pi-provider-kimi-code — Kimi model provider
  • npm:@narumitw/pi-chrome-devtools — Chrome DevTools control

Editing the catalog

Extensions live in the EXTENSIONS array at the top of bin/hasapi.mjs. Add an entry with an id, source (npm: or git:), and description.