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

@qualflare/cypress

v0.1.0

Published

Native Cypress reporter for the Qualflare test-management platform.

Readme

@qualflare/cypress

A native Cypress reporter for Qualflare — uploads test results directly from your Cypress run: suite/test status, real retry counts, screenshots, step-by-step command traces, and author-facing metadata (labels, links, tags, custom attachments). No post-hoc file parsing, no intermediate report format.

Install

npm install --save-dev @qualflare/cypress

Requires Cypress >=12.0.0 <15.0.0 (installed separately as a peer dependency) and Node >=18.

Quickstart

// cypress.config.ts
import { defineConfig } from 'cypress';
import { qualflareCypress } from '@qualflare/cypress/plugin';

export default defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      return qualflareCypress(on, config, {
        environment: 'staging',
      });
    },
  },
});
// cypress/support/e2e.ts
import '@qualflare/cypress';

Set your token via the QUALFLARE_TOKEN environment variable (or the token plugin option):

QUALFLARE_TOKEN=<your-token> npx cypress run

That's it — suite/test results, retries, and automatic-on-failure screenshots upload as one Launch at the end of the run. See examples/basic/ for a complete runnable project.

Enriching your tests

import { qualflare } from '@qualflare/cypress';

it('logs in with valid credentials', () => {
  qualflare.label('epic', 'Authentication');
  qualflare.tag('smoke');

  qualflare.step('fill in credentials', () => {
    cy.get('#email').type('[email protected]');
    cy.get('#password').type('correct-horse-battery-staple');
  });

  qualflare.step('submit and verify redirect', () => {
    cy.get('#submit').click();
    cy.url().should('include', '/dashboard');
  });
});

See docs/METADATA-API.md for the full reference (labels, links, tags, description, priority, parameters, custom attachments, nested steps).

Configuration

Every option can be set either as a plugin option (qualflareCypress(on, config, options)) or via a QUALFLARE_* environment variable. Full table, precedence rules, and auto-detection behavior (git branch/commit, CI provider/build/PR, browser/OS) in docs/CONFIGURATION.md.

Known limitations

  • No video upload — Qualflare has no blob/video-attachment storage yet.
  • One cypress run process uploads as one Launch — sharded CI setups get multiple Launches.
  • Command-log step nesting is two levels only (Cypress's own API limit) — qualflare.step() supports arbitrary nesting depth.

Full details in docs/LIMITATIONS.md.

Development

npm run typecheck   # tsc --noEmit
npm run lint        # eslint .
npm run build       # tsup — dual ESM+CJS, .d.ts
npm test            # unit tests (vitest)
npm run test:integration   # spawns real cypress run against a fixture project + mock server

Release process: see RELEASING.md.

License

Apache-2.0