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

@parke.dev/pi-firecrawl

v0.1.0

Published

Firecrawl search, scrape, map and crawl tools for the pi coding agent

Readme

@parke.dev/pi-firecrawl

Firecrawl tools for the pi coding agent. Turn web pages into clean markdown, search the web, map a site's URLs, or crawl many pages in one job — against Firecrawl's hosted API or a self-hosted v1 instance.

Four tools:

| Tool | What it does | | ------------------ | ----------------------------------------------------------------- | | firecrawl_scrape | scrape one URL into markdown (and optional other formats) | | firecrawl_search | web search; optionally scrape each result page | | firecrawl_map | discover the URLs on a site | | firecrawl_crawl | crawl linked pages into markdown (async job, polls to completion) |

Install

pi install npm:@parke.dev/pi-firecrawl

By default the tools talk to the hosted API at https://api.firecrawl.dev, which needs an API key and consumes credits. Point baseUrl at a self-hosted instance instead and no key is required on a typical local setup. Run /firecrawl in pi to confirm connectivity.

Configuration

Everything is optional. Precedence is defaults ← ~/.pi/firecrawl.json ← environment.

{
  "baseUrl": "https://api.firecrawl.dev",
  "apiKey": "…",
  "timeoutMs": 120000,
  "crawlTimeoutMs": 120000
}

| Field | Env var | Default | Meaning | | ---------------- | ---------------------------- | --------------------------- | ----------------------------------------------------------- | | baseUrl | FIRECRAWL_BASE_URL | https://api.firecrawl.dev | Firecrawl API origin | | apiKey | FIRECRAWL_API_KEY | none | sent as Authorization: Bearer; required by the hosted API | | timeoutMs | FIRECRAWL_TIMEOUT_MS | 120000 | request timeout for scrape / search / map | | crawlTimeoutMs | FIRECRAWL_CRAWL_TIMEOUT_MS | 120000 | how long to poll a crawl job before giving up |

Deployment shapes

Hosted API (the default) needs a key and burns credits:

{ "apiKey": "fc-…" }

Or export FIRECRAWL_API_KEY=fc-….

Self-hosted only needs the origin:

{ "baseUrl": "http://localhost:3002" }

Diagnostics

/firecrawl    show config and test connectivity with a scrape of example.com

License

MIT