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

@dotcom-tool-kit/parallel

v2.0.1

Published

This plugin allows you to run Tool Kit tasks in parallel. By default, Tool Kit tasks run sequentially in the order they are specified in a command.

Readme

@dotcom-tool-kit/parallel

This plugin allows you to run Tool Kit tasks in parallel. By default, Tool Kit tasks run sequentially in the order they are specified in a command.

Installation

Install @dotcom-tool-kit/parallel as a devDependency in your app:

npm install --save-dev @dotcom-tool-kit/parallel

Add the plugin to your Tool Kit configuration:

plugins:
	- '@dotcom-tool-kit/parallel'

Usage

To run tasks in parallel, pass them in as the tasks option to the Parallel task.

Tasks

Parallel

Run Tool Kit tasks in parallel

Task options

tasks

An array listing the tasks to run in parallel, and the options to run each task with. Each element in the array is an object with a single key and value; the key is the name of the task to run, and the value is the options object for that task. Other tasks' options are documented in their plugin's readme.

Example
commands:
  run:local:
    - Parallel:
        tasks:
          - Node:
              entry: server/index.js
          - Webpack:
              watch: true
onError

optional

| Value | Description | |-|-| | 'wait-for-others' (default) | If any task errors, wait for the other tasks to complete, and print all the errors at the end. | | 'stop-all' | If any task errors, immediately stop the other tasks, and print the error. |

For long-running tasks, e.g. a Node server and Webpack in watch mode, it's possible for one task to error, but its error logging to be buried by the other tasks' output, meaning you might have missed an error and aren't aware that not everything you expect to be running is still running. In these cases, set onError: stop-all; Tool Kit will exit every Parallel task if one of them errors, so you're always in a consistent state and don't miss any errors.

If you're using Parallel to run shorter tasks in parallel as an optimisation, keep this as the default wait-for-others so every task runs to completion and Tool Kit can show the final results of all the tasks.