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

covers

v1.9.1

Published

Selective code coverage tool

Downloads

8

Readme

covers.js

It's always annoyed me trying to write tests & code in node.js that code coverage doesn't have the annotations that I was used to in PHPUnit

This is an attempt to bring some of that functionality to node.js

// exampleCode.js
function foo() {
  bar();
  return bar();
}

function bar() {
  return true;
}

function hello() {
  return true;
}

module.exports = {
  foo: foo,
  bar: bar
}
// myTest.js
const exampleCode = require("exampleCode");
describe("Selective coverage", () => {
  covers(exampleCode.foo);
  it("run", () => {
    exampleCode.foo();
  })
});

Will result in coverage results like:

1x | function foo() {
1x |   bar();
1x |   return bar();
   | }

1x | function bar() {
0x |   return true;
   | }

1x | function hello() {
0x |   return true;
   | }

1x | module.exports = {
   |   foo: foo,
   |   bar: bar
   | }

Instead of what would ordinarily come out:

...
1x | function bar() {
2x |   return true;
   | }
...

This will allow you to write unit tests that test just the method you want, and continue to have integration and end-to-end testing that doesn't effect your code coverage results.

Roadmap

  • [x] nothing selector
  • [ ] selector for named functions
  • [ ] selector for anonymous functions
  • [ ] selector for es6 arrow anonymous functions