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

@twinedo/rn-netinspect

v0.2.15

Published

React Native NetInspect is a React Native Network Inspector for inspecting app network requests.

Readme

Preview

Why This Exists

  • See request method, URL, headers, body, status, duration, and response payload in one place.
  • Works across iOS Simulator, Android Emulator, USB-connected Android devices, and Wi-Fi-connected real devices.
  • Supports direct client capture, Android emulator proxy flow, and Android real-device adb reverse flow.
  • Keeps setup local: run one server on your machine and inspect requests from your app immediately.

Install

npm install -D @twinedo/rn-netinspect

Quick Start

This is the simplest setup for both iOS Simulator and Android Emulator.

1. Add it once at app startup

Use this in development mode:

if (__DEV__) {
  void import("@twinedo/rn-netinspect").then(({ installRNNetInspect }) => {
    installRNNetInspect({
      appName: "My RN App",
      // inspectorUrl: "http://10.0.2.2:19826", // Android emulator reaches the host machine through 10.0.2.2.
    });
  });
}

Why this setup:

  • works in stricter ESLint setups without disabling rules
  • keeps the library development-only
  • usually works for both Simulator and Emulator without extra setup
  • if Android Emulator does not connect automatically, uncomment inspectorUrl

2. Start the server

npx rn-netinspect-server

3. Open the dashboard

http://localhost:19826

4. Run your app

  • iOS: npm run ios
  • Android: npm run android

Then trigger requests in the app and watch them appear in the dashboard.

If You Need Extra Setup

Most developers should start with the quick start above first.

Android Emulator

If the Android Emulator does not connect, uncomment this line:

inspectorUrl: "http://10.0.2.2:19826", // Android emulator reaches the host machine through 10.0.2.2.

10.0.2.2 is how the Android Emulator reaches your computer.

Real Devices

Real devices may need a manual inspectorUrl.

  • iPhone over Wi-Fi: http://<your-computer-lan-ip>:19826
  • Android over Wi-Fi: http://<your-computer-lan-ip>:19826
  • Android over USB: use adb reverse tcp:19826 tcp:19826

If you want the server to auto-manage adb reverse for physical Android devices, run:

npx rn-netinspect-server --auto-connect

Android Proxy Warning

Android proxy mode changes global device network settings. This can affect the whole emulator or phone, not just your app.

Use proxy mode only when you really need it.

To clear old Android proxy settings:

adb shell settings put global http_proxy :0
adb shell settings put global https_proxy :0
adb shell settings delete global http_proxy
adb shell settings delete global https_proxy
adb shell settings delete global global_http_proxy_host
adb shell settings delete global global_http_proxy_port
adb shell settings delete global global_http_proxy_exclusion_list

If It Still Does Not Connect

If the dashboard opens but no requests appear:

  • start the server before launching or reloading the app
  • reload the app after the server is already running
  • on Android Emulator, uncomment inspectorUrl: "http://10.0.2.2:19826"
  • on real devices, make sure the device can reach your computer

Options

installRNNetInspect({
  inspectorUrl: "http://127.0.0.1:19826",
  appName: "My RN App",
  captureBodies: true,
  patchFetch: true,
  patchXHR: true,
});

Server API

The client sends events to:

POST /api/ingest

The dashboard also uses:

GET  /api/health
POST /api/register

Troubleshooting

The dashboard opens, but no requests appear

  • make sure the app points to the correct inspectorUrl
  • reload the app after the server is already running
  • on physical devices, verify the phone can open the same URL in its browser

Android app says it cannot connect to 127.0.0.1:8899

That is proxy configuration, not the direct client.

  • On an emulator, prefer the direct client URL http://10.0.2.2:19826
  • On a real device, prefer adb reverse or a LAN IP
  • Clear any old Android global proxy settings if necessary

Android phone has Wi-Fi but no internet after testing

Clear Android proxy settings:

adb shell settings put global http_proxy :0
adb shell settings put global https_proxy :0
adb shell settings delete global http_proxy
adb shell settings delete global https_proxy

Then check the phone Wi-Fi settings and ensure proxy is disabled.

Log Colors

React Native NetInspect logs use a colored [RN NetInspect] prefix.

To disable colors:

  • set NO_COLOR=1, or
  • set global.__RN_INSPECTOR_NO_COLOR__ = true before calling installRNNetInspect()