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

widthwise

v0.1.1

Published

Declarative responsive layout testing — Galen-style YAML rules driven through a headless browser.

Downloads

275

Readme

widthwise

Declarative responsive layout testing — Galen-style rules in plain YAML, driven through a headless browser. No Java, no custom DSL, no pixel diffs: assert layout facts ("the sidebar is hidden on mobile", "the nav sits above the content") per viewport, and gate CI on the result.

Install

npm i -D widthwise playwright   # or puppeteer — bring your own driver
npx playwright install chromium

The browser driver is an optional peer dependency; widthwise auto-detects whichever one is installed (Playwright is preferred, --adapter overrides).

Spec files

# specs/home.yml
url: /
viewports:
  mobile: 375           # width only; height defaults to 800
  tablet: 768
  desktop: { width: 1280, height: 900 }
rules:
  - selector: .sidebar
    at: [mobile]        # named viewports, so specs survive breakpoint changes
    visible: false
  - selector: .hero
    at: [mobile, tablet]
    width: 100vw        # px, %, vw, vh — numbers mean px
  - selector: .nav
    above: .main-content   # omit `at` to assert at every viewport

Rule assertions:

| Key | Value | Meaning | | --- | --- | --- | | visible | true / false | true: at least one match is visible. false: none are (absent passes). | | width, height | 320, "320px", "50%", "100vw", "40vh" | Every matched element must be within tolerance (default ±1px). % is relative to the parent element. | | above, below, left-of, right-of | CSS selector | Edge comparison between the first match of each selector. | | inside | CSS selector | Full containment within the target's box. | | tolerance | number (px) | Slack applied to the rule's dimension/relation checks. |

Config

Optional widthwise.config.json in the project root:

{
  "baseUrl": "http://localhost:3000",
  "specs": ["specs/**/*.yml"],
  "viewports": { "mobile": 375, "tablet": 768, "desktop": 1280 },
  "reporters": ["console", "html"],
  "outDir": "widthwise-report"
}

Config viewports are defaults; a spec's own viewports block overrides them by name.

CLI

npx widthwise run                                  # uses config + default globs
npx widthwise run ./specs/*.yml -b http://localhost:3000 -r console,html

Exit codes: 0 all checks passed, 1 check failures, 2 config/spec errors — so the run gates a PR directly.

# CI usage
- run: npx widthwise run -r console,html
- uses: actions/upload-artifact@v4
  if: always()
  with:
    name: widthwise-report
    path: widthwise-report/

Programmatic API

import { runTests } from 'widthwise'

const result = await runTests({
  baseUrl: 'http://localhost:3000',
  specs: ['specs/**/*.yml'],
})
if (!result.passed) process.exit(1)

parseSpec, runSpec, evaluateRule, and the BrowserAdapter interface are exported too, so you can plug in a custom driver or embed the evaluator in another harness.