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

@simplehook/playwright

v0.1.1

Published

Playwright WebhookProvider for simplehook — test real webhooks in E2E tests.

Downloads

210

Readme

@simplehook/playwright

Playwright WebhookProvider for simplehook. Test your E2E flows against real webhook events from Stripe, GitHub, Twilio, and any provider.

Install

npm install @simplehook/playwright

Requires @seontechnologies/playwright-utils as a peer dependency (>=4.0.0).

Quick Start

import { test } from "@seontechnologies/playwright-utils/webhook/fixtures";
import { SimplehookWebhookProvider } from "@simplehook/playwright";
import { WebhookTemplate } from "@seontechnologies/playwright-utils/webhook";

// Reads SIMPLEHOOK_KEY from the environment by default.
// Each test worker gets a unique listener ID for parallel safety.
const webhookTest = test.extend({
  webhookProvider: async ({}, use) => {
    await use(new SimplehookWebhookProvider());
  },
});

webhookTest.use({ webhookConfig: { cleanupStrategy: "matched-only" } });

webhookTest("Stripe charge creates an order", async ({ webhookRegistry, page }) => {
  // Trigger a real Stripe test charge
  await page.click("#buy-button");

  // Wait for the real webhook to arrive through simplehook
  const webhook = await webhookRegistry.waitFor(
    WebhookTemplate.create("stripe-charge")
      .withUrlMatching("/stripe/events")
      .withBodyMatching({ type: "charge.succeeded" })
  );

  expect(webhook.body.data.object.amount).toBe(500);
});

API

new SimplehookWebhookProvider(options?)

Creates a provider that pulls real webhook events from simplehook's API and exposes them through the WebhookProvider interface.

Called with no arguments, it reads SIMPLEHOOK_KEY from the environment.

// Defaults: reads SIMPLEHOOK_KEY from env, auto-generates unique listener ID
new SimplehookWebhookProvider();

// Override anything you need
new SimplehookWebhookProvider({
  apiKey: "ak_...",           // Optional, falls back to SIMPLEHOOK_KEY env var
  serverUrl: "...",           // Override server URL
  listenerId: "my-worker",   // Custom listener ID (default: auto-generated per instance)
  pullBatchSize: 50,          // Events per pull cycle (default: 100)
});

How it works

The provider bridges simplehook's cursor-based Pull API to the journal model that playwright-utils expects:

  1. Each provider instance gets a unique listener ID, so parallel test workers never see each other's cursors
  2. Events are pulled from the API into an in-memory journal
  3. getReceivedWebhooks() queries the local journal with filter support (URL pattern, method, timestamp)
  4. deleteById() removes events from the local journal (for matched-only cleanup)
  5. resetJournal() clears the journal and generates a fresh listener ID (clean slate)

Parallel safety

Each SimplehookWebhookProvider instance generates a unique listener ID (pw-<random>). This means:

  • Workers A and B both see the same events (independent cursors)
  • deleteById() in worker A doesn't affect worker B
  • resetJournal() in one worker doesn't affect others

Links

License

MIT