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

webhook-replay

v1.0.0

Published

Replay webhook deliveries against a handler to detect duplicate side effects.

Readme

webhook-replay

Replays webhook deliveries against a handler to simulate retries, concurrency, and reordering.

Usage

npx webhook-replay path/to/handler.js

After publishing to npm. Until then: node bin/webhook-replay.js path/to/handler.js

The handler will be invoked multiple times using the same payload, including concurrent executions.


Debug mode (Local Debugging Path)

When you suspect “why did this run twice?”, use:

webhook-replay debug ./path/to/handler.js --payload ./payload.json --trace

Or provide payload inline:

webhook-replay debug ./path/to/handler.js --payload-inline '{"id":"evt_123"}' --trace

It prints:

  • how many times the handler ran
  • which side effects repeated
  • a minimal reproduction command
  • call-by-call trace timing (with --trace)

Exit codes (CI-safe)

  • 0 = safe (no duplicate side effects observed)
  • 2 = unsafe (duplicate side effects and/or handler errors observed)
  • 1 = tool error (bad input, failed to load handler, unexpected crash)

This is intentional: in CI, unsafe should fail the build.


Declaring side effects

Handlers may declare external side effects using ctx.effect(key).

The same key being observed more than once is treated as a failure.

Example:

module.exports = async function handler(payload, ctx) {
  ctx.effect(`stripe.charge:${payload.id}`);
};

Output

If duplicate side effects are detected, the run fails:

❌ Failure detected

Duplicate side effects observed:

  • stripe.charge:evt_demo_123: 7 executions

If no duplicates are observed, the run completes successfully.


CI Failure Path (GitHub Actions)

Add a workflow that runs webhook-replay on every PR. If unsafe, the job fails and the merge is blocked.

Example:

name: webhook-replay
on:
  pull_request:
  push:
    branches: [ main ]

jobs:
  replay:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20

      # If installed in the repo (recommended for CI determinism):
      # - run: npm ci
      # - run: npm run ci:replay

      # Or run directly via npx (no install) once published:
      - run: npx webhook-replay ./examples/handler.js