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

@theholocron/jest-config

v4.1.0

Published

A Jest preset for testing code within the Galaxy.

Readme

Jest Preset

A Jest preset for testing code within the Galaxy.

Installation

npm install --save-dev @theholocron/jest-preset

Usage

In your project package.json add the following:

{
	"jest": {
		"displayName": "<project>",
		"preset": "@theholocron/jest-config"
	}
}

How We Test

Currently we use Jest for our testing framework. There isn't much to our configuration that differs from what Jest provides out of the box with the following exceptions:

  • Coverage: we enforce coverage collection and require that all work be covered at least 80% at this time, with negligible reduction (< 1%) of coverage per PR
  • Directory Naming: while we do support the same regex that Jest provides, our convention is to co-locate all test files as close to the source as possible with the suffix of .test added.