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-config-generator

v1.0.7

Published

☕ Mocha CLI tool to generate a configuration file boilerplate that supports different output formats.

Readme

☕ Mocha Config Generator

Mocha CLI tool to generate a configuration file boilerplate that supports different output formats.

Is it useful? For me, yes. It's a side project, ain't that deep :3

✨ Features

  • Generate configuration files: Easily create .mocharc files for your Mocha tests.
  • Multiple output formats: Supports yaml, yml, json, and js formats.
  • Customizable: Uses a default configuration that can be easily extended in your project.
  • Simple CLI: Easy to use with minimal configuration.

🚀 Installation

npm install -g mocha-config-generator

💻 Usage

mocha-config-gen [options]

Options

  • --format <format>: Output format (yaml, yml, json, js). Defaults to yaml.
  • --version: Outputs the CLI version.
  • --help: Shows more help.

Examples:

  • Configuration file is generated in the directory where the command is run.

  • For jsonc just generate normal json and rename the file.

  • Generate a YAML configuration file (default):

    mocha-config-gen

    or

    mocha-config-gen --format yaml
  • Generate a YML configuration file:

    mocha-config-gen --formal yml
  • Generate a JSON configuration file:

    mocha-config-gen --format json
  • Generate a JavaScript configuration file:

    mocha-config-gen --format js

⚙️ Default Configuration Template

The tool generates a configuration file with the following default settings as boilerplate (the most commonly used):

  • diff: Shows diffs of expected vs. actual values.
  • spec: Glob pattern for test files.
  • extension: Array of file extensions to include.
  • timeout: Timeout in milliseconds for each test.
  • reporter: Mocha reporter to use.
  • require: Modules to require before running tests.
  • slow: Threshold in milliseconds to consider a test slow.
  • grep: Filter tests by string.
  • ignore: Array of files to ignore.
  • ui: Mocha UI to use.
  • forbidOnly: Whether to forbid the use of only.
  • 'watch-files': Files to watch for changes.
  • retries: Number of times to retry failed tests.
  • bail: Whether to exit after the first failed test.
  • color: Whether to use color output.
  • growl: Whether to use Growl notifications.
  • recursive: Whether to search for tests recursively.
  • exit: Whether to exit after all tests have run.

🔗 Links