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

@describe-me/vitest

v0.4.0

Published

Vitest integration for describe-me: plugin, setup file and reporter

Readme

@describe-me/vitest

The Vitest integration for describe-me: a plugin, a setup file that makes every interaction record a frame, and the Node reporter that writes .describe-me/.

Install

pnpm add -D @describe-me/vitest @describe-me/react describe-me

Usage

One line in the Vitest config registers the setup file and the reporter, and redirects the test library's render import to the recording adapter. The plugin detects where the tests run:

  • Browser mode (test.browser.enabled): redirects vitest-browser-react, records a frame after every Locator action and keyboard-level userEvent.
  • DOM environments such as jsdom (anything else): redirects @testing-library/react, records a frame after every @testing-library/user-event call, turns on test.css so imported stylesheets reach the snapshots, and sets RTL_SKIP_AUTO_CLEANUP so the component is unmounted only after the closing frame.
import { describeMe } from '@describe-me/vitest/plugin'

// browser mode
export default defineConfig({
  plugins: [react(), describeMe()],
  test: {
    browser: { enabled: true, provider: playwright(), instances: [{ browser: 'chromium' }] },
  },
})

// jsdom
export default defineConfig({
  plugins: [react(), describeMe()],
  test: { environment: 'jsdom' },
})

Pass describeMe({ environment: 'browser' | 'dom' }) to override the detection.

The pieces can also be wired by hand, in which case tests import render from the adapter themselves (@describe-me/react in browser mode, @describe-me/react/testing-library in jsdom):

import DescribeMeReporter from '@describe-me/vitest/reporter'

export default defineConfig({
  test: {
    // browser mode: '@describe-me/vitest/setup'
    setupFiles: ['@describe-me/vitest/setup-dom'],
    reporters: ['default', new DescribeMeReporter()],
    // jsdom only: keep imported CSS and leave unmounting to describe-me
    css: true,
    env: { RTL_SKIP_AUTO_CLEANUP: 'true' },
  },
})

typescript is an optional peer: without it the docs are still generated, only the props tables are left out. @testing-library/user-event is an optional peer too, needed only in DOM environments.

See the root README for the full picture.