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

jest-setup-mock

v0.1.5

Published

Return / resolve values while simultaneously testing expected arguments. Full TypeScript type safety.

Downloads

18

Readme

jest-setup-mock

Return / resolve values while simultaneously testing expected arguments. Full TypeScript type safety.

Rationale

Have you ever wanted to setup a Jest mock to return a value only when it received the correct arguments?

Sure, you could access mockVariable.mock.calls and assert its contents besides your original assert, but to my taste that is a pretty low-level API that furthermore makes your test code bloated and noisy.

With jest-setup-mock, you can set up the mock to return / resolve a value only when the arguments match the expected arguments that you specify:

let someFunction: (x: number, y: string) => Promise<boolean>;
let functionMock: FunctionMock<typeof someFunction>;

setupMock(someFunction)
    .expectArguments(42, 'is the answer')
    .resolveValueOnce(true);

The code above will result in the mock resolving true whenever it is called with two arguments matching [42, 'is the answer'], and throwing a descriptive error otherwise.

Furthermore, by typing your mock variable as FunctionMock<ActualFunctionType>, the types of arguments and return values in the above fluent syntax will be inferred correctly, guarding you from type mistakes.

For reference, lodash's isEqual method is used to check for expected / actual argument equality, so deep object / array equality comparison will work.

Contributing

Pull requests are accepted.