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

@litehouse/metrics

v0.1.5

Published

Test/coverage/LOC metrics with a fully themeable report dashboard.

Readme

litehouse-metrics

Cross-platform CLI to generate test + coverage + cloc metrics and a static HTML report.

Install (local)

npm i -D @gfdlr/litehouse-metrics

Quick start

# Run tests + generate metrics JSON
npx @litehouse/metrics run

# Build report + serve at http://localhost:8000
npx @litehouse/metrics serve --open

# Dev mode: run metrics, serve, watch JSON, open browser once
npx @litehouse/metrics dev

Commands

  • run – runs tests with coverage, optional cloc, writes metrics/metrics.json and metrics/history/metrics-<timestamp>.json.
  • report – rebuilds metrics/report/index.html from JSON.
  • serve – rebuilds report and serves metrics/report/ on port 8000.
  • watch – watches JSON and rebuilds report on change.
  • devrun + serve + watch + open browser once.
  • presets – list available presets.

Options

Common options:

  • --cwd <path> – project root (default: current working directory)
  • --config <path> – path to litehouse-metrics.config.json
  • --preset <name> – apply a preset (next, node)
  • --set <key=value> – override config values (repeatable)
  • --port <number> – server port (default: 8000)
  • --host <host> – server host (default: localhost)
  • --open / --no-open – open browser
  • --no-cloc – skip cloc
  • --no-categories – skip per-category coverage runs
  • --test-command <cmd> – custom test command to run instead of Vitest
  • --test-summary <path> – optional path to test summary JSON
  • --coverage-summary <path> – path to coverage summary JSON

Config file (optional)

Create litehouse-metrics.config.json in your project root to override defaults. See the template in this repo: litehouse-metrics.config.json.

Presets:

  • next (default)
  • node

Themes:

  • minimal (default)
  • neon-hud Themes can also change the report layout. Themes live in src/report-themes/ and are loaded by filename. Layouts live in src/report-layouts/ and are selected by the theme layout field.

Add a new theme by copying an existing JSON file in src/report-themes/ and setting layout to minimal or hud.

Example theme override:

{
  "report": {
    "theme": "neon-hud"
  }
}

Example override without editing JSON:

npx @gfdlr/litehouse-metrics report --set report.charts.coverage.metric=branches

Notes

  • cloc is optional. If it’s not installed, LOC metrics are omitted.
  • vitest must be available in the target project (local node_modules/.bin preferred).
  • If you use --test-command, ensure it produces coverage/coverage-summary.json. Optionally write a test summary JSON and point to it with --test-summary.
  • When --test-command is used, per-category coverage runs are skipped by default.