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

spyn

v0.2.6

Published

Simple and safe spy tool for tests

Downloads

3

Readme

Spyn

Build Status

Safe and minimal spying tool for testing purposes.

Installation

npm install spyn --save-dev

Reference

Spy

Takes a function and returns a function that is being spied on.

const spiedFn = spy(sum)

spiedFn(1, 2) // => 3

There is also a optional configuration object which allows you to define what function call properties are stored in the calls array. By default it stores arguments and return values.

const spiedFn = spy(sum, {arguments: false, this: true})

spiedFn.call('thiz', 'a', 'b') // => 'ab'

calls(spiedFn) // => [{this: 'thiz', return: 'ab'}]

Calls

Takes a spy function and returns an array containing information of each call

const spiedFn = spy(multiply)

spiedFn(1,2)

calls(spiedFn) // => [{arguments: [1,2], return: 2}]

Original

Returns the original function of the spy.

const spiedFn = spy(divide)

spiedFn === divide // => false

original(spiedFn) === divide // => true

Usage

Spies tend to be used only in tests. They allow you to observe and automate the checking of function calls.

It is good practice to remove a spy when the test has completed. This prevents edge cases.

Tests

npm install && npm test

Example