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

@hootlens/playwright

v0.1.2

Published

Playwright fixture that records a test run as a Hoot Lens test visit and returns the narrative and snags.

Readme

@hootlens/playwright

A Playwright fixture that records a test run as a Hoot Lens test visit and hands the recording back, so a coding agent (or any test) can read what the run did and fail on snags: pile-ups, no-shows and misfires.

Test visits are marked with a controlled-validation variant. Hoot Lens keeps them but never counts them in traffic, findings, heatmaps or plan usage.

// playwright.config.ts
import { defineConfig } from '@playwright/test';
import type { HootlensTestOptions } from '@hootlens/playwright';

export default defineConfig<HootlensTestOptions>({
  reporter: [['list'], ['html'], ['@hootlens/playwright/reporter']],
  use: {
    hootlensOptions: { projectId: process.env.HOOTLENS_PROJECT_ID, token: process.env.HOOTLENS_PAT, controlled: true },
  },
});
// checkout.spec.ts
import { test, expect } from '@hootlens/playwright';

test('paying with a card', async ({ page, hootlens }) => {
  await hootlens.start();                  // before page.goto()
  await page.goto('/checkout');
  await page.getByRole('button', { name: 'Pay' }).click();
  await expect(page.getByText('Thank you')).toBeVisible();
  await hootlens.expectNoSnags();          // fails with the narrative and the replay link
});

| Call | Returns | | --- | --- | | hootlens.start({ projectId?, label? }) | The handle. Marks the visit controlled; adds the tracker to a page without the Hoot Lens tag. | | hootlens.flush() | Waits until the collector has the recording. Throws a HootlensError that names the fix on a refusal. | | hootlens.recording() | { projectId, sessionId, recordingId?, recordingIds, variant, dashboardUrl } | | hootlens.narrative() | { available: true, text, steps, snags: { pileUps, noShows, misfires, total } ... }, or { available: false, note, recording } without a token | | hootlens.expectNoSnags({ allow? }) | The narrative, or throws with it |

A local dev server must be allowed first: the project owner chooses Allow localhost for testing in Installation. Reading narratives needs a personal access token with the read scope in HOOTLENS_PAT.

Full guide for agents, CI usage, errors and privacy: hootlens.com/docs/TESTING-WITH-HOOT-LENS.md.

License

MIT