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

@ose4g/webhook-cli

v1.3.0

Published

cli application to allow easy testing and development of webhooks

Downloads

5

Readme

webhook-cli

npm (scoped) npm npms.io (final) Libraries.io dependency status for latest release, scoped npm package

One issue backend developers is testing webhooks locally. Since the webhook must be connected to the internet an approach may be to write code and deploy in order to test. This could be inefficient espeicially if you don't know what data to expect.
Using this package you could proxy requests from a remote url to your server running locally.

Installation

npm install -g @ose4g/webhook-cli

Usage

  • To get the remote url you'll be using run the following command.

    webhook-cli get password
    • replace password with your password.
    • make sure to note down your password as you'll need it to connect to that particular url again.
  • It then logs the remote url you'll be using for testing. The urls are usually in the pattern http://ose4g-webhook.herokuapp.com/<unique-code>/webhook

  • In your application(e.g github apps or stripe) set this url as your webhook.

  • Once that is done run the following command in your terminal

webhook-cli connect --pass <password> --url <remote-url> --port <port> --path <path>

e.g

webhook-cli connect --pass password --url http://ose4g-webhook.herokuapp.com/<unique-code>/webhook --port 3000 --path /api/v1/webhook
  • This makes a connection from the remote url to the specified server and proxies the request to the local server.
  • You can then log the request and write code to test the webhook.