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

react-network-hijack

v2.0.2

Published

A small higher order component for hijacking all network requests while a component is mounted

Readme

React Network Hijack

The aim for this library is to provide an easy way to mock network requests in a browser while using React components. This was originally developed with the intent of being used as part of your stories in Storybook but there is no reason it shouldn't work with a framework which runs in the browser.

Getting Started

To use this in your stories or other browser tests you can specify a set of urls, their methods to mock and what data to return as options to the HoC and then pass your own component in.

import withNetworkMock from "react-network-hijack";

const NetworkMocked = withNetworkMock({
  GET: {
    "https://jsonplaceholder.typicode.com/todos/1": {
      body: {
        ...
      },
      status: 200,
      delay: 200
    }
  },
  POST: {
    ...
  }
})(MyComponent);

The top level object contains the methods to mock. For each of these methods you can mock individual urls with a set of options.

  • body:

    • Type: Object or String
    • Required: Yes
    • Usage: The body content to return. If an object is passed it will be stringified as JSON else the String will be passed along.
  • status:

    • Type: Number
    • Required: No (default: 200)
    • Usage: The response status to return.
  • delay:

    • Type: Number
    • Required: No (default: 50ms)
    • Usage: The amount of delay a network request should have.

If a request is not mocked an event will be emitted that you can capture in some other component and display a warning to the user. You can import this with:

import { UNMOCKED_EVENT } from "react-network-hijack";

You can also pass a whitelist to the withNetworkMock function to stop emits happening on certain URLs. The whitelist can contain either regular expressions for fuzzy matching or strings for exact matches.

import withNetworkMock from "react-network-hijack";

const whitelist = ["example.com", /www.example.com/];

const NetworkMocked = withNetworkMock(config, whitelist)(MyComponent);

License

This project is licensed under the MIT License - see the LICENSE.md file for details