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

grunt-mocha-parallel-extended

v0.2.7

Published

A Grunt task for running mocha test suites in parallel

Downloads

3

Readme

grunt-mocha-parallel

A Grunt task for running mocha test suites in parallel

Intro

this is a extended version of https://www.npmjs.com/package/grunt-mocha-parallel from https://www.npmjs.com/~jkp

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-mocha-parallel-extended --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-mocha-parallel-extended');

The "mocha_parallel" task

Overview

In your project's Gruntfile, add a section named mocha_parallel to the data object passed into grunt.initConfig().

grunt.initConfig({
  mocha_parallel_extended: {
    options: {
      args: function(suiteName) {
        return [];
      },
      env: function(suiteName) {
        return process.env;
      },
      report: function(suite, code, stdout, stderr) {
      },
      done: function(success, results) {
      },
      mocha: './node_modules/.bin/mocha',
      concurrency: os.cpus().length,
      source: './path/*.js'
    },
  },
});

Options

options.args

Type: Function Default value: A function that returns an empty list.

A function that should return a list of mocha options to use when running the named suite.

The first parameter will be the name of the suite or Skipped when running all the skipped tests.

options.env

Type: Function Default value: A function that returns process.env

A function that should return a custom environment hash to use when running the named suite.

The first parameter will be the name of the suite or Skipped when running all the skipped tests.

options.report

Type: Function Default value: A function that logs the standard output followed by the standard error for the named suite.

A function to invoke to report the results of a given suite.

options.done

Type: Function Default value: A function that does nothing.

A function to invoke when all the suites have completed. The first argument is a boolean indicating if all suites succeeded or not, the second is a map between suite name and the output of that suite (code, stderr, stdout).

options.mocha

Type: String Default value: ./node_modules/.bin/mocha

The path to the mocha binary to invoke.

options.concurrency

Type: Number Default value: os.cpus().length * 1.5

Specifies the maxiumum number of concurrent test suites to run.

options.source

Type: String Default value: ./

The path to the test folder to invoke.

Versioning

Releases will be numbered with the follow format:

<major>.<minor>.<patch>

And constructed with the following guidelines:

  • Breaking backwards compatibility bumps the major
  • New additions without breaking backwards compatibility bumps the minor
  • Bug fixes and misc changes bump the patch

For more information on semantic versioning, please visit http://semver.org/.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.