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

@tracecov/playwright

v0.23.4

Published

Automatic OpenAPI coverage capture for Playwright API testing.

Readme

@tracecov/playwright

Automatic OpenAPI coverage capture for Playwright API testing.

Install

npm install -D @tracecov/playwright

Usage

Swap the test import and add the reporter.

// tests/api.spec.ts
import { test } from '@tracecov/playwright';
import { expect } from '@playwright/test';

test('lists pets', async ({ request }) => {
  const res = await request.get('/pets');
  expect(res.ok()).toBeTruthy();
});
// playwright.config.ts
import { defineConfig } from '@playwright/test';

export default defineConfig({
  use: { baseURL: 'http://localhost:8080' },
  reporter: [
    ['list'],
    ['@tracecov/playwright/reporter', {
      schema: './openapi.json',
      report: { html: 'coverage.html', markdown: 'coverage.md' },
      thresholds: { operations: 80 },
    }],
  ],
});

A reporter configured with neither report nor thresholds emits nothing — set at least one to get output.

Contexts you create yourself (request.newContext(), global setup) aren't covered by the fixture — wrap them:

import { wrapRequest, createDirRecorder, interactionsDir } from '@tracecov/playwright';

const { recorder, flush } = createDirRecorder(interactionsDir());
const ctx = wrapRequest(await request.newContext(), recorder);
// ... use ctx ...
flush();

Limitations

  • Context-level headers. Only per-call headers are recorded. Headers set on the context (newContext({ extraHTTPHeaders }), auth) are merged by Playwright with no public getter, so coverage of header parameters supplied that way is missed.
  • Network errors with relative paths. A request that fails before a response, when its URL is relative to a context baseURL, isn't recorded as an operation error (Playwright exposes no baseURL to resolve it). Successful-response coverage is unaffected.
  • Interactions directory. Workers and the reporter share os.tmpdir()/tracecov-playwright-<cwd-hash>. Set TRACECOV_PLAYWRIGHT_DIR to override it — e.g. to isolate concurrent runs that share one working directory.