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

mocha-duplicate-reporter

v0.2.1

Published

Finds mocha tests that use the exact same full name

Downloads

59

Readme

Mocha Duplicate Reporter

Build Status Code Climate Downloads Version

Mocha seems perfectly content to let you create multiple tests that share the same name, but some CIs (caugh Teamcity caugh) are not so happy. They will just refuse to acknowledge the duplicates, and you are stuck wondering why your CI reports 7 test less than you are seeing locally. Once you build up a large enough test suite, it's pretty hard to figure out what the offending tests are. Well, no more! Use this quick reporter and see who those pesky bastards are.

Install

npm install -save-dev mocha-duplicate-reporter

Usage

mocha --reporter mocha-duplicate-reporter

Output

Regex report: 9-8-0-1-4

9 total tests:
   8 passed
   0 failed
   1 pending
   4 duplicate names

Duplicate test names:
[Example] is obviously written in a loop
[Example] tests the same thing over and over
[Example] performs a vague action
[Example] forks forks forks

Run npm test on the repo to see the original test file that produces this output.

Just in case you want to automate this

To hint to those devs who wrote the poorly named tests, I suggest you make the build fail, so here is a free regular expression for you:

var regex = /Regex report\:\s?([0-9]+)-([0-9]+)-([0-9]+)-([0-9]+)-([0-9]+)/;
var match = output.match(regex);

if (match) {
    var total = match[1];
    var pass = match[2];
    var fail = match[3];
    var pending = match[4];
    var dups = match[5];
    
    if (+dups) {
        console.log('fail with %d duplicates', +dups);
    }
}