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

@bouaiche/vitest-discord-reporter

v1.0.1

Published

A Vitest reporter that sends test results to a Discord channel via embeds

Readme

vitest-discord-reporter

A Vitest reporter that sends test results to a Discord channel via embeds.

  • Summary, passed/failed/skipped/total, and duration
  • Optional mention when failures occur
  • Optional stack traces in failure details
  • Configurable inclusion of passed tests

Install

  • npm: npm i -D @bouaiche/vitest-discord-reporter
  • yarn: yarn add -D @bouaiche/vitest-discord-reporter
  • pnpm: pnpm add -D @bouaiche/vitest-discord-reporter

Quick start

  1. Create a Discord webhook (Server Settings → Integrations → Webhooks) and copy the URL.
  2. Expose it as an env var (recommended) and configure the reporter.

vitest.config.ts:

import { defineConfig } from 'vitest/config';
import { DiscordReporter } from '@bouaiche/vitest-discord-reporter';

export default defineConfig({
  test: {
    reporters: [
      'default',
      new DiscordReporter({
        // Prefer set VITE_DISCORD_REPORTER_WEBHOOK_URL in .env.test var to avoid committing secrets
        webhookUrl: 'https://discord.com/api/webhooks/<channel_id>/<token>',
        title: 'Test Results',
        includeStackTrace: false,
        mentionOnFailure: '',
        showPassedTests: true,
      }),
    ],
  },
});

.env (or .env.test):

VITE_DISCORD_REPORTER_WEBHOOK_URL=https://discord.com/api/webhooks/<channel_id>/<token>

package.json:

{
  "scripts": {
    "test:run": "vitest run"
  }
}

Options

  • webhookUrl (string): Discord webhook URL.
  • title (string, default: "Test Results"): Title of the summary embed.
  • includeStackTrace (boolean, default: false): Include stack traces for failed tests (truncated to fit Discord limits).
  • mentionOnFailure (string, default: ""): A string added to the summary embed when there are failures (e.g. <@1234567890> or @team).
  • showPassedTests (boolean, default: true): Include an embed listing passed tests.

What gets sent

  • Summary embed with counts for passed/failed/skipped/total and total duration.
  • Failed tests embed: up to 10 failed tests (names and errors). Long names and errors are truncated.
  • Passed tests embed: up to 20 passed tests. Long lists are truncated.

Note: Discord enforces size limits on embeds. This reporter truncates fields to avoid rejections.

Mentions: Whether a mention actually pings depends on your webhook and server mention settings.

CI example (GitHub Actions)

name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - run: npm ci
      - run: npm run build --if-present
      - run: npx vitest run
        env:
          VITE_DISCORD_REPORTER_WEBHOOK_URL: ${{ secrets.CI_DISCORD_WEBHOOK_URL }}

Local testing

  • Set VITE_DISCORD_REPORTER_WEBHOOK_URL in your environment or .env
  • Run: npm run test:run or npx vitest run

Development

  • Build: npm run build
  • Lint: npm run lint / npm run lint:fix
  • Format: npm run format / npm run format:check
  • Tests: npm run test or npm run test:run

License

MIT © Mounir Bouaiche