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

qunit-cli

v0.2.0

Published

A command line interface for the QUnit testing framework

Downloads

2,533

Readme

qunit-cli

A Node module that adds colorful CLI support for the QUnit testing framework.

screenshot

Usage

There are two ways to use qunit-cli:

  1. Include it at the top of your test files. First, install the module using npm.

     npm install qunit-cli

    And now, require it in your test files:

     if (typeof QUnit == 'undefined') // if your tests also run in the browser...
         QUnit = require('qunit-cli');
        
     // use QUnit as you normally would.

    Note that this module does not introduce QUnit into the global scope like QUnit does in the browser, so you'll have to do that yourself if needed.

    To run, use the node program.

     node mytests.js
  2. Use the command-line testrunner located at bin/qunit-cli, passing it the test files as arguments. If you install the module globally using npm, you can use the qunit-cli command which will be installed into your PATH.

     npm install qunit-cli -g
     qunit-cli mytests.js

    This will introduce QUnit into the global scope like QUnit does in the browser, so you don't need to modify the tests themselves. You can use both methods in the same test files without problems.

Command line options

There are several command line options available when running your tests using qunit-cli that mimic some of the options in the standard browser-based QUnit testing interface. They are:

--module, -m    Limits testing to an individual module
--test,   -t    Limits testing to a single test (by number)
--quiet,  -q    Flag to hide passed tests from the output

The command-line test runner has some additional options available:

--code,   -c    Path to code loaded globally. You can prefix a namespace
                using a colon (:)

Here are some examples:

# code exports are added to global namespace
qunit-cli -c /path/to/code test.js

# code exports are added to ns namespace
qunit-cli -c ns:/path/to/code test.js

License

qunit-cli is released under the MIT license.