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

@canyonjs/report

v1.0.28

Published

An [Istanbul](https://istanbul.js.org/) reporter that emits the **Canyon interactive HTML coverage report**. It extends `istanbul-lib-report`’s `ReportBase`, aggregates per-file coverage, enriches it with optional Git diff metadata, and writes a self-cont

Readme

@canyonjs/report

An Istanbul reporter that emits the Canyon interactive HTML coverage report. It extends istanbul-lib-report’s ReportBase, aggregates per-file coverage, enriches it with optional Git diff metadata, and writes a self-contained site (from @canyonjs/report-html) plus compressed report-data.js for the UI.

Features

  • Rich HTML report — Copies the bundled @canyonjs/report-html assets into the output directory and generates data/report-data.js with gzip-compressed coverage payload.
  • Diff-aware metrics — If you supply a unified diff (see below), the report can align coverage with changed lines and surface changed-line / “new lines” style summaries (via canyon-data).
  • canyon.json — When applicable, writes newlinesPercent next to index.html for downstream tooling.

Installation

npm install @canyonjs/report @canyonjs/report-html

@canyonjs/report-html is a runtime dependency: the reporter resolves its dist folder and copies it into your coverage output directory.

Usage

Register @canyonjs/report as an Istanbul reporter wherever your toolchain exposes Istanbul-compatible reporters (Vitest, nyc, Jest, c8, etc.).

Vitest

// vitest.config.ts
export default {
  test: {
    coverage: {
      provider: "istanbul",
      reporter: ["json", "@canyonjs/report"],
    },
  },
};

nyc

{
  "reporter": ["json", "@canyonjs/report"]
}

Or CLI: nyc --reporter=@canyonjs/report …

Jest / c8

Use each tool’s coverageReporters (or equivalent) and include "@canyonjs/report" alongside "json" if you still need raw JSON output.

Optional: diff input

To correlate coverage with a patch, pass unified diff text via reporter options (when supported) or place a diff.txt file in the current working directory when the reporter runs. If no inline diff is configured, the reporter tries to read ./diff.txt automatically.

The diff is parsed with parse-diff to map additions/deletions per file.

Output layout

Typical output directory (e.g. coverage/):

  • index.html — Entry for the Canyon report UI
  • data/report-data.jswindow.reportData payload (compressed)
  • canyon.json — Optional; includes newlinesPercent when computed
  • Additional assets copied from @canyonjs/report-html/dist

The console logs the resolved report path when generation finishes.

Development

pnpm install
pnpm run build
pnpm test

License

MIT — see the repository for details.