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

@heyhuynhgiabuu/pi-search

v0.2.2

Published

Unified search toolkit for pi — web search, code search, docs lookup, and GitHub code search in one extension.

Downloads

608

Readme

pi-search

npm version

pi-search is a standalone pi extension that bundles the search and research tools you reach for most often into one package.

It combines:

  • real-time web search via Exa AI
  • technical docs and API search via Exa AI web search
  • official documentation lookup via Context7
  • real-world GitHub code search via grep.app

The goal is simple: install one extension and get a practical research toolkit for current docs, code examples, library references, and production usage patterns.

Tools

| Tool | Source | Description | |------|--------|-------------| | grepsearch | grep.app | Search real-world code on GitHub. Use literal patterns like "useState(", not keywords. | | websearch | Exa AI | Real-time web search. No API key required. | | codesearch | Exa AI | Technical doc/example search tuned for programming queries and powered by Exa web search. No API key required. | | context7 | Context7 | Resolve library IDs and fetch library documentation. Optional CONTEXT7_API_KEY for higher rate limits. | | web_fetch | Exa AI | Fetch a webpage's full content as clean markdown. Use after websearch/codesearch to read a specific result. |

Install

pi install npm:@heyhuynhgiabuu/pi-search

Or load locally during development:

pi -e ./src/index.ts

Optional for higher Context7 rate limits:

export CONTEXT7_API_KEY=your_key_here

Configuration

Create ~/.pi/agent/pi-search.json to customize the extension.

Disable specific tools

{
  "disabledTools": ["context7", "codesearch"]
}

Valid tool names: grepsearch, websearch, codesearch, context7, web_fetch.

If the file doesn't exist or is invalid JSON, all tools are enabled by default.

Usage

grepsearch({ query: "getServerSession", language: "TypeScript" })
websearch({ query: "Next.js 15 server actions" })
codesearch({ query: "Go context.WithCancel usage" })
context7({ operation: "resolve", libraryName: "react" })
context7({ operation: "query", libraryId: "/reactjs/react.dev", topic: "hooks" })

When to use which tool

  • websearch → current information, blog posts, docs, release notes, discussions
  • codesearch → programming docs, API examples, framework usage, and technical references
  • context7 → official library documentation after resolving the right library ID
  • grepsearch → how real repositories use an API in practice

Development

npm install
npm run typecheck
npm run lint
npm test

License

MIT — huynhgiabuu