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

vitest-md-reporter

v0.2.4

Published

A TypeScript-based Markdown reporter for Vitest - ideal for CI pipelines and readable test summaries.

Readme

vitest-md-reporter

npm version License

A lightweight Vitest reporter that generates Markdown test reports. Group your tests by project and file, see passed/failed/skipped tests - all in a neat Markdown file.

Features

  • ✅ Generates Markdown reports from Vitest test runs
  • 📁 Groups tests by project and file
  • ⏱️ Shows metadata like start and end time or total duration of the test run
  • ⚡ Simple setup, fully ESM and TypeScript ready

Quick Start

1. Install

npm i -D vitest-md-reporter

Peer dependency: Vitest should already be installed in your project. If it is not, you probably do not need this package.

2. Configure Vitest

Configuration options

| Option | Required | Default | Description | | --------------- | -------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | outputFile | false | vitest-report.md | Path and filename for the generated Markdown report. Can be relative to the project root or an absolute path, but the file must remain within the project root. Attempts to save outside the project root will throw an error. | | projectLabel | false | Project | Label used as the section name for grouping test results by project. Useful when working with multiple Vitest projects | | projectsOrder | false | - | Explicit order in which projects should appear in the report. Projects not listed will be appended after the specified ones, preserving vitest order | | title | false | Vitest Test Report | Title displayed at the top of the report. Can be customized to match codebase or CI context |

Example

// {vite,vitest}.config.{js,ts}
import { defineConfig } from 'vitest/config';
import { MarkdownReporter } from 'vitest-md-reporter';

export default defineConfig({
  test: {
    reporters: [
      'default',
      new MarkdownReporter({
        outputFile: './test-results/report.md',
        projectLabel: 'Test Level',
        projectsOrder: ['Unit', 'Integration'],
        title: 'Test Summary - MyApp',
      }),
    ],
  },
});

Environment variables

| Variable | Required | Default | Description | | -------------------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | REPORT_OUTPUT_ROOT | false | - | Defines the root directory where the reporter is allowed to write output files. All generated report files must resolve inside this directory. If not set, the current working directory (process.cwd()) is used. The reporter prevents writing files outside of this directory to avoid accidental or unsafe filesystem access (e.g. path traversal). This is mainly intended for CI environments where test artifacts are written outside of the project checkout directory. |

3. Run Tests

npx vitest run

The markdown report will be generated at the configured path (outputFile).

Example Output

# Vitest Test Report

## Test Run Summary

| ℹ️ Status | 🕒 Start Time          | 🕓 End Time            | ⌛ Duration |
| --------- | ---------------------- | ---------------------- | ----------: |
| ❌ failed | 26/01/2026 at 20:03:53 | 26/01/2026 at 20:03:53 |       300ms |

|            | ✅ Passed | ❌ Failed | ⏭️ Skipped | #️⃣ Total |
| ---------- | --------: | --------: | ---------: | -------: |
| Test Files |         0 |         1 |          0 |        1 |
| Tests      |         1 |         1 |          0 |        2 |

## Test Results

### Project: Renderer

| ✅ Passed | ❌ Failed | ⏭️ Skipped | #️⃣ Total | ⌛ Duration |
| --------: | --------: | ---------: | -------: | ----------: |
|         1 |         1 |          0 |        2 |       300ms |

#### ✅ test/renderer/MarkdownRenderer.test.ts

1 passed, 1 failed, 0 skipped, 2 total, done in 300ms

- ✅ renders title heading _100ms_
- 🗂️ rendering test run summary
  - ❌ renders test run summary heading _200ms_

License

MIT © Robert Kłódka