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

commercehook

v0.3.0

Published

Inspect, tail and replay webhook deliveries from your terminal.

Readme

commercehook

Inspect, tail and replay webhook deliveries from your terminal.

CommerceHook is a webhook inspector for ecommerce platforms: point BigCommerce (Shopify soon) at an endpoint, watch deliveries arrive, inspect every header and payload, and replay them at your handler while you fix it.

npx commercehook --help

Sign in

npx commercehook login

Your browser opens on the same consent screen any connected app gets; approve it and the terminal is signed in. The CLI then appears under Connected apps in your dashboard settings, where it can be disconnected like anything else. commercehook logout does the same from this end, revoking the grant rather than just forgetting it.

No browser on the machine? commercehook login --with-api-key stores an API key instead, or set CH_API_KEY in the environment and store nothing, which is what CI wants.

Commands

| Command | What it does | | --- | --- | | login | Sign in through your browser (or --with-api-key) | | logout | Sign out and revoke this CLI in Connected apps | | whoami | Which account this terminal acts as | | endpoints | List endpoints; create, rename, delete | | events <endpoint> | List deliveries; --search, --tail for live | | event <id> | Inspect one delivery, signature verdict included; --raw for the exact body | | listen <endpoint> --forward-to <url> | Stream deliveries into a local handler | | replay <id> --to <url> | Re-send a delivery to your handler | | version | CLI version and the API version it talks to | | upgrade | How to update this install, whichever way it arrived |

Endpoints are referenced by id or by any unambiguous name prefix: commercehook events prod works until you also have prod-eu, at which point the CLI lists both and asks rather than guessing.

The one to try first:

npx commercehook listen my-endpoint --forward-to http://localhost:3000/webhooks

Register the CommerceHook URL with your platform once, then every delivery streams into the handler on your laptop (original method, headers and body) while also being captured for inspection. The ngrok part of the webhook loop, without the tunnel.

--tail does the same without forwarding: one line per delivery as it arrives. With --json each line is the delivery as JSON, ready for jq.

Flags every command takes

| Flag | What it does | | --- | --- | | --json | Machine-readable output, one JSON document per line | | --api-url <url> | Talk to a different CommerceHook instance | | --help, -h | Help for the command | | --version, -v | CLI and API versions |

CH_API_KEY and CH_API_URL environment variables override the stored config, which is what CI wants.

Update checks

Once a day, after a command finishes, the CLI checks npm for a newer release and mentions it on stderr. It never runs in CI, never delays a command, and never touches stdout. Set CH_NO_UPDATE_NOTIFIER=1 to turn it off entirely.