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

comark-metrics

v0.11.0

Published

Before → after numbers with the percent change, progress bars, and tables of metrics with a change column. A Comark plugin.

Readme

comark-metrics

npm version npm downloads license docs

Before → after numbers with the percent change, colored by whether lower or higher is better; progress bars; and tables of metrics with a change column. A Comark plugin for HTML, Vue, React, and Svelte.

pnpm add comark comark-metrics
import { createHtmlRenderer } from "@comark/html";
import metrics, { components } from "comark-metrics/html";

const render = createHtmlRenderer({ plugins: [metrics()], components });
The bundle went :delta{from=412 to=388 unit="kB" better="lower"} and :progress{value=0.85 label="Migrated"} of the tests moved.

::stats{better="lower"}
| Metric | Before | After |
| --- | --- | --- |
| JavaScript | 412 kB | 388 kB |
| Largest paint | 2.4 s | 1.9 s |
::

:delta shows 412 kB → 388 kB ↓ 5.8%, green when the change is better and red when it's worse. :progress is a native <progress> with its percent; max counts to something other than 1. ::stats wraps a table of names, befores, and afters and adds a Change column. It needs no script.

The plugin adds every problem to meta.issues, so a host can reject a document before publishing it: a number it can't read, a better that isn't lower or higher, a value outside its range, a ::stats without a three-column table, and a row in two units. Each issue names its block and says how to fix it.

Renderers

| Renderer | Import | | --- | --- | | @comark/html | comark-metrics/html: the styles are inlined | | @comark/vue | comark-metrics/vue | | @comark/react | comark-metrics/react | | @comark/svelte | comark-metrics/svelte |

Each entry exports the parse plugin as default and the renderer's components. The Vue, React, and Svelte components add the styles when they mount; import comark-metrics/style.css with your styles so a server-rendered page doesn't shift. The styles read the shared --comark-* tokens and sit in a comark CSS layer, so any plain rule of your own wins.