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

flaky-detective

v1.0.0

Published

Detect flaky Playwright tests, classify root causes, generate quarantine CI configs.

Readme

Flaky Test Detective

Run Playwright tests repeatedly to detect flakiness.
If flaky, generates a GitHub Actions workflow to quarantine the test (run nightly, non‑blocking).

Usage

npx flaky-detective "tests/login.spec.ts" 10
  • Run npx flaky-detective

  • First argument = test file pattern (e.g., "tests/login.spec.ts")

  • Second argument = number of runs (default 10 if omitted)

Example

Running tests/login.spec.ts 10 times... ✓✗✓✗✓✓✗✓✓✗

6/10 passed FLAKY

--- Quarantine Config ---

Copy to .github/workflows/quarantine.yml

name: Quarantined Test on: schedule: - cron: '0 2 * * *' jobs: quarantine: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - run: npm ci - run: npx playwright install --with-deps chromium - run: npx playwright test tests/login.spec.ts continue-on-error: true

--- NOTE: The YAML uses the exact test path you provided. In this example, it's tests/login.spec.ts.---

Quarantine step‑by‑step

  1. Run the CLI. If flaky, copy the YAML block from --- Quarantine Config ---.

  2. In your repository, create the folder .github/workflows/ (if it doesn't exist).

  3. Save the YAML as quarantine-[test-name].yml.

  4. Commit and push. GitHub will run the test nightly at 2 AM with continue-on-error: true.

What it does

  1. Runs your test N times

  2. Detects flakiness (inconsistent pass/fail)

  3. Prints a YAML file you can copy into .github/workflows/ to move the test to a nightly, non‑blocking job

What it does NOT do

  • Automatically fix flaky tests

  • Reliably classify root causes (we try keyword matching, but often return "unknown")

  • Rewrite imports or handle nested test paths (the YAML assumes the test file is in the root)

License

MIT

Links

  • https://github.com/flaky-detective/flaky-detective
  • https://github.com/flaky-detective/flaky-detective/issues