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

@vitus-labs/tools-vitest

v2.3.0

Published

Shared [Vitest](https://vitest.dev) configuration for consistent testing across projects.

Readme

@vitus-labs/tools-vitest

Shared Vitest configuration for consistent testing across projects.

Installation

bun add -d @vitus-labs/tools-vitest

Peer dependency: vitest >= 4

Usage

Create a vitest.config.ts in your package:

import { createVitestConfig } from '@vitus-labs/tools-vitest'

export default createVitestConfig()

Options

Pass an options object to customize the config:

import { createVitestConfig } from '@vitus-labs/tools-vitest'

export default createVitestConfig({
  environment: 'jsdom',
  css: true,
  setupFiles: ['@testing-library/jest-dom/vitest'],
  aliases: { '~/': 'src/' },
  plugins: [myVitePlugin()],
  testTimeout: 10000,
  pool: 'forks',
  include: ['tests/**/*.test.ts'],
  exclude: ['tests/e2e/**'],
  coverageExclude: ['src/storybook/**'],
  coverageThresholds: { statements: 80, branches: 80 },
})

| Option | Type | Default | Description | | --- | --- | --- | --- | | environment | string | 'node' | Test environment ('node', 'jsdom', 'happy-dom', etc.) | | css | boolean | false | Enable CSS processing — useful for jsdom/happy-dom | | setupFiles | string[] | — | Setup files to run before each test | | aliases | Record<string, string> | — | Path aliases (e.g. { '~/': 'src/' }) | | plugins | PluginOption[] | — | Vite plugins | | testTimeout | number | 5000 | Test timeout in milliseconds | | pool | 'threads' \| 'forks' \| 'vmThreads' \| 'vmForks' | 'threads' | Worker pool | | include | string[] | — | Extra glob patterns for test discovery | | exclude | string[] | — | Extra glob patterns to exclude from tests | | coverageExclude | string[] | — | Extra glob patterns to exclude from coverage | | coverageThresholds | CoverageThresholds | 90% all | Override default thresholds |

You can also pass a string array as shorthand for coverageExclude:

export default createVitestConfig(['src/storybook/**', 'src/bin/**'])

What's included

  • Environment: Node.js (configurable)
  • Globals: enabled (describe, it, expect available without imports)
  • Mock reset: automatic between tests
  • Test files: src/**/*.test.ts, src/**/*.test.tsx
  • Coverage provider: V8
  • Coverage thresholds: 90% statements, branches, functions, and lines
  • Coverage excludes: test files, index re-exports, bin scripts

Workspace setup

For monorepos, create a vitest.workspace.ts at the root:

import { defineWorkspace } from 'vitest/config'

export default defineWorkspace([
  'packages/my-lib',
  'packages/my-app',
])

Each package references the shared config via its own vitest.config.ts.

License

MIT