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 🙏

© 2024 – Pkg Stats / Ryan Hefner

rich-assert

v0.0.3

Published

A rich assert library for the node test runner.

Downloads

208

Readme

A rich assert library for the node test runner

This is a drop-in replacement for the node:asert/strict library. Why? There are a few reasons:

  • The node assert library is a little bit confusing. There are both non-strict and strict variants of the assertions. The former is a legacy design mistake and the later should be preferred. The rich-assert library provides only strict assertions.
  • The node assert library is a little bit lacking. It provides a bare minimum set of assertions and forces us to write verbose tests. The rich-assert library provides some new useful assertions for writing shorter tests. One of those new assertions is like for partial comparison of objects. It only checks a subset of object properties and provides a detailed explanation of where the objects differ, at which array index or object key.

rich-assert is really a tiny wrapper around node:assert/strict. It simply re-export the strict asserts and adds a few more helpful functions.

Usage

import { test } from "node:test";
import { deepEqual, includes, like, isTrue, isNull, isEmpty } from "rich-assert";

test("test", () => {
  // Every assertion is strict.
  deepEqual({ foo: 1, bar: 2 }, { foo: 1, bar: 2 });
  includes([1], 1);
  like({ foo: 1, bar: 2 }, { foo: 1 });
  isTrue(true);
  isNull(null);
  isEmpty([]);
});