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

@adeattwood/diff-cov

v0.2.0

Published

Simple CLI to get test coverage on a diff

Readme

Diff Cov

Simple CLI to print diffs highlighted with test coverage status

Example Output

Installation

You can install the package with npm

npm i -g @adeattwood/diff-cov

You can run it directly with npx

npx @adeattwood/diff-cov

Setup

For diff-cov to get the diff to your default branch, you must set up your origin/HEAD ref. To test to see if you have this set up, run.

git rev-parse --abbrev-ref origin/HEAD

This should print out the origin ref to your default branch for this repo it will print origin/0.x. If you get an unknown ref error, then you will need to link origin/HEAD to your default branch with the below command.

git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/0.x

Note: Make sure you change 0.x for your default branch name typically main or development

Usage

Before you run diff-cov you must run your test suite with coverage and output a lcov coverage file. You must also have all your changes committed to ensure it's included in the output.

Once you are ready to go, you can run diff-cov to print your diff highlighted with coverage status. Any line not included in the coverage report will not be highlighted and hit and missed lines will be colored green and red. You can use the --coverageFile flag to specify the path to your coverage report if its not in the default location of ./lcov.info

diff-cov
diff-cov --coverageFile coverage/lcov.info

A report is printed at the bottom and colored with a threshold of 90% anything below this percentage coverage will be colored red.