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 🙏

© 2025 – Pkg Stats / Ryan Hefner

sigh-mocha

v0.1.4

Published

Sigh plugin for running mocha in a subprocess

Downloads

19

Readme

sigh-mocha

Runs mocha with the provided options each time the plugin receives a value. If the tests are already running then the process is killed and the tests are run in a new process. The plugin maintains a cache of at least two processes with the mocha state set up ready to run a test to ensure minimal latency.

Example

npm install --save mocha then add this to your sigh.js:

var mocha, glob, babel, write

module.exports = function(pipelines) {
  pipelines['build:source'] = [
    glob({ basePath: 'src' }, '**/*.js'),
    babel(),
    write('build'),
    mocha({ files: 'build/**/*.js' })
  ]
}

sigh-mocha can currently only work with files written to the fs so it should receive output events from the write plugin or any similar plugin that writes data to the filesystem.

The options must be provided and must contain the files entry which is a glob expression matching the test files to run. All other fields are passed as the first parameter to the mocha API's Mocha constructor. This can be used to customise mocha, the documentation for these options be found here.

TODO

  • Glob relative to basePath of events.
  • Call runner.uncaught() (see gult-mocha).