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

hubot-command-blacklist

v2.0.1

Published

Middleware and commands for blacklisting specific commands in certain rooms or channels

Downloads

11

Readme

hubot-command-blacklist

Middleware and commands for blacklisting specific commands in certain rooms or channels

Installation

In hubot project repo, run:

npm install hubot-command-blacklist --save

Then add hubot-command-blacklist to your external-scripts.json:

[
  "hubot-command-blacklist"
]

Configuration

HUBOT_DEFAULT_COMMANDS - comma separated list of command ids that can't be disabled.

Commands

| Command | Listener Id | Description| |:---| :---: | ---:| hubot enable <commandId> | room.enable | Enable the command with a given commandId in your current room. hubot enable all | room.enable | Enable all commands in the current room hubot disable <commandId> | room.disable | Disable the command with a given commandId in your current room. hubot disable all | room.enable | Disable all commands except for this packages command and any commands you've listed as HUBOT_DEFAULT_COMMANDS hubot list commands | room.list-commands | Lists list all the commandIds split into categories: enabled commands and disabled commands hubot toggle respond | room.toggle-response | Toggle whether or not responses will be sent in this room for these commands. (Defaults to false) hubot toggle override | room.toggle-override | Toggles whether or not admin users can override and send commands that are otherwise disabled.

Notes

If you are using hubot-auth, anyone who is admin or anyone with role [room-name]-admin can run these commands. If you aren't using hubot-auth, then anyone can run them.

If your listener doesn't have an id set using listener metadata you won't be able to disable that command.