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-tests

v0.11.0

Published

Test results from a JUnit XML report: pass, fail, and skip counts, the duration, and each failure with its stack. A Comark plugin.

Readme

comark-tests

npm version npm downloads license docs

Test results from a JUnit XML report: how many tests passed, failed, and were skipped, how long they took, and each failure as a <details> with its message and stack. A Comark plugin for HTML, Vue, React, and Svelte.

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

const render = createHtmlRenderer({ plugins: [tests({ root: "." })], components });
::tests{src="reports/junit.xml" title="Unit tests"}
::

::tests
```xml
<testsuite><testcase name="counts the ducks"/></testsuite>
```
::

src reads the report relative to the document, under root, as comark-include does; pass read in a browser or an edge runtime. A report can also sit in an ```xml fence inside the block. Vitest, Jest, pytest, Go, Playwright, and most CI tools write this format. The page shows the counts with no script.

The plugin adds every problem to meta.issues, so a host can reject a document before publishing it: a missing src, a missing file, a path outside the root, a URL, malformed XML with its line, and a document that isn't a JUnit report. Each issue names the block and says how to fix it.

Renderers

| Renderer | Import | | --- | --- | | @comark/html | comark-tests/html: the styles are inlined | | @comark/vue | comark-tests/vue | | @comark/react | comark-tests/react | | @comark/svelte | comark-tests/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-tests/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.