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

snaptdout

v2.1.0

Published

simple stdout snaptshot testing

Downloads

28

Readme

snaptdout

snaptdout is a lightweight, simple stdout snapshot testing with great diffs

install

npm i -D snaptdout

how does it work ?

snaptdout saves a copy of stdout to a .json file equivalent to the test file name, which should be committed to git.

usage

snaptdout is a drop-in snapshot testing tool, you can use it in any testing framework by simply calling it with the expected stdout:

describe('snapshot testing', () => {
    it('should snapshot stdout', async () => {
        const stdout = ` 
        this is a 
        complicated cli
        str ing
        `
        await snap(stdout, 'snapshot name');
    });
});

all consequential tests from this file will be compared to the snapshot.

while snapshot name is optional, it is highly recommended.
if you do not provide a snapshot name, snaptdout will save the line and column of the running test as keys in the .json file.

config

you can provide config through your package.json, like so:

...
"snaptdout": {
    "snapshotsDir": "relative/to/root/project/directory"
}
...

you can also provide the config as a third paremeter. snapshot specific config overrides any global config.

const stdout = '\x1b[32;7mHEY THERE\x1[0m';
await snap(stdout, 'hey', {ignoreAnsi: true});

snapshotsDir

snapshots directory.
under this directory all snapshots files will be saved.

default: test file location.

snapshotsPrefix

snapshots file prefix.

default: ''.

ignoreAnsi

ignore ansi formatting characters (\x1b[32m || [32m).
if set to true - snaptdout will save the raw string without formatting and use that for future comparisons.

default: false.

formattedOutput

show formatted output after error message.

default: true.

features

lightweight

snaptdout has no dependencies, and a minimal footprint.

0 setup

you can simply require / import snaptdout and use it out of the box.

simple.

snaptdout uses simple .json files to store the string we refer to as a snapshot.
no binaries. nothing fancy.

great diffs

when output based tests break, you need to know exactly where.

examples

yargs cli test example

const {exec} = require('child_process');
const execute = require('util').promisify(exec);
const snap = require('snaptdout');

describe(('help test') => {
    it('should show the correct help text', async () => {
        const {stdout} = await execute('node index.js --help');
        await snap(stdout, 'help');
    });
});

ignore ansi characters for specific test