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

@aryzing/bun-mock-fetch

v0.2.2

Published

Mock fetch requests in Bun. Great for tests.

Downloads

264

Readme

@aryzing/bun-mock-fetch

Mock fetch requests in Bun. Great for tests.

bun add @aryzing/bun-mock-fetch

Basic usage:

mockFetch(requestMatcher, optionalMockResponseOptions);

Request matcher examples:

// Simple string matching
mockFetch("https://example.com");

// Using minimatch
mockFetch("https://example.com/foo/**");

// Using regex
mockFetch(/.*example.*/);

// Using a function
mockFetch((input, init) => input.url === "https://example.com");

// Using a detailed matcher object. All properties are optional.
mockFetch({
  // Must match this string, glob, or regex
  url: "https://example.com",
  // Must match this method (case-insensitive).
  method: "POST",
  // Must include these headers (case-insensitive) and match their values.
  headers: {
    "Content-Type": "application/json",
  },
});

Response options example:

mockFetch(/.*example.*/, {
  // The expected resolved value of Response.json() or Response.text().
  data: "Hello, world!",
  status: 200,
  headers: {
    "Content-Type": "text/plain",
  },
});

Test example:

afterEach(() => {
  clearFetchMocks();
});

test("first test", async () => {
  mockFetch("https://api.example.com", {
    response: {
      data: "first",
    },
  });
  expect(await makeApiRequest()).toBe("first");
});

test("second test", async () => {
  mockFetch("https://api.example.com", {
    response: {
      data: "second",
    },
  });
  expect(await makeApiRequest()).toBe("second");
});

Each call to mockFetch defines a new mock. At most one mock is used, with each mock taking precendece over previously defined mocks.

By default, requests that aren't matched against any mock definitions are forwarded to the native built-in fetch. This behavior can be modified with setIsUsingBuiltInFetchFallback().

To clear the mocks and restore original built-in fetch,

clearFetchMocks();

Helpers

  • setIsUsingBuiltInFetchFallback(value: boolean): Enable or disable using the built-in fetch for requests that haven't been matched against any mocks. Enabled by default.
  • setIsVerbose(value: boolean): Enable or disable debugging logs. Disabled by default.