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

gnu-patch

v2.6.0

Published

Npm wrapper that ships pre-extracted patch binaries and exposes them via the package bin entry (`patch`).

Readme

gnu-patch

Npm wrapper that ships pre-extracted patch binaries and exposes them via the package bin entry (patch). Currently includes the GnuWin32 build; the structure allows adding other platforms.

Install

  • Global (adds patch to PATH via npm's global bin): npm install -g gnu-patch
  • Project-scoped (available via npx patch or node_modules/.bin/patch): npm install gnu-patch

Layout

  • bin/win32/patch.exe — bundled GnuWin32 binary.
  • bin/win32/docs/ — upstream docs and man pages (patch.1.txt, patch.1p.txt, AUTHORS, COPYING, ChangeLog).
  • Entry point: index.js (wired via package.json bin field to patch).

Platform behavior

  • Currently ships only the Windows binary; additional platforms can be added under bin/<platform>/.
  • Until other binaries are added, non-Windows hosts will exit with an explanatory error.

Postinstall

  • On Windows, scripts/postinstall.js only verifies that bin/win32/patch.exe exists; there are no downloads or extractions.
  • On non-Windows hosts, postinstall prints a skip notice and exits.

Usage

  • Global install: patch --version should work immediately (npm global bin is typically on PATH on Windows).
  • Local install: use npx patch or node_modules/.bin/patch (no system PATH changes).
  • If patch.exe ever goes missing, run npm rebuild gnu-patch or reinstall to restore bundled files.

License

MIT