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

vitest-reporter-flakiness

v0.0.0-beta.2

Published

A Vitest reporter that identifies and reports flaky tests by tracking test retries and their outcomes.

Downloads

403

Readme

This package provides a Vitest reporter that identifies and reports flaky tests.

A test is considered flaky if it fails in at least one run and passes in a retry run.

Getting Started

Install the package:

npm install vitest-reporter-flakiness --save-dev

Add the reporter to your Vitest configuration. Ensure that you have retries enabled in your Vitest configuration for the reporter to work effectively:

// vitest.config.js
import { defineConfig } from 'vitest/config'
import FlakinessReporter from 'vitest-reporter-flakiness'

export default defineConfig({
  test: {
    // Important: to be able to report flaky tests, you need to set a retry count.
    //  This is because a test is only considered flaky if it passed but had retries.
    retry: 3,
    reporters: [
      new FlakinessReporter({
        outputFile: 'reports/flaky-tests.json',
      }),
    ],
  },
})

In CI, trigger an alert if the reporter generated the report file; for example, in GitHub actions, the workflow could include steps like this:

- name: Run tests
  run: npm test
- name: Report flaky tests
  run: |
    if [ -f "reports/flaky-tests.json" ]; then
      # TODO: this is where you would want to send a notification or create an issue based on the flakiness report.
      echo "Artifacts: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}"
    fi
- name: Upload flaky test report artifact
  if: always()
  uses: actions/upload-artifact@v4
  with:
    name: flaky-tests-report
    path: reports/flaky-tests.json
    if-no-files-found: ignore

Examples

See the example configuration:

This gives the following output in the terminal:

⚠️ Found 1 flaky test(s):
  • src/with-flakiness.test.ts
    └─ flaky tests
      └─ is a flaky test (retry x2)

And generates a file, reports/flaky-tests.json:

{
  "flakyTests": [
    {
      "moduleName": "src/with-flakiness.test.ts",
      "suitePath": ["flaky tests"],
      "testName": "is a flaky test",
      "retries": 2
    }
  ]
}

API

The FlakinessReporter accepts an options object with the following (optional) properties:

  • outputFile (string): The path to the output file where the flakiness report will be saved.
  • disableConsoleOutput (boolean): If set to true, the reporter will not output flaky test information to the console. Default is false.
  • onReport ((report: Report) => void): A callback function that will be called with the