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

@bobfrankston/jgrep

v1.0.3

Published

Recursive grep for TypeScript/JavaScript source trees, with comment-stripping and filename-glob filters

Downloads

169

Readme

@bobfrankston/jgrep

Recursive grep tailored for TypeScript / JavaScript source trees.

By default jgrep searches .ts files (and .js files only when no sibling .ts exists), skips node_modules, prev, recycle bins, and hidden directories, and follows real paths to avoid revisiting the same directory through symlinks/junctions.

Install

npm install -g @bobfrankston/jgrep

Usage

jgrep [options] pattern [startdir ...]

If no starting directories are given, jgrep searches y:\dev, y:\inetpub, and y:\x\bin (with WSL-style path translation when not on Windows).

Options

| Flag | Meaning | |------|---------| | -c | Include comments when matching lines (default: strip // from non-TS files) | | -s / -show | Show each matching line with the match highlighted | | -v / -verbose | Verbose output (line text after each hit) | | -d<n> | Print directory names up to depth n while traversing | | -ext .x .y | Add file extensions to consider (in addition to .ts) | | -n / -name / -names | Match filenames against glob patterns (e.g. *.json, package.*) |

Examples

jgrep "TODO" y:\dev\utils
jgrep -ext .json -n package.* "homepage"
jgrep -s "RMFLogger"

Develop

tsc -w        # rebuild on save
node .        # run locally

The compiled index.js is the bin entry, so npm link or npm install -g . makes jgrep available on PATH.