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

@vscode/ripgrep

v1.18.0

Published

A module for using ripgrep in a Node project

Readme

vscode-ripgrep

This is an npm module for using ripgrep in a Node project. It's used by VS Code.

How it works

  • Ripgrep is built in microsoft/ripgrep-prebuilt and published as release assets for each tag.
  • At publish time, the binaries for every supported platform are downloaded by build/prepare-binaries.js, verified against binaries.lock.json (SHA256), and placed under bin/<target>/rg[.exe]. They ship inside the npm tarball.
  • At runtime, lib/index.js resolves rgPath from process.platform/process.arch to the correct bin/<target>/<binary>.
  • There is no postinstall step and no runtime network access.

Usage example

const { rgPath } = require('@vscode/ripgrep');

// child_process.spawn(rgPath, ...)

Updating ripgrep

  1. Edit the VERSION (or MULTI_ARCH_VERSION) constant in lib/platforms.js.
  2. Run npm run update-lock. This re-downloads every platform's archive and rewrites binaries.lock.json with the fresh SHA256 hashes.
  3. Commit the updated lib/platforms.js and binaries.lock.json.

Building locally

  • npm run prepare-binaries — downloads any missing binaries and verifies them against binaries.lock.json. Fails on hash mismatch.
  • npm run prepare-binaries -- --force — forces a clean re-download (still verifies).
  • npm run update-lock — refreshes binaries.lock.json after a version bump.

Set GITHUB_TOKEN to avoid GitHub's anonymous API rate limit during downloads.