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

istanbul-coverage-slack

v0.0.8

Published

Sends coverage report on Slack webhook

Readme

istanbul-coverage-slack

Sends coverage reports on Slack webhook.

Build Status Coverage Status

Install

npm i --save-dev istanbul-coverage-slack

Before You run

Make sure You configure webhook on Your Slack team https://api.slack.com/incoming-webhooks

Put file shout.json (example below) into root directory of Your project.

{
  "reports": {
    "files": ["coverage/coverage.json"]
  },
  "slack": {
    "username": "Chuck Norris",
    "channel": "reports",
    "icon": "https://s3-us-west-2.amazonaws.com/slack-files2/bot_icons/2016-06-16/51472942259_48.png",
    "timeout": 5000
  },
  "thresholds": [
    {
      "percent": 100,
      "words": "excellent",
      "color": "good"
    },
    {
      "percent": 80,
      "words": "nice",
      "color": "warning"
    },
    {
      "percent": 50,
      "words": "do it better",
      "color": "warning"
    },
    {
      "percent": 40,
      "words": "mad",
      "color": "danger"
    },
    {
      "percent": 0,
      "words": "crap",
      "color": "danger"
    }
  ]
}

Notice: Coverage report for You project must be generated. If not generate coverage report via istanbul. This coverage report should correspond with reports.files section located in shout.json.

Run

Inside Your project root directory You can use on of following run sequence.

Via arguments

./node_modules/.bin/shout --SLACK_WEBHOOK_URL=https://hooks.slack.com/...

Via env variables

export SLACK_WEBHOOK_URL=https://hooks.slack.com/... && ./node_modules/.bin/shout

Via npm task

...
"shout": "./node_modules/.bin/shout",
...
export SLACK_WEBHOOK_URL=https://hooks.slack.com/... && npm run shout

Additional parameters

  • --BRANCH_NAME - name of the branch
  • --PROJECT_NAME - name of the project

You can also override shout.json factors

  • --SLACK_CHANNEL - selected channel of Your Slack team
  • --SLACK_TIMEOUT - in milliseconds request timeout to slack webhook (default 5000ms)
  • --LOG - debug for verbose

This will send coverage report into Slack webhook and Your message should look like below

Message example

Debug

If You have troubles with receiving messages launch for more information about any issues.

./node_modules/.bin/shout --LOG=debug