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

@starci/playwright-preset

v1.0.0

Published

The StarCi Playwright config: one Chromium project per ui-screen viewport (desktop 1440x900, tablet 768x1024, mobile 390x844), one worker, list reporter.

Readme

@starci/playwright-preset

The Playwright config of a front-end repository. Install it from the npm registry at the exact version in knowledge/hfs/canon-pins.yaml (see packages/README.md).

// playwright.config.ts
import { starciPlaywrightConfig } from "@starci/playwright-preset"

export default starciPlaywrightConfig({
    baseURL: "http://127.0.0.1:5067",
    webServer: { command: "npm run start", url: "http://127.0.0.1:5067", reuseExistingServer: true },
})
  • Three Chromium projects, one per ui-screen viewport: desktop 1440x900, tablet 768x1024, mobile 390x844. Desktop and mobile are the layout-tree DEFAULT_BREAKPOINTS (scripts/work/layout-tree.mjs) that interface.draw shots use; the spec fails if they drift. A flow runs once per viewport, so a screen is asserted at every size it was drawn at.
  • One worker, no parallelism, no retries, forbidOnly in CI, list reporter, light scheme, reduced motion, trace kept on failure.
  • Specs are **/*.e2e-spec.ts under ./e2e. e2e is run by hand: no husky, no coverage, and the CI job is workflow_dispatch only.
  • baseURL defaults to E2E_BASE_URL, else http://127.0.0.1:3000. The suite runs against a local stack or a double generated from the contract, never a step that skips for a missing environment.