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

@appsurify-testmap/rrweb-playwright-plugin

v3.60.1-alpha.1

Published

```ts // playwright.config.ts — no `declare module` needed, the plugin augments // PlaywrightTestOptions with `testmap`. export default defineConfig({ reporter: [['@appsurify-testmap/rrweb-playwright-plugin/reporter']], use: { testmap: { out

Readme

@appsurify-testmap/rrweb-playwright-plugin

Configuration

// playwright.config.ts — no `declare module` needed, the plugin augments
// PlaywrightTestOptions with `testmap`.
export default defineConfig({
  reporter: [['@appsurify-testmap/rrweb-playwright-plugin/reporter']],
  use: {
    testmap: {
      outputReportDir: 'test-results/playwright/ui',
      recordingOpts: { /* JSON-serializable rrweb record options */ },
      settleBeforeStop: { networkIdle: true, domQuietMs: 300, timeout: 5000 },
    },
  },
});

settleBeforeStop (default: enabled)

A test usually ends on an assertion that the first paint already satisfies (URL, a heading) while API data is still loading. Before stopping the recorder the plugin therefore:

  1. waits until no request has been in flight for 500 ms (networkIdle) — tracked per page, so SPA requests after a client-side route change count too (Playwright's own networkidle fires once per document and would miss them); EventSource/WebSocket are ignored;
  2. waits until the DOM has had no mutations for domQuietMs;
  3. takes a final FullSnapshot if the DOM changed since the last one.

All of it is capped by timeout; when the cap is hit, a step fails, or the page navigates/closes, the recorder simply stops (logged via console.debug, the test is not affected). The wait is skipped for tests that did not pass.

Cost: a page that is already idle stops after ~domQuietMs. The wait runs in the page fixture's teardown, i.e. in Playwright's after-hooks budget (a separate budget equal to the test timeout), not in the test body's timeout. Since Playwright 1.60 it is part of the reported test duration.

settleBeforeStop: false restores the stop-immediately behaviour.

When the recorder stops

In the page fixture teardown — after the test's afterEach hooks, so actions performed there are recorded too. The plugin does not hook Playwright's private "test function finished" callbacks: they run before afterEach, and their shape differs between versions (_onDidFinishTestFunction method, _onDidFinishTestFunctionCallback — which Playwright's artifacts recorder also assigns — and, since 1.60, the _onDidFinishTestFunctionCallbacks set), which made the stop point depend on the installed Playwright version.

Notes