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

pipe-slack

v1.1.1

Published

a simple pipe to slack util for

Readme

pipe-slack

A simple util for adding slack to your CLI pipe tool chain.

What?!

That's right! Now you can ls -al | pipe-slack and have the result of your ls printed out in the channel you want by a bot of your choosing.

Config

There are two ways to pass in most of the information that pipe-slack needs. The first of them is to pass it command line arguments for channel, bot name, and emoji for the bot icon. That looks like this:

ls -al | pipe-slack my-channel my-rad-robot :robot_face:

The one exception here is that you still need to provide your webhook url as an ENV var calles SLACK_URL. Best to just toss that in a .zshrc, .bashrc, or something similar right now.

While you are in there you can all specify SLACK_CHANNEL, SLACK_BOT_NAME, and SLACK_EMOJI and not have to pass in anything at all. Letting you simplify the above command to be:

ls -al | pipe-slack

Woot!

Other things to know...

pipe-slack passes the pipe along! So ls -al | pipe-slack | grep 'awesomesauce' might make sense in some cases just like ls -al | grep 'awesomesauce' | pipe-slack does.