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

@terra-symposium/standards-reporting

v0.6.2

Published

Reusable Playwright evidence reporting for Terra repositories

Readme

@terra-symposium/standards-reporting

Reusable responsive Playwright diagnostics and evidence reports for Terra Symposium repositories.

Install

pnpm add -D @terra-symposium/standards-reporting @playwright/test

The package requires Node.js >=18.18 and has an @playwright/test >=1.52.0 <2 peer dependency. Spreadsheet, slideshow, and image-processing dependencies are installed with the package.

Configure responsive projects

import { defineConfig } from '@playwright/test';
import { withResponsivePlaywright } from '@terra-symposium/standards-reporting/viewports';

export default withResponsivePlaywright(
	defineConfig({
		projects: [{ name: 'web', testMatch: '**/*.spec.ts' }],
	}),
	{
		singleRunProjects: ['manual-browser-capture'],
	},
);

By default, regular projects run at the six shared viewport sizes. Set PW_VIEWPORTS=mobile,lg to select a subset. Setup projects and names listed in singleRunProjects run once. The helper enables full-page screenshots and the shared reporter.

A timestamped directory under test-results/visual contains the workbook, slideshow, and copied screenshots. Each Playwright result screenshot and keyed visual capture is also stored with metadata under test-results/visual/screenshots. Repeated test/viewport captures replace their previous file, and each new slideshow is rebuilt from the whole folder, so interrupted and subset runs retain earlier evidence. The Playwright output directory defaults to test-results/playwright-output.

More capabilities

  • Import diagnosticsTest from /playwright to attach browser console, page, and request failures.
  • Import loadTest to measure named operations and capture page-navigation timings. It reads loadTesting from quality.json by default.
  • Import visualTest to call visuals.capture(key) anywhere inside a Playwright test. Matching keys are grouped across responsive projects. The reporter writes report.pptx as image-only responsive screenshot slides by default; set screenshotOnlySlideshow: false to use the diagnostic review slideshow instead.
  • Import writeScreenshotSlideshowFromDirectory from /slideshow to rebuild an image-only deck from persisted screenshot evidence without running Playwright.
  • Use /spreadsheet and /slideshow to write artifacts from normalized results without using the Playwright reporter.
  • Use /core, /viewports, and /load-testing for shared types and helpers.

The repository remains responsible for test scenarios, authentication, browser setup, CI uploads, and retention. See the reporting guide for complete options and output details.