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

@netgrep/netgrep

v0.4.0

Published

grep over HTTP — search a remote file with ripgrep's regex engine while it downloads

Readme

The netgrep wordmark: new Netgrep(); set in monospace, fading from white into teal on a dark gradient

@netgrep/netgrep

The main netgrep package. See the main README for more information.

netgrep streams a URL's response through ripgrep's real regex engine and answers the moment a matching line arrives — without waiting for the last byte, and without holding the file in memory. No index to build, no backend to run.

It runs in a browser and nowhere else: it needs fetch with a streaming response body, and it is ESM only. The file has to be one the browser can fetch anonymously — a cross-origin URL needs Access-Control-Allow-Origin, and netgrep puts nothing on the request, so anything behind a login is out of reach however permissive its CORS policy.

It answers one question per URL — does this pattern occur? — as a boolean, plus the first matching line if you pass capture: 'line', or that line with each match's position within it under capture: 'line-ranges'. That is the whole result: no ranking, no match counts, no line numbers, no positions in the file. It costs a ~1.17 MB WebAssembly download (~500 KB gzipped) once per page load, and it has known limitations worth reading first.