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

@skeptools/plugin-slack

v0.0.15

Published

A Slack implementation for [Skep](https://github.com/skeptools/skep-core).

Downloads

14

Readme

Skep: Slack plugin

A Slack implementation for Skep.

Features

This plugin will create the following for each team in the org:

  1. A Slack user group for the team, so it can be called out in Slack with @team-name (paid version only).
  2. A Slack user group for each sub-team, e.g. devs-only, etc (paid version only). Sub-teams are defined at the org level as a map of sub-team-name => function that filters members of the team based on their Person properties.
  3. A private Slack channel for the team (paid version only). The Slack user group is used to define membership in this channel. This can optionally be turned off. The standard prefix for the channel name is defined at the org level.
  4. A public Slack channel for the team. The Slack user group is used to define membership in this channel (paid version), or team members will need to join manually (free version). This can optionally be turned off.