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

@johnnywu/pi-default-tools

v1.0.0

Published

Activate default tools from settings.json — reads project or global settings to enable built-in tools like grep, find, and ls on session start

Readme

pi-default-tools

Activate built-in pi tools from settings.json — reads project or global settings to enable tools like grep, find, and ls on session start.

Install

pi install npm:@johnnywu/pi-default-tools

Or via local path in ~/.pi/agent/settings.json:

{
  "packages": ["~/dev/jwu/pi-default-tools"]
}

Configuration

Add a tools field to .pi/settings.json (project) or ~/.pi/agent/settings.json (global):

{
  "tools": ["grep", "find", "ls"]
}

Behavior

| Configuration | Effect | |---------------|--------| | tools not present | Nothing changes — pi uses its default tools | | tools: [] | Whitelist — clears all active tools | | tools: ["grep"] | Whitelist — sets active tools to exactly grep | | tools: ["...", "grep"] | Merge"..." expands to current active tools, then appends grep |

The special marker "..." represents "keep current active tools". Without it, the array acts as a strict whitelist.

Precedence

  • Project .pi/settings.json takes precedence over global ~/.pi/agent/settings.json
  • If tools is not defined in project settings, global settings are used
  • Only string array values are accepted; invalid types are ignored

Development

# Install dependencies
bun install

# Run tests
bun test

# Type check
bun run typecheck

# Format
bun run format

# Release (local, requires GH_TOKEN and NPM_TOKEN)
bun run release

This project uses semantic-release with conventional commits.

License

MIT