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

cypress-parallel-runner

v1.0.1

Published

Run multiple Cypress spec files in parallel locally — no Cypress Cloud needed. Supports headed mode, multiple browsers, fixtures, localStorage, and custom commands.

Readme

⚡ cypress-parallel-runner

Run multiple Cypress spec files in parallel locally — no Cypress Cloud needed. Free forever.

Install

npm install cypress-parallel-runner --save-dev

Required Setup in Your Cypress Project

1. cypress/plugins/index.js

Add a null check in before:browser:launch to prevent crashes when running with Electron:

on('before:browser:launch', (browser = {}, options) => {
  if (browser.family === 'chromium' && options.preferences && options.preferences.default) {
    options.preferences.default['download'] = { default_directory: config['downloadsFolder'].replace(/\\/g, "\\\\") }
    return options
  }
});

2. cypress.config.js

Make sure reporterOptions has reporterEnabled inside the object:

reporter: "mocha-multi-reporters",
reporterOptions: {
  reporterEnabled: "spec",
  configFile: "cypress/config.json",
},

3. cypress/config.json

Create this file if it doesn't exist. Run this in PowerShell:

[System.IO.File]::WriteAllText("$PWD\cypress\config.json", '{"reporterEnabled": "spec"}')

Usage

As a CLI command

# Run specific specs in parallel
npx cypress-parallel --spec login,checkout,contacts

# Run an entire folder
npx cypress-parallel --spec cypress/e2e/leases

# Run with Chrome
npx cypress-parallel --spec login,checkout --browser chrome

# Run with Edge
npx cypress-parallel --spec login,checkout --browser edge

# Limit parallel workers
npx cypress-parallel --spec login,checkout,contacts --workers 2

# Pass env variables
npx cypress-parallel --spec login --env ENV=staging

As a package.json script

{
  "scripts": {
    "parallel": "cypress-parallel --spec login,checkout,contacts",
    "parallel:chrome": "cypress-parallel --spec login,checkout --browser chrome",
    "parallel:staging": "cypress-parallel --spec login --env ENV=staging"
  }
}

Then run:

npm run parallel
npm run parallel:chrome

Options

| Option | Description | Default | |---|---|---| | --spec | Comma-separated spec names, paths, or folder names | all specs | | --browser | Browser: electron, chrome, edge, firefox | electron | | --workers | Max parallel specs at once | all at once | | --config-file | Path to Cypress config file | cypress.config.js | | --env | Cypress env variables | none | | --specs-dir | Directory to search for specs | cypress/e2e | | --help | Show help | |

How it works

  • Discovers spec files from your cypress/e2e folder
  • Launches each spec simultaneously using cypress run --headed --no-exit
  • Each spec runs in its own browser window
  • Uses your existing cypress.config.js, fixtures, custom commands, and localStorage setup
  • --no-exit keeps the browser open after the test so you can inspect results

Requirements

  • Node.js >= 14
  • Cypress >= 10 installed in your project

License

MIT