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

@gate-forge/pack-playwright

v0.19.2

Published

Gateforge Playwright evidence pack: loopback witness service, engine-side adapter execution, trusted evidence fixture, verdict reporter.

Readme

Writing witnessed journeys

A witnessed journey must exercise the real application behavior and verify the result that users depend on. A passing test declaration is not proof: only a valid receipt proves a run, and an adopted baseline forgives previously accepted debt.

Start from a complete example

examples/overlay-proof.spec.js (in this package, so node_modules/@gate-forge/pack-playwright/examples/overlay-proof.spec.js in your repo) is a complete overlay proof test: a surface descriptor for a small list/create/edit/archive app, the gateforge annotation, and the witnessed evidence.ui.* / visible.confirm / http.observe / persistence.verify / finalize sequence. Copy it, change the selectors, and the fixture calls stay the same.

Keep each journey isolated

  • Create distinct records and tenant context for every test. Do not reuse a per-tenant singleton across tests; shared state can hide cross-tenant leaks and make outcomes depend on test order.
  • Give test data unique identifiers, and clean it up through the same supported application path the test is checking.
  • Keep setup independent of Gateforge environment variables so discovery can register the same tests in local and CI runs.

Observe mutation results without hanging

  • Read a mutation response body only when the application returns one. Calling .json() on an intentionally empty response waits forever; assert the status and then query the resulting state through the application’s normal read path.
  • Check both the submitted value and the persisted value on the same record. A successful HTTP status or click alone does not prove the update happened.
  • Prefer a specific response or visible application condition over fixed sleeps and transient loading text.

Prefer real behavior over mocks

  • Use the real server and persistence path when the journey claims a user-facing behavior. A page.route() stub can prove client handling, but it cannot show that the server stored the right value or enforced tenant boundaries.
  • Keep mock-only tests, but do not treat them as evidence for the real application surface.
  • When multiple journeys cover the same obligation, state why each one is needed; avoid copy-pasted tests that compete for shared data.

Run the configured suite with gateforge test-gates --changed. For a selected non-authoritative slice, use gateforge test-gates --changed --scope changed --result-only; this reports selected results without creating or changing a receipt.

Install the browsers before the first witnessed run

npx playwright install chromium, from the directory that holds your Playwright config. On a Linux machine without the browser's system libraries — a container, a CI image, WSL — install those too in the same command: npx playwright install --with-deps chromium (it needs root or sudo). gateforge enforcement doctor names the case: a missing build names the install, and a build that is installed but cannot start names the loader's own line and the npx playwright install-deps chromium that fixes it.