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

reporter-minimal

v0.0.2

Published

A minimal test reporter for node:test

Readme

node-reporter-minimal

Screenshot

About

A simple test reporter for node:test (Node.js's test runner). The reporter will prioritize logging errors and hides everything else while staying relevant.

You get

  • Per root test execution time
  • Nested test errors and nesting path
  • A decently colorised output

[!TIP]

reporter-minimal is a lot more effective for running in CI systems where the passing tests don't mean much and the failed ones are what need to be re-validated. This saves you from missed log data when there's a limit to the size of the log on certain CI systems

Installation

npm add -D reporter-minimal

Usage

node --test-reporter=reporter-minimal --test-reporter-destination=stdout

Why should we use this ?

  1. You have a large project where the reduced output could help with the size of the logs in a CI environment and you don't use Github (Check out nearform/node-test-github-reporter)
  2. You need a reporter that only logs errors and nothing else.

License

MIT