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

plgg-test

v0.0.5

Published

Minimal in-house test runner for the plgg monorepo

Readme

plgg-test

UNSTABLE - Experimental study work. Part of the plgg monorepo.

The monorepo's in-house minimal test runner — the plgg-test bin every package's test and coverage scripts call. Built from scratch on plgg, its only other dependency is the project's own typescript; there is no vitest / jest in the tree.

Why this package exists

The family runs its own tests the same way it runs everything else: on plgg, with no heavy external toolchain. plgg-test discovers *.spec.ts files, runs them, and reports — including coverage with a threshold gate.

Usage

Each package wires it into its scripts:

{
  "scripts": {
    "test": "tsc --noEmit && plgg-test src",
    "test:watch": "plgg-test src --watch",
    "coverage": "tsc --noEmit && plgg-test src --coverage"
  }
}

Per-package options live in plgg-test.config.json:

{
  "coverage": {
    "threshold": 90,
    "exclude": ["/index.ts"]
  }
}

How it's organized

  • Cli — the argv → run entrypoint (--watch, --coverage).
  • Discovery / Resolve — find spec files and resolve their imports.
  • Core — the run loop.
  • Expect / Matchers — the assertion surface.
  • Mock — test doubles.
  • Coverage — instrumentation + the threshold gate.
  • Env — the runtime seam.

Requires Node >=22.6 (it runs TypeScript specs directly).

Conventions

  • as / any / ts-ignore are prohibited (see root CLAUDE.md).
  • Coverage thresholds are strict (>90%) across the family; a package's plgg-test.config.json sets its exclusions.