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

@qlens/cypress-reporter

v0.1.0

Published

Cypress plugin that posts run summaries and per-spec results to QualityPilot (qlens.dev) CI ingest.

Readme

@qlens/cypress-reporter

npm version npm downloads license Powered by QualityPilot

Install in 30 seconds

npm install --save-dev @qlens/cypress-reporter
# wire it into setupNodeEvents in cypress.config.ts (snippet below)
QLENS_API_KEY=qlens_... npx cypress run  # get key at qlens.dev/dashboard/keys
// cypress.config.ts
import { defineConfig } from "cypress";
import { registerQlensReporter } from "@qlens/cypress-reporter";

export default defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      registerQlensReporter(on, { sendCases: true });
      return config;
    },
  },
});

What you get

Need a key?

Sign in at https://www.qlens.dev with GitHub. Free tier includes 10 auto-fixes/month.


Posts Cypress run summaries + optional per-spec results to QualityPilot CI ingest. Zero code changes inside specs, one snippet in cypress.config.ts.

Why a plugin (not a Mocha reporter)?

Cypress runs each spec file in its own browser process and exposes the mocha reporter slot only to per-spec, in-browser reporters. To get a single aggregated upload across the whole run we hook into the plugin event channel (after:spec, after:run) which fires in the parent Node process. Same payload as @qlens/jest-reporter and @qlens/playwright-reporter.

Configure

Create an API key at qlens.dev/dashboard/keys (Pro+ plans), then:

// cypress.config.ts
import { defineConfig } from "cypress";
import { registerQlensReporter } from "@qlens/cypress-reporter";

export default defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      registerQlensReporter(on, {
        // apiKey: process.env.QLENS_API_KEY,       // default
        // repo: process.env.GITHUB_REPOSITORY,     // default
        sendCases: true,   // include per-case data (default: false)
        maxCases: 5000,    // hard cap
      });
      return config;
    },
  },
});

Set QLENS_API_KEY in your CI secrets.

Environment variables (auto-detected)

| Var | Purpose | |-----|---------| | QLENS_API_KEY | Required. Generate at https://www.qlens.dev/dashboard/keys | | QLENS_ENDPOINT | Override ingest URL (self-hosted) | | GITHUB_REPOSITORY | Repo in owner/name — set by GitHub Actions | | GITHUB_SHA | Commit SHA — set by GitHub Actions | | GITHUB_REF_NAME | Branch name — set by GitHub Actions |

Flakiness

Cypress retries are respected. If a test ends passed but its attempts[] array has more than one entry, it's counted as flaky, not passed. This shows up in the QualityPilot dashboard as a flakiness trend.

Enable retries in your config so flakiness has a chance to surface:

export default defineConfig({
  retries: { runMode: 2, openMode: 0 },
  // ...
});

Fail-safe

The reporter never fails the test run. Network errors, 4xx/5xx from the ingest, missing API key — all logged ([qlens]) and ignored. Your CI green stays green.

GitHub Actions example

- name: Run Cypress
  env:
    QLENS_API_KEY: ${{ secrets.QLENS_API_KEY }}
  run: npx cypress run

Docs

Full API schema: qlens.dev/docs/ci-ingest.

License

MIT — built by IK Lab.