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

hungry-fetch

v0.9.2

Published

A hungry fetch mock.

Downloads

112

Readme

Hungry Fetch

Tests npm

Nomnomnom … lets you test your fetch calls.

What it doesn’t do

Hungry Fetch does not polyfill the Fetch API. Furthermore it requires Response to be available, so you might actually need to polyfill the Fetch API before using Hungry Fetch.

How does it work?

Hungry Fetch monkey patches window.fetch and saves all calls to fetch(…) with it’s parameters.

Installation

npm install --save-dev hungry-fetch

Examples

Swallow and resolve requests

By default hungryFetch resolves any request with an undefined response.

import hungryFetch from 'hungry-fetch';

test('test network call', () => {
  return fetch('/path/to/nowhere', {
    body: JSON.stringify({
      data: 'I am a body'
    })
  }).then(() => {
    const call = hungryFetch.singleCall();
    expect(call.url).toBe('/path/to/nowhere');
    expect(call.json().data).toBe('I am a body');
  });
});

Mock response

You can mock responses for explicit URLs. You may also use * as url matcher to match any URL. Explicit URLs are stronger weighted than the wildcard matcher, so you can specify a default response and add different responses for explicit URLs.

import hungryFetch from 'hungry-fetch';

test('test response', () => {
  hungryFetch.mockResponse('/path/to/nowhere', {
    data: 'some data'
  });

  return fetch('/path/to/nowhere').then(response => {
    return response.json();
  }).then(body => {
    expect(body.data).toBe('some data');
  });
});

Advanced response

You can set some parameters of the response with the third argument of mockResponse(…).

import hungryFetch from 'hungry-fetch';

test('advanced response', () => {
  hungryFetch.mockResponse('/somewhere', {}, {
    // set custom status code
    status: 204,

    // set custom content type
    contentType: 'plain/text',

    // set additional headers
    headers: {
      'X-MyHeader': 'hello',
    },
  });

  return fetch('/somewhere').then(res => {
    expect(res.status).toBe(204);
    expect(res.headers.get('Content-Type')).toBe('plain/text');
    expect(res.headers.get('X-MyHeader')).toBe('hello');
  });
});