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

github-coverage-robot

v1.0.0

Published

Create code coverage status and comment on code coverage in PRs.

Downloads

4

Readme

Creates a github 'status' for every build which passes only if coverage hasn't fallen compared to master.

How it Works

The basic idea is, you run github-coverage-robot as part of your build process. On master branch, github-coverage-robot will upload a small JSON file to Amazon S3 with details about your code coverage. After any build, github-coverage-robot will fetch the JSON data from S3, and generate a github status for the build which will pass if coverage is as good as or better than master, and fail if it's worse than master.

Usage:

Install with:

npm --save github-coverage-robot

First, create a github access token repo and repo_public permissions. Second, create a bucket on S3 to store coverage reports, and obtain an AWS access key ID and secret access key. On your CI server, set up the following environment variables (note that you should NOT commit these to source control in an open source project):

export GITHUB_ROBOT_ACCESS_TOKEN=[github access token]
export AWS_ACCESS_KEY_ID=[...]
export AWS_SECRET_ACCESS_KEY=[...]

Then, when running your tests on the CI server, generate your coverage numbers and run:

./node_modules/.bin/github-coverage-robot \
    --bucket [s3Bucket] \
    --project [owner/repo] \
    --coverage [percent]

where s3Bucket is the name of the bucket you created to hold reports, owner/repo is the github user and repo name for your project, and percent is a float value representing the coverage of your project. For example:

./node_modules/.bin/github-coverage-robot \
    --bucket ci-reports \
    --project benbria/node-github-coverage-robot \
    --coverage 89.34

You can optionally specify --branch and --sha, but github-coverage-robot should be smart enough to figure them out in most cases.