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

@spaguettiscope/vitest-reporter

v2.2.0

Published

Vitest reporter for SpaguettiScope — writes skeleton-aware test results to native format

Readme

@spaguettiscope/vitest-reporter

Vitest reporter for SpaguettiScope. Writes test results to .spasco/results/ in the native spasco format, readable by the SpascoConnector.

Installation

pnpm install -D @spaguettiscope/vitest-reporter

Usage

Add to your vitest.config.ts:

import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    reporters: ['default', '@spaguettiscope/vitest-reporter'],
  },
})

Options

Pass options as the second element of the reporter tuple:

reporters: [
  'default',
  [
    '@spaguettiscope/vitest-reporter',
    {
      workspaceRoot: '../..', // defaults to auto-detected monorepo root
      outputDir: '.spasco/results', // defaults to {workspaceRoot}/.spasco/results
    },
  ],
]

Monorepo Setup

In a monorepo with multiple test packages, add the reporter to each package's vitest config. The reporter auto-detects the workspace root (via pnpm-workspace.yaml, turbo.json, or package.json with workspaces) and writes all results to a shared .spasco/results/ directory at the workspace root.

For example, if you have:

  • apps/admin/vitest.config.ts
  • apps/web/vitest.config.ts
  • packages/database/vitest.config.ts

Add the reporter to each one. spasco init will list all the configs that need updating.

How It Works

Each test run creates a timestamped directory under .spasco/results/ containing:

  • meta.json — run metadata (vitest version, git info, timestamps, CI detection)
  • results/{testCaseId}.json — one file per test case with name, status, duration, and inferred dimensions

The testCaseId is a deterministic hash of the source file + full test name, enabling deduplication across runs.