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

usnap

v0.1.0

Published

Micro alternative to assert.snapshot

Downloads

18

Readme

μsnap

A micro snapshot testing tool that works very well with the Node >=18 built-in node:test harness.

Usage

npm install --save-dev usnap utap

Note: utap is of course optional: it is a test TAP output formatter.

my.test.js:

import snapshot from 'usnap';

snapshot.setup(import.meta.url);

test('test name', async t => {
  const obj = { foo: { bar: 42 } };

  await snapshot(obj, t.name);
});

Run the test:

node my.test.js | npx utap

The snapshot will be created in the snapshots/ directory next to my.test.js.

To update the snapshot:

node my.test.js -u | npx utap

But why?

  • The currently built-in assert.snapshot is horrible since it is using util.inspect for serialization, with default options, which means limited depth and basically produces garbage.
  • μsnap relies on YAML. One could not possibly choose a better format for snapshots, since it is
    • perfectly human-readable, git-friendly, and ubiquitously supported;
    • homomorphic in the sense
    assert.equal(YAML.stringify(array), array.map(a => YAML.stringify([a])).join(''))
    which makes it trivial to append to an existing snapshot file.
  • Unlike most snapshot testing tools, μsnap creates a separate snapshot file for each individual test point. This avoids many issues when running tests in parallel and updating snapshots in --test-only mode.
  • 60 lines of code with YAML as the only dependency.