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

@next-starters/skill-playwright-testid-catalog

v1.0.0

Published

Builds a single typed data-testid catalog per feature area instead of scattering string literals across components and specs. A shared createTestIdRegistry helper builds a nested, as-const catalog…

Readme

playwright-testid-catalog

Build a single typed data-testid catalog per feature area instead of scattering string literals across components and specs. A shared registry helper validates id uniqueness at dev-time, and a Playwright-side mirror module re-exports the exact same catalog object so app code and test code can never drift apart on an id string.

What it covers

  • A createTestIdRegistry helper that builds a nested, as const catalog object and throws on duplicate leaf string values in development.
  • A documented key/suffix vocabulary — sections (list/detail/create/edit/ dialogs) and element suffixes (-page/-button/-input/-table/-row) — so ids are readable without opening the component that renders them.
  • A mirror module for the Playwright side that re-exports the identical catalog object, plus a prefix-${id} convention (with a reverse-parse fallback) for dynamic per-row ids.

Use it

Read SKILL.md for the 7 invariants and the three-step verification loop (typecheck → dev-mode run → lint). Copy the genericized templates from references/ (utils.ts, example-catalog.ts, example-catalog.mirror.ts) as the starting shape for a new feature's catalog.

Install globally

Symlink into your global skills the same way as the other next-starters skills:

skills add [email protected]:catesandrew/next-starters.git --skill skills/playwright-testid-catalog -g

Companion

Pairs with playwright-testid-attributes, playwright-attribute-waits, and playwright-page-objects. This skill defines the registry and mirror mechanics that produce the catalog in the first place; those companion skills consume catalog ids inside components, waits, and page objects respectively, without redefining how the catalog itself is built, validated, or mirrored.