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

webhookify

v1.1.1

Published

Implementation of the webhookify protocol.

Downloads

7

Readme

logo

Protocol implementation of the webhookify client protocol. The specification of the protocol can be found on the wiki.

Installation

Install the protocol stack by running

npm i -S webhookify

Usage

// load module
const { Protocol } = require('webhookify');

// load private key and client id from somewhere
let clientId, privateKeyPEM;

// instantiate protocol
let connection = new Protocol(client, privateKeyPEM);

// connect to server
connection.connect();

// handle incoming events
connection.on("push", (plugin, payload) => {
	// push message with payload was received and is directed at plugin
});

connection.on("fetch", (plugin, payload, reply) => {
	// push fetch with payload was received and is directed at plugin

	// retrieve the requested data and call reply function with (err, response)
	reply(null, {});
});

connection.on("error", (err) => {
	console.log("An error occurred:", err.message);
});

Reference

class Protocol

constructor(clientId, privateKeyPem, options)
Creates a new instance of the protocol. A valid clientId can be retrieved at https://www.webhookify.net and a valid private RSA key can be generated with the client or openssl for example.

The options parameter is an object with the following recognized keys:
reconnect (boolean) [Default: true]
reconnectDelay (number) [Default: 2000]
ignoreErrors (boolean) [Default: true]

connect()
Initiates a connection to the webhookify server.

All other methods are for internal use only, but they might be useful, if you plan on extending this class somehow

processMessage(message)
Parses the message string and invokes the appropriate action, either replying to the challenge or emitting a "push" or "fetch" event.

sendReply(id, payload)
Encodes id and payload into a reply message, which is then sent to the server via the websocket connection.

sendError(id, err)
Encodes id and err.message into an error message, which is then sent to the server via the websocket connection.

encodeMessage(type, id, payload)
Creates a new message string with the specified parameters.

Events

Event 'push'
A push message was received from the server. The handler is called with (plugin, payload).

Event 'fetch'
A fetch message was received from the server, which now expects a reply within five seconds. The handler is called with (plugin, payload, reply), where reply is a function with the signature (err, response).

Event 'connected'
The websocket connection is (re-)established.

Event 'disconnected'
The websocket connection was interrupted for some reason.

Event 'error'
If the ignoreErrors option is set to false, the error events the socket encounters are passed on here.