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

@nx-extend/e2e-runner

v13.1.1

Published

<a href="https://www.npmjs.com/package/@nx-extend/e2e-runner" rel="nofollow"> <img src="https://badgen.net/npm/v/@nx-extend/e2e-runner" alt="@nx-extend/e2e-runner NPM package"> </a>

Readme

@nx-extend/e2e-runner

Nx plugin to start your API and then run the Cypress/Playwright E2E tests.

Features

  • Start multiple targets before running tests
  • Health check URLs to ensure targets are ready
  • Support for Cypress, Playwright, and custom runners
  • Configurable retry attempts for health checks
  • Optional log forwarding from targets
  • Reuse existing servers option

Setup

Install

npm install -D @nx-extend/e2e-runner
nx g @nx-extend/e2e-runner:add

Usage

Available Options

All options of the specified runner are available:

  • @nrwl/cypress:cypress options (if runner = cypress)
  • @nx-extend/playwright:test options (if runner = playwright)
  • @nx/playwright options (if runner = @nx/playwright)
  • @nx/workspace:run-commands options (if runner = run-commands)

Target Configuration

The targets option is used to define targets that should be started before running the tests. Each target can be configured with the following options:

{
  target: string // The target to run.
  checkUrl?: string // The url to check if the target is "live", a target is live if this url returns a status-code in the 200 range.
  checkMaxTries?: number // The amount of times the `checkUrl` is tried before failing, there is a two second delay between tries.
  env?: { [key: string]: string } // Extra parameters provided to the target on startup.
  reuseExistingServer?: boolean // Set to true to allow using a previously started target.
  rejectUnauthorized?: boolean // Set to false to allow the use of self-signed certificates in your target.
  logging?: boolean // Set to true to forwards the logs of the target, set to false to hide the logs of the target. When undefined, the logs are only forwarded with the `--verbose` flag.
}

Example Configuration

{
  "e2e": {
    "executor": "@nx-extend/e2e-runner:run",
    "options": {
      "runner": "playwright",
      "targets": [
        {
          "target": "app:serve",
          "checkUrl": "http://localhost:4200/",
          "checkMaxTries": 50,
          "rejectUnauthorized": true
        },
        {
          "target": "api:serve",
          "checkUrl": "http://localhost:9000/health",
          "checkMaxTries": 50,
          "logging": false
        }
      ]
    }
  }
}

How It Works

  1. The executor starts all configured targets in parallel
  2. For each target with a checkUrl, it performs health checks
  3. Once all targets are healthy (or max tries reached), the E2E tests run
  4. After tests complete, all started targets are terminated