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

@edgetesting/playwright-reporter

v1.0.0

Published

Custom Playwright reporter that syncs test results to EdgeTesting — auto-creates bug reports and uploads artifacts on failure

Readme

@edgetesting/playwright-reporter

A custom Playwright reporter that syncs test results to EdgeTesting. On failure it automatically creates a bug report, posts a comment to the linked Jira issue, and uploads trace/video/screenshot artifacts.

Requirements

  • Node.js 18+
  • Playwright 1.40+
  • An EdgeTesting workspace with an API key

Installation

npm install @edgetesting/playwright-reporter

Setup

1. Add to playwright.config.ts

import { defineConfig } from '@playwright/test';

export default defineConfig({
  use: {
    trace:      'on-first-retry',
    video:      'on-first-retry',
    screenshot: 'only-on-failure',
  },
  reporter: [
    ['list'],
    ['@edgetesting/playwright-reporter', {
      apiKey: process.env.EDGETESTING_API_KEY,
      apiUrl: process.env.EDGETESTING_API_URL,
    }],
  ],
});

2. Set environment variables

EDGETESTING_API_KEY=et_xxxx   # from Settings → API Keys
EDGETESTING_API_URL=https://your-edgetesting-instance.com

3. Annotate your tests

import { test, expect } from '@playwright/test';

test('Login works', {
  annotation: { type: 'automation_id', description: 'TC-42' },
}, async ({ page }) => {
  await page.goto('/login');
  // ...
});

Get the TC-xxx ID from EdgeTesting by opening any Jira issue and expanding a test case card.

Options

| Option | Type | Default | Description | |---|---|---|---| | apiKey | string | EDGETESTING_API_KEY env | Your EdgeTesting API key | | apiUrl | string | EDGETESTING_API_URL env | Base URL of your EdgeTesting instance | | uploadArtifacts | boolean | true | Upload trace/video/screenshot on failure |

Annotation formats

// Recommended
annotation: { type: 'automation_id', description: 'TC-42' }

// Shorthand
annotation: [{ type: '@TC-42' }]

What happens on failure

  1. Bug report created in EdgeTesting with the error message and failed step
  2. Comment posted to the linked Jira issue with full details
  3. Playwright trace, video, and screenshot uploaded to the bug report
  4. Jira assignee notified by email and in-app notification

License

MIT