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

@flakeytesting/cypress-reporter

v0.9.0

Published

Cypress reporter for Flakey — uploads results, screenshots, videos, and DOM snapshots

Readme

@flakeytesting/cypress-reporter

Cypress reporter + plugin + support bundle for the Flakey test reporting dashboard. Uploads results, screenshots, videos, and (with @flakeytesting/cypress-snapshots) DOM snapshots, and streams per-test events live as the suite runs.

Install

pnpm add -D @flakeytesting/cypress-reporter @flakeytesting/cypress-snapshots @flakeytesting/live-reporter
# or
npm install --save-dev @flakeytesting/cypress-reporter @flakeytesting/cypress-snapshots @flakeytesting/live-reporter

cypress is a required peer (>=12.0.0). The snapshots + live-reporter packages are optional peers — install them only if you want DOM snapshots and live streaming.

Quick start

Two changes to your Cypress config:

// cypress.config.ts
import { defineConfig } from "cypress";
import { setupFlakey } from "@flakeytesting/cypress-reporter/plugin";

export default defineConfig({
  reporter: "@flakeytesting/cypress-reporter",
  reporterOptions: {
    url:    process.env.FLAKEY_API_URL,
    apiKey: process.env.FLAKEY_API_KEY,
    suite:  "my-app-e2e",
  },
  e2e: {
    setupNodeEvents(on, config) {
      return setupFlakey(on, config);
    },
  },
});

Add the reporter's support file (captures Cypress command logs for the error modal) and, optionally, the snapshots support file (DOM snapshots per command):

// cypress/support/e2e.ts
import "@flakeytesting/cypress-reporter/support";
import "@flakeytesting/cypress-snapshots/support"; // optional — only if you installed @flakeytesting/cypress-snapshots

Then run as usual:

FLAKEY_API_URL=https://flakey.your-domain.com \
FLAKEY_API_KEY=fk_xxx... \
cypress run

What setupFlakey wires up

setupFlakey(on, config, opts?) composes three things behind one call:

  • Result uploads — POSTs the run + screenshots + videos to /runs/upload at end-of-run.
  • DOM snapshots (when @flakeytesting/cypress-snapshots is installed) — captures the DOM at each command step. Snapshots stream live to the backend if a live run is active; otherwise they batch with the end-of-run upload.
  • Live streaming (when @flakeytesting/live-reporter is installed) — opens a live run via POST /live/start, fires per-test test.started / test.passed / test.failed events as the suite runs, sends a 30s heartbeat so quiet suites don't auto-abort, and calls POST /live/:runId/abort on SIGINT/SIGTERM so the dashboard clears the LIVE badge.

Opt out of either layer via setupFlakey(on, config, { snapshots: false, live: false }).

Reporter options

| Option | Type | Fallback | Notes | |--------|------|----------|-------| | url | string | FLAKEY_API_URL env | Backend base URL. Required. | | apiKey | string | FLAKEY_API_KEY env | API key. Required. | | suite | string | FLAKEY_SUITE env, then "default" | Suite name shown in the dashboard. | | branch | string | env chain | BRANCHGITHUB_HEAD_REFGITHUB_REF_NAMEBITBUCKET_BRANCH | | commitSha | string | env chain | COMMIT_SHAGITHUB_SHABITBUCKET_COMMIT | | ciRunId | string | env chain | CI_RUN_IDGITHUB_RUN_IDBITBUCKET_BUILD_NUMBER | | release | string | FLAKEY_RELEASE env | Release version — backend upserts release + links run | | environment | string | FLAKEY_ENVTEST_ENV env, then config.env.environment / config.env.name | Target env label (e.g. qa, stage) | | verbose | boolean | FLAKEY_VERBOSE=1 env | Logs upload success / live-run progress |

Per-test screenshot streaming

Each PNG written by Cypress is POSTed to /live/:runId/screenshot the moment after:screenshot fires, with the spec path and full test title attached so the backend can link it directly to the test row. On a successful upload the local file is unlinkSynced — the end-of-run batch's directory walk naturally skips it. This prevents a long failure-heavy suite from filling the CI runner's disk before after:run ever fires.

Compatibility

  • Cypress: >=12.0.0 (required peer)
  • Node: 20+
  • Cypress 15+: the reporter and plugin live in different processes; this package's process-ancestry walk handles that automatically (no pid-based file matching).

Links