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 🙏

© 2024 – Pkg Stats / Ryan Hefner

webhook-tester

v1.2.0

Published

Simple express app to use for automated testing of webhooks Edit

Downloads

15

Readme

webhook-tester

Simple express app to use for automated testing of webhooks

Use this package to test webhook calls that your app API is supposed to make. A test sequence could be

  • register a webhook using your app API
  • register a webhook test on webhook-tester, this request will be pending
  • make a call to your API that is supposed to trigger the webhook call
  • the webhook test request will be called. If the webhook had a request body, you will get it as a response body

Install

npm install webhook-tester

Use

Launching webhook-tester

You can either start webhook-tester on a separate terminal window, or require it in your tests. Don't do both :-)

Start in the terminal

npm start

Require in your test files

You only need to start it once but it doesn't matter if you call start multiple times.

const webhookTester = require('webhook-tester');
webhookTester.port = 4003; // Optional. 4003 is the default
webhookTester.timeout = 10000; // in ms. Optional. 10000 is the default
webhookTester.verbose = false, // Boolean. Optional. Defaults to true. If true logs every register and webhook call
webhookTester.start(); // Required. You can optionnally pass a function to get the register and call urls

Registering a webhook test

GET http://localhost:4003/register/:webhook_id

where :webhook_id is a unique id you assign to this webhook This request will timeout after a maximum of a minute if the webhook is never called

Registering a webhook on your app API

The Webhook url that needs to be called to get a successful response from the above test registered is

http://localhost:4003/webhooks/:webhook_id

where :webhook_id is the same unique id that you have registered above. This url will accept GET and POST requests. It can only be called one time per webhook test.