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

@nexxspace/campsite

v1.0.16

Published

Script to help improve test coverage

Downloads

126

Readme

Campsite

The Pitch

Have you ever heard of a Boy Scout Rule that says

   "Try and leave this world a little better than you found it."

You can also apply this rule in software development as well. Here is another quote from Uncle Bob:

   "Always leave the code you're editing a little better than you found it."

Then you might ask question, How do I know when I am editing the code if I have made it better or worse?

   Have we made our test coverage better or have we made it worse than before?

Campsite can show you exactly that. It compares your unit test coverage against a baseline ("code when you found it"). It then gives you a concise report of areas of improvement and mess that we are leaving behind.

Installation

Lets install campsite globally.

npm install @nexxspace/campsite jest

How it works

  1. Before you make any changes in the code. Evaluate the test coverage of current code and form a baseline. To do that, run the following command in your project.

     $ campsite --baseline

    This in addition to running all unit tests, it also creates a baseline file capturing the jest coverage statistics.

  2. Now change your code. Don't forget to add some unit tests :)

  3. Now, lets compare it against the baseline we saved earlier in (1), by running the following command.

     $ campsite

    This produces a report that looks something like this:

  4. campsite shows us the areas we:

    • made some improvements. The "+" (in green)
    • made it worse. The "-" (in red) .