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

@amykit/plugin-slack

v0.6.0

Published

A Slack thread per piece of work, over the Web API, as the conversation port.

Readme

@amykit/plugin-slack

A Slack thread per piece of work, over the Web API, as the conversation port.

A plugin for amy. It provides the conversation port.

Install

# Add @amykit/plugin-slack to amy.yaml, then install configured plugins:
amy init --install

Then name it in ~/.amy/config.yaml:

workflows:
  your-profile:
    plugins:
      - "@amykit/plugin-slack"

Configuration

plugins:
  "@amykit/plugin-slack":
    channel: <string>
    defaultRetryAfterSeconds: 60
    directory: "slack"
    maxRateLimitRetries: 5
    operator: <string>
    retentionDays: 30
    token: <string>

| Setting | Type | Required | Default | What it is | | :-- | :-- | :-- | :-- | :-- | | channel | string | yes | | the channel id every work thread opens in, such as C0XXXXXXX — an id, not a name | | defaultRetryAfterSeconds | number | no | 60 | how long to wait after a 429 that carries no Retry-After; one names its own wait, and that wins | | directory | string | no | slack | where each work item's thread is remembered, relative to the state directory | | maxRateLimitRetries | number | no | 5 | how many times a call Slack rate limits (HTTP 429) is waited out and tried again before it fails | | operator | string | yes | | the user id, such as U0XXXXXXX, whose replies are answers; everybody else's are ignored | | retentionDays | number | no | 30 | days a downloaded file or a thread's memory stays unused before it is pruned, 0 to keep everything. A pruned file is fetched again when its reply is read; a pruned thread means the next question opens a new one | | token | string | yes | | where the bot token lives: env:SLACK_BOT_TOKEN or file:<path>#<KEY>, never the token itself |

Every field is checked at boot against the schema this package declares. A key that is not one of the above is a refusal naming the plugin and the key, not a setting that silently never applied.

Where the reasoning is

Licence

MIT