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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@exodus/mock-fetch

v2.1.1

Published

Util for mocking fetch on tests

Readme

@exodus/mock-fetch

Utils to help you mock HTTP responses in your tests

Usage

mockFetchival

If your codebase uses fetchival, you can use this function to mock your API calls.

import { mockFetchival } from '@exodus/mock-fetch'

import spiderman from '..'

describe('Spiderman', () => {
  beforeEach(async () => {
    await mockFetchival(`${__dirname}/__mocks__/mock-spiderman.json`)
  })

  it('should get uncle Ben name from API', async () => {
    const bensPhone = await spiderman.getBenPhoneFromAPI()

    expect(bensPhone).toMatchSnapshot()
  })
})

The code above will perform one API call the first time you run your tests and store the results. All subsequent tests will read the results from the store making sure your tests:

  1. Run faster.
  2. Don't depend on real time values (e.g. prices)

Notes

  • If you want your tests to react to real-time changes (e.g. you want a test to fail if an API response changes), we suggest not mocking the response.

Troubleshooting

If your tests are nor reading/writing from the mocks JSON file, ensure the @exodus/fetch version your package is using is the same one as this library's. Otherwise jest will not use the mock exposed here when your codebase tries to do an actual fetch.