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

nonly

v1.0.1

Published

Mocha plugin to prevent accidental only

Downloads

3

Readme

nonly

A plugin for mocha that will cause your test suite to fail if less than 90% of the tests in the suite are executed.

This helps to catch erroneous .only statements that might be added for development/debugging but get accidentally committed.

Usage

To use simply pass nonly as a value to the --require flag for mocha

$ mocha --require nonly

Or add the following line to your mocha.opts file:

--require nonly

How is this different to mocha's --forbid-only?

The --forbid-only flag causes test suites to fail completely without executing when .only is used. This means that if someone is using .only locally for development and debugging then they'll likely also remove this flag to allow the test suite to run.

That means they're potentially likely to also accidentally commit the removal of this flag.

Using nonly allows the test suites to run exactly as normal, and only fails if test execution falls below 90%.