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 🙏

© 2025 – Pkg Stats / Ryan Hefner

luispablo-test-helpers

v1.4.1

Published

Some small and simple helpers for my unit tests

Readme

test-helpers

Some small and simple helpers for my unit tests

Content

DispatchMock

How to use

import { DispatchMock } from "luispablo-test-helpers";

...

const expectedActions = [{ type: "set item", payload: "some text" }, { type: "remove item" }];
const dispatch = DispatchMock(assert, expectedActions, true);

The first param (assert) is the tape assert object. The expected actions is and array of objects, each one containing a type and a payload. As you can see the payload is optional, but the type is required. For each action called it will check that a part of the action type has the type you provided in them and, if it matches and it has a payload, checks for a === of the action payload to the expected one.

The last param set wether to log via assert.comment the triggered action or not (if it's not provided it wont log)

FetcherMock

This component is a function that works as the new fetch API function, so when your code calls it as fetcher("url") it will return a promise that resolves or reject, based on the params you provide. So, first do

import { FetcherMock } from "luispablo-test-helpers";

And then, for an HTTP 200 response with a JSON body do

const fetcher = FetcherMock({ json: { name: "Tom" } });

So, fetch("anyURL") will resolve a response with a json() function that returns { name: "Tom" }. Or, the same but with text:

const fetcher = FetcherMock({ text: { "some dummy text" } });

This will resolve a response with a text() function that returns "some dummy text".

To resolve the promise, but with different HTTP code do

const fetcher = FetcherMock({ status: 404 });

This will still resolve when you invoke it, but giving you a response object with the status property in 404.

And finally, if you want it to reject (as in a network error) do

const fetcher = FetcherMock({ error: { code: 1, message: "Network error" } });

This will fall into the catch part of the promise, with an error param with code 1 and the message shown above.

Data stored by the FetcherMock

The mocked fetcher receives a URL and, optionally, some options (like method, headers, body, and so on). It saves the URL and the options in its invokedURL and providedOptions properties.

var fetcher = FetcherMock();

// your code here, and later you can do

console.log(fetcher.invokedURL); // This should give you the actual URL invoked
console.log(fetcher.providedOptions); // Here you get the second param given to fetch

If you want to see al available options check https://github.com/github/fetch

LocalStorageMock

This is a HTML 5 window local storage mock, to use in your tests. Just do:

import { LocalStorageMock } from "luispablo-test-helpers";

...

// and then
const storage = LocalStorageMock();
// and you're done!