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

@brittlehq/playwright-reporter

v0.2.1

Published

Brittle reporter for Playwright — streams test results to the Brittle Hub in real time

Readme

@brittlehq/playwright-reporter

Stream Playwright test results to Brittle — failure triage, AI-grouped errors, flake history, command + network logs — without changing how your tests run.

Install

pnpm add -D @brittlehq/playwright-reporter
# or: npm i -D @brittlehq/playwright-reporter
# or: yarn add -D @brittlehq/playwright-reporter

Configure

Add the reporter to playwright.config.ts:

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

export default defineConfig({
  reporter: [
    ['list'],
    [
      '@brittlehq/playwright-reporter',
      {
        url: process.env.BRITTLE_URL,
        token: process.env.BRITTLE_TOKEN,
      },
    ],
  ],
});

Set the env vars in your shell or CI:

export BRITTLE_URL=https://brittle.dev          # or your self-hosted hub
export BRITTLE_TOKEN=brt_svc_xxxxxxxxxxxxxxxx   # mint at Project → Settings → Tokens

In CI, set BRITTLE_TOKEN as a secret and BRITTLE_URL as an environment variable in the workflow.

All options

{
  url?: string;              // defaults to process.env.BRITTLE_URL
  token?: string;            // defaults to process.env.BRITTLE_TOKEN
  runName?: string;          // groups parallel workers into one Run row
  target?: string;           // 'prod' / 'staging' / app version label
  tags?: string[];           // e.g. ['nightly', 'smoke']
  // Explicit git overrides — only set when CI env is more reliable than `git`
  branch?: string;
  commitSha?: string;
  commitMessage?: string;
  prUrl?: string;
}

Git context (branch, commit, PR) is auto-detected from the working tree.

Run

pnpm exec playwright test

Results appear in the dashboard within a few seconds of onEnd.

Debug logging

The reporter is quiet by default — only warnings (missing token, upload failures) print to stderr. To see verbose per-test debug output (onTestEnd events, retry attempts, individual API calls), set:

export BRITTLE_DEBUG=1

Useful when triaging "test ran but didn't show up in the dashboard" issues. Safe to leave on in CI if you want richer logs.

License

Apache-2.0