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

deploy-listener-server

v0.0.2

Published

Start an SSL listener for GitHub to listen for pushes to branches then launch an executable.

Readme

Deploy Listener Server

This is an attempt to simplify the process of dealing with Github webhooks. Through use of a simple configuration file, you can configure a listener for a Github webhook from one or multiple repositories. You can listen for push events. (I may enhance for any event in the future, it is very easy to do so yourself.) Upon receipt of the push event, you can execute launch a local executable to do some task. e.g. When code gets checked into the master branch, pull updated code from Github and restart the node.js application or start some other process.

Configuration

To use this application clone this repo or install via npm

npm install deploy-listener-server

{
	"port": port your webhook listens on,
	"githubPath": "path for your webhook to listen",
	"handlers": [
		{
			"repo": "username/reponame",
			"branch": "refs/heads/branch of interest",
			"executable": "./deploy.sh",
			"slackUsername": "Deploy-Bot",
			"slackChannel": "specific channel for just this handler"
		},
		{
			"repo": "ikhnaton/deploy-listener-server",
			"branch": "refs/heads/master",
			"executable": "./deploy.sh"
        }
	],
	"secret": "Your github secret associated with this webhook",
	"sslKey": "path to your ssl key",
	"sslCert": "path to your ssl certificate",
	"logLevel": "debug",
	"logFile": "../deployer.log",
	"environment": "development",
	"slackMessage": "message to send to slack when successful",
	"slackChannel": "slack channel to post to",
	"slackUrl": "your slack url",
	"slackUsername": "your slack username"
}

logLevel - The log levels are as follows.

"fatal" (60): The service/app is going to stop or become unusable now. An operator should definitely look into this soon.
"error" (50): Fatal for a particular request, but the service/app continues servicing other requests. An operator should look at this soon(ish).
"warn" (40): A note on something that should probably be looked at by an operator eventually.
"info" (30): Detail on regular operation.
"debug" (20): Anything else, i.e. too verbose to be included in "info" level.
"trace" (10): Logging from external libraries used by your app or very detailed application logging.