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

snapseq

v0.6.0

Published

Playwright Test fixtures for scripted screenshot sequences.

Readme

snapseq

npm

Playwright Test fixtures for scripted screenshot sequences. A sequence is a Playwright test; snapseq adds numbered screenshots per run, sequence and device, env and host selection, one project per device, a snapseq command, and defaults suited to long sequential runs. Everything else is stock Playwright: --headed, --ui, --debug, --trace on, reporters, the VS Code extension. Plugins add to the shots: a label strip above each one, one PDF per sequence, or steady viewport units for snapPage and no motion before a shot.

Quick start

In the app that owns the pages:

pnpm add -D @playwright/test snapseq @snapseq/stabilize
pnpm exec playwright install chromium   # once per machine; under Node 26 run this with Node 22
// snapseq.config.ts
import { defineConfig } from "snapseq";
import { stabilize } from "@snapseq/stabilize";

export default defineConfig({
  envs: { dev: { host: "http://localhost:3000" } },
  plugins: [stabilize()],
});

Without stabilize(), a page with a 100vh section makes snapPage refuse it (the document grew …). With it, the section keeps its height, and motion stops and the pointer leaves the content before each shot.

// snapseq/pricing.seq.ts
import { sequence } from "snapseq";

sequence(async ({ page, seq }) => {
  await page.goto("/pricing");
  await seq.snap();      // 01.png  the viewport
  await seq.snapPage();  // 02.png  the whole page
});
pnpm snapseq
screenshots/2026-10-01 at 04.07.16 PM/pricing/desktop/01.png
screenshots/2026-10-01 at 04.07.16 PM/pricing/desktop/02.png
screenshots/2026-10-01 at 04.07.16 PM/pricing/mobile/01.png
screenshots/2026-10-01 at 04.07.16 PM/pricing/mobile/02.png

Docs

| Page | Answers | | ------------------------------------------- | -------------------------------------------------------------------- | | Getting started | How do I get from an empty app to a PNG? | | Config | How do I set up envs, devices, the dev server, Playwright options? | | Sequences | How do I write a sequence that takes the right shot? | | Running | How do I run it, and what do the outputs and the terminal mean? | | Plugins | How do I add a label strip, a PDF or steady vh units, or write a plugin? | | Examples | Complete sequence files, basic to complex. | | Troubleshooting | Something looks wrong. |

Develop and release

The commands run at the workspace root: see Develop and release. docs/ is the API reference; a public change updates it and gets a changeset.