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

any-toolkit-vitest

v0.1.2

Published

A vitest-aware toolkit of utility methods for testing purposes.

Readme

any-toolkit-vitest

A vitest-aware wrapper around any-toolkit that shows the actual generated values when a test fails.

Motivation

When a test using random values fails, you typically need to know which values triggered the failure. any-toolkit-vitest hooks into vitest's onTestFailed callback to append the generated values to the error output automatically.

any-toolkit:
- anyInteger()                   | 42
- anyString()                    | xK9mP

Installation

npm install any-toolkit-vitest

Usage

Replace imports from any-toolkit with any-toolkit-vitest:

import { anyString, anyInteger, anyBoolean } from "any-toolkit-vitest";

it("should greet the user", () => {
  const name = anyString();
  const age = anyInteger();
  expect(greet(name, age)).toBe(`Hello ${name}, you are ${age} years old`);
});

If the test fails, the error message will include the values that were generated:

AssertionError: expected 'Hello ...' to be '...'

any-toolkit:
- anyString()                    | xK9mP
- anyInteger()                   | 42

API

any-toolkit-vitest re-exports all functions from any-toolkit with identical signatures:

| Function | Description | |------------------------|------------------------------------------| | anyBoolean() | Random boolean | | anyDate() | Random Date | | anyError() | Random Error | | anyFloat() | Random floating-point number | | anyPercentage() | Random number between 0 and 1 | | anyInteger() | Random integer | | anyPositiveInteger() | Random positive integer | | anyNegativeInteger() | Random negative integer | | anyOf(...items) | Random element from the provided list | | anyString() | Random string | | anyPrintableString() | Random printable string | | anyIdentifier() | Random identifier-safe string |

Peer dependencies

  • vitest ^3

License

MIT