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

@manufac/general-tests

v0.1.1

Published

A library for general tests for landing pages

Downloads

569

Readme

@manufac/general-tests

Shared Playwright regression suite for landing pages, built from the Landing Page Test Plan. It ships generic, page-agnostic checks (page load, responsive layout, forms, CTAs/links, media, orientation, touch targets, etc.) that any landing-page app in the monorepo can run against its own pages.

See CHANGELOG.md for release notes.

Consuming from an app

Add it as a normal dependency, pinned to the version you want to consume:

npm install @manufac/[email protected]
{
  "dependencies": {
    "@manufac/general-tests": "0.0.1-alpha"
  }
}

Then wire it into the app's playwright.config.ts using the project-builder helpers:

import { defineConfig } from "@playwright/test";
import { Breakpoints, createProject } from "@manufac/general-tests/config/projects.js";

export default defineConfig({
  use: {
    baseURL: "http://localhost:8080",
  },
  projects: [
    createProject({
      name: "Desktop Chrome",
      device: "Desktop Chrome",
      configuration: { projectType: "desktop", breakpoint: Breakpoints.Desktop },
    }),
    createProject({
      name: "Desktop Safari",
      device: "Desktop Safari",
      configuration: { projectType: "desktop", breakpoint: Breakpoints.Desktop },
    }),
    createProject({
      name: "Desktop Firefox",
      device: "Desktop Firefox",
      configuration: { projectType: "desktop", breakpoint: Breakpoints.Desktop },
    }),
    createProject({
      name: "Mobile Safari",
      device: "iPhone 12",
      configuration: { projectType: "mobile", breakpoint: Breakpoints.MobileM },
    }),
    createProject({
      name: "Mobile Chrome",
      device: "Pixel 5",
      configuration: { projectType: "mobile", breakpoint: Breakpoints.MobileM },
    }),
  ],
  webServer: {
    command: "npm run start",
    url: "http://localhost:8080",
    reuseExistingServer: !process.env.CI,
  },
});
  • createProject({ name, device, configuration }) builds a Playwright project for the given device.
  • configuration.projectType: "desktop" runs the shared + desktop-only specs, and requires configuration.breakpoint: Breakpoints.Desktop (1440x900).
  • configuration.projectType: "mobile" runs the shared + mobile-only specs, and requires configuration.breakpoint: Breakpoints.MobileM (390x844).

By default every spec runs against /. To point a project at a different page, override the targetPage fixture option:

createProject({
  name: "Desktop Chrome — pricing",
  device: "Desktop Chrome",
  configuration: { projectType: "desktop", breakpoint: Breakpoints.Desktop },
}),
// then, in that project's `use`:
use: { targetPage: "/pricing" }