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

@testream/vitest-reporter

v1.2.7

Published

Publish Vitest test results, failures, source locations, and CI metadata to Testream and Jira.

Downloads

535

Readme

@testream/vitest-reporter: Vitest test reporting for Jira

@testream/vitest-reporter publishes fast Vitest unit and frontend test results from CI/CD to Testream as durable, Jira-visible evidence. Vitest remains the execution source, so teams do not need to recreate every automated test as a manual Jira case.

What the reporter sends to Testream and Jira

  • Passed, failed, skipped, and pending Vitest results
  • Failure messages, stack traces, source locations, and bounded snippets
  • Branch, commit, build, environment, and CI metadata, including merge-base data for pull-request comparisons
  • Suite changes and trends for Jira work and release reviews

For pull requests, the reporter uses an explicit TESTREAM_MERGE_BASE_SHA or provider-supplied merge-base metadata; otherwise it resolves git merge-base from the existing checkout without fetching. Keep history available (fetch-depth: 0 on GitHub Actions); if no merge base can be resolved, Testream falls back to execution-time comparison.

It fits Vite-based React, Vue, Angular, and other JavaScript or TypeScript projects that need automated test reporting connected to Jira.

Install and configure

npm install --save-dev @testream/vitest-reporter
// vitest.config.ts
import { defineConfig } from 'vitest/config'

export default defineConfig({
  test: {
    reporters: [
      'default',
      ['@testream/vitest-reporter', {
        apiKey: process.env.TESTREAM_API_KEY,
        uploadEnabled: true,
      }],
    ],
  },
})

The reporter enables Vitest includeTaskLocation automatically so generated CTRF reports include line metadata and shared snippet enrichment can populate source evidence for JavaScript and TypeScript tests.

Vitest evidence in CI/CD

Keep your normal Vitest command and store TESTREAM_API_KEY as a protected secret. The reporter publishes the completed run from GitHub Actions, GitLab CI/CD, Azure Pipelines, Jenkins, or another command-based CI provider. Testream then connects the results to Jira work and release context.

Frequently asked questions

Do we need to recreate automated tests as manual Jira cases?

No. Your Vitest suite remains the code-first execution source. Testream makes the results inspectable in Jira without introducing duplicate manual cases.

Does it work outside React projects?

Yes. The reporter works with Vitest itself, including Vue, Angular, Vite, and other projects that use Vitest for unit or frontend testing.

Official Testream resources