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

slack-relayer

v1.1.0

Published

relay any string you want to slack, using events

Downloads

9

Readme

slack-relayer

Given a slack channel and an access token, send any string from anywhere in a node program to your Slack. As easy as process.emit('slack', 'HALP!'), no baton-passing needed.

usage

const createSlacker = require('slack-relayer');

 // returns the object just in case
const relayer = createSlacker({
	channel: 'bots',
	token: process.env.SLACK_API_TOKEN,
	event: 'event-to-listen-for'
});

// later on in another file...
process.emit('event-to-listen-for', 'I have a terrible pain in all the diodes down my left-hand side.');
// the relayer will then post this to slack for us with zero effort

// if you need to group specific events emit a key before your message
process.emit('event-to-listen-for', 'wisdom','a group of wombats');

You can use either a channel id or a channel name. It'll look up the channel id if you pass a name. It will maintain a backlog of up to 100 messages while it waits for the lookup, and unregister itself if it can't find the channel.

The slack api only wants one message per second. By default slack-relayer will group messsages that are emitted by key to prevent flooding the api. Every 10 seconds it will send them in a single post to slack. If you emit more than 10 messages in 10 seconds only the last 10 will be shown in slack. This delay and truncation limit can be changed with optional options documented below.

bonus!

> npm install -g slack-relayer
> slack-relayer general "omg this is a thing"

You must have SLACK_API_TOKEN or SLACK_TOKEN set in your environment for this to work.

optional options

opts.prefix - this string prefix is put before every post to slack - defaults to ''. its a very good place to put the hostname and service name.

opts.lineLimit - the number of lines to buffer for each key - default 10 - slack messages are limited to 4k otheriwse it'll truncate it for you. - consider adding your own listener to this event that calls your standard logging so events that dont post to slack can be reviewed.

opts.slackInterval - the rate at which this process posts to slack. - default 10000 ms

license

ISC.