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

@hotfyllc/debug-console-rn

v1.1.3

Published

Floating in-app debug console for React Native — captures console logs, network requests (fetch/XHR), and app-defined custom actions. Toggleable via a draggable button.

Readme

@hotfyllc/debug-console-rn

Floating in-app debug console for React Native. Captures console.* output, intercepts fetch/XHR for network inspection, and exposes custom action buttons.

Status: 1.0.0 — stable.


What you get

  • Floating draggable button — toggleable, position persisted in AsyncStorage. Shows badge with unread error count.
  • Logs tab — captures all console.log/info/warn/error calls automatically. Search, filter by level, copy to clipboard.
  • Network tab — intercepts fetch and XMLHttpRequest. Shows status, method, duration, URL. Tap a request for full headers/body in/out.
  • Actions tab — host app passes a list of DebugAction[] (label + onPress) for quick triggers (clear cache, force refresh, dump state, etc.).

Zero impact on production: just don't render <DebugConsole /> and the interceptors never install.


Install

npm install @hotfyllc/debug-console-rn

Peer dependencies

| Package | Required version | |---|---| | react | * | | react-native | >=0.70.0 | | @react-native-async-storage/async-storage | >=1.17.0 | | expo-clipboard | >=6.0.0 | | lucide-react-native | >=0.300.0 | | react-native-safe-area-context | >=4.0.0 |

If you're on Expo, all of these (except lucide-react-native) are already installed in most templates. For bare RN, install them manually.


Usage

Mount once

Render <DebugConsole /> at the root of your app (or anywhere it's always mounted while the app runs). Best place: just before the screen tree closes in your root layout.

import { DebugConsole, type DebugAction } from '@hotfyllc/debug-console-rn'
import AsyncStorage from '@react-native-async-storage/async-storage'

const debugActions: DebugAction[] = [
  {
    label: 'Clear Storage',
    onPress: async () => {
      await AsyncStorage.clear()
      console.warn('AsyncStorage cleared')
    },
    color: '#EF4444',
  },
  {
    label: 'Force CDN refresh',
    onPress: () => fetch('/api/cache-bust', { method: 'POST' }),
  },
]

export default function RootLayout() {
  return (
    <>
      {/* your app */}
      {__DEV__ && <DebugConsole actions={debugActions} />}
    </>
  )
}

Conditionally enable in production

For builds shipped to testers/QA, you can gate the console behind a flag read from env, install referrer, or any other source:

const debugEnabled =
  process.env.EXPO_PUBLIC_DEBUG_CONSOLE === 'true' ||
  installedViaDebugReferrer

return (
  <>
    {/* your app */}
    {debugEnabled && <DebugConsole actions={debugActions} />}
  </>
)

API

<DebugConsole>

interface DebugConsoleProps {
  actions?: DebugAction[]
}

When mounted:

  • Installs console.* interceptor (logs become entries in the Logs tab; original console.* still works)
  • Installs fetch and XHR interceptors (network requests appear in Network tab; originals still work)
  • Renders the floating button + tap-to-open panel

DebugAction

interface DebugAction {
  label: string
  onPress: () => void | Promise<void>
  color?: string  // hex, default = neutral gray
}

NetworkRequest (exported type)

If your app needs to inspect captured requests programmatically, import the NetworkRequest type. The internal store isn't exposed publicly — the panel reads it via useSyncExternalStore.


Behavior notes

  • Logs are kept in memory only (capped at 1000 entries). Cleared on app reload.
  • Network requests cap at 200. Older are dropped.
  • No remote logging — the console only displays locally. If you want to ship logs to a backend, use a separate analytics SDK and let this console just be the local lens.
  • Performance: interceptors add a thin wrapper around console, fetch, XHR. Negligible overhead, but if you mount <DebugConsole> in production builds, audit before shipping.

License

UNLICENSED — proprietary. Copyright (c) 2026 Hotfy LLC. All rights reserved. See LICENSE for terms.