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

slacked

v2.0.0

Published

Simple pluggable slack app base

Readme

Slacked

A slack app for automation.

Create slack slash commands quickly and easily, as simple node modules.

See the demo in packages/demo for a basic example.

Config

You should export the app token provided to you by slack as the SLACK_TOKEN environment variable.

Adding slack slash commands

Add new slash commands as plugins - see packages/demo-plugin for an example. Register your plugin in config.json:

{
  "plugins": [
    "demo"
  ]
}

Plugins

Plugins export three things, an exec method which is called when the command is initiated via slack:

exec: function(who, text, responseUrl)

who: the username of the person executing the task text: all remaining arguments passed after the initial /slash command responseUrl: The out-of-band response url which you can send delayed replies to.

a command getter:

command: <string>

Which is the name of the command. For instance exports.command = 'foo' would mount the command at the endpoint http://localhost/commands/foo and you could point slack's slash command url at that. It's probably wise to also assign the command /foo to this, but it's not mandatory - your slash command can be anything you like.

The built in demo command will just say hello to somebody: /demo <name here>

and a config setter:

setConfig: function (conf) { ... }

which will be passed the relevant config, from the appropriately named key in config.json:

{
  "plugins": [
    "demo"
  ],
  "demo": {
    "some": "config"
  }
}

Replies

The slacked-slack module handles replies and things. If you throw errors anywhere in your plugins, these will be relayed ephermally to your calling users.