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

treslek

v0.11.0

Published

node.js irc bot

Downloads

5

Readme

treslek

Join the chat at https://gitter.im/jirwin/treslek A node irc bot made to replace doslek.

Webhook Server

treslek supports running a simple HTTP server for receiving webhooks from external services and acting on them. In order to enable this feature, include a key in the config that looks something like the following:

"webhook": {
  "host": "0.0.0.0",
  "port": 1304,
  "channelKey": "webhookChannels"
}

The webhook server works by forwarding the headers and body of any incoming request to a PUBSUB channel on the Redis server. This allows any plugins to listen for any requests that may come in and deal with them accordingly. Given the above configuration, a redis prefix of treslek and the assumption that treslek is available at http://treslek.example.com:1304, a HTTP request to http://treslek.example.com:1304/treslek/webhook would be published to the Redis key treslek:webhookChannels:treslek/webhook. A plugin that would like to listen to this webhook would then subscribe to treslek:webhookChannels:treslek/webhook and react as it pleases.

A good example of this would be a plugin that listens for webhooks from Github about activity on a set of repositories. You could configure each of your repositories to send webhooks to http://treslek.example.com:1304/github/<repo-name> and then write a plugin to announce when Pull Requests have been opened.

License

treslek may be freely distributed under the MIT license.

treslek <3 you