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

@map-colonies/vitest-utils

v0.2.0

Published

Utilities for Vitest testing framework

Readme

vitest-utils

Shared utilities for the Vitest testing framework used across MapColonies packages.

Install

npm install --save-dev @map-colonies/vitest-utils

Peer dependencies (vitest, jest-openapi, jest-extended) are optional — install only what you use.

API documentation

Check the autogenerated documentation here.

Usage

reporters

A pre-configured reporters array for vitest.config.ts. Includes default and html reporters, and automatically adds github-actions when running in CI.

// vitest.config.ts
import { defineConfig } from 'vitest/config';
import { reporters } from '@map-colonies/vitest-utils';

export default defineConfig({
  test: {
    reporters,
  },
});

getPathAlias

Converts compilerOptions.paths from a tsconfig.json into a Vitest resolve.alias map, keeping path aliases in sync between TypeScript and test runs.

// vitest.config.ts
import { defineConfig } from 'vitest/config';
import { getPathAlias } from '@map-colonies/vitest-utils';
import tsconfigJson from './tsconfig.json';

export default defineConfig({
  resolve: {
    alias: getPathAlias(tsconfigJson, __dirname),
  },
});

setupOpenapi

Patches Vitest's expect into the global scope so that jest-openapi matchers (e.g. toSatisfyApiSpec) work inside Vitest tests. Resets the global after setup to avoid conflicts.

Recommended: call it from a Vitest setup file so it runs once for the entire suite.

// tests/setup.ts
import { setupOpenapi } from '@map-colonies/vitest-utils';

setupOpenapi('/absolute/path/to/openapi.yaml');
// vitest.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    setupFiles: ['./tests/setup.ts'],
  },
});

Then use the matcher in your tests:

it('should satisfy the OpenAPI spec', async function () {
  const response = await supertest(app).get('/resource');
  expect(response).toSatisfyApiSpec();
});

Alternatively, call it inside a beforeAll when you need per-suite control:

beforeAll(function () {
  setupOpenapi('/absolute/path/to/openapi.yaml');
});

vitest-extended (side-effect import)

Registers all jest-extended matchers into Vitest's expect. Import it once from a setup file.

// tests/setup.ts
import '@map-colonies/vitest-utils/extended';
// vitest.config.ts
import { defineConfig } from 'vitest/config';

export default defineConfig({
  test: {
    setupFiles: ['./tests/setup.ts'],
  },
});