react-native-network-logger
react-native-network-logger is a TypeScript library that monitors HTTP traffic in React Native apps on iOS and Android, displaying requests/responses in an in-app interface without requiring native code. It supports features like request inspection, HAR export, GraphQL detection, and cURL sharing.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | alexbrazier/react-native-network-logger |
| Owner | alexbrazier |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 679 |
| Forks | 67 |
| Open issues | 20 |
| Latest release | v3.0.0 (2026-06-11) |
| Last updated | 2026-06-11 |
| Source | https://github.com/alexbrazier/react-native-network-logger |
What react-native-network-logger is
A zero-dependency JavaScript/TypeScript network interceptor for React Native that hooks into HTTP traffic, stores logs in memory (configurable limit), and renders a React Native UI component for viewing and exporting network activity. Supports filtering by host/URL/pattern and integrates with existing navigation.
Get the react-native-network-logger source
Clone the repository and explore it locally.
git clone https://github.com/alexbrazier/react-native-network-logger.gitcd react-native-network-logger# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Call startNetworkLogging() early in app initialization (entry point or conditional on flag) to ensure all network requests are captured from startup.
- Decide on filtering strategy upfront: use ignoredHosts, ignoredUrls, or ignoredPatterns to avoid logging internal or sensitive endpoints in production.
- Configure maxRequests appropriate to device memory and use case (default 500); monitor memory usage in testing to prevent app slowdown.
- Theme customization is noted as not guaranteed to follow semver, so expect potential breaking changes on minor updates if overriding theme objects.
- Test the forceEnable flag carefully if using alongside other interceptors; the library will log a warning but may cause unexpected behavior.
When to avoid it — and what to weigh
- Sensitive Data Logging at Scale — The library logs full request/response bodies and headers in memory with no built-in encryption or redaction. Production deployments handling PII or secrets require careful configuration or alternative solutions.
- High-Volume Production Monitoring — Memory overhead and the default 500-request limit make this unsuitable as a production analytics or APM tool. Use dedicated APM platforms for enterprise observability.
- Network Interception Conflicts — Only one network logging interceptor can run at a time. Projects already using Reactotron, Redux DevTools, or other interceptors will require the forceEnable flag, which may cause instability.
- Deep Performance or Protocol Analysis — The library captures basic HTTP metadata but does not provide packet-level inspection, TLS analysis, or advanced performance metrics that specialized network debugging tools offer.
License & commercial use
MIT License. Permissive OSI-approved license allowing commercial use, modification, and distribution with attribution.
MIT license permits commercial use without restriction. However, review your own obligations if bundling this in a production app: ensure any logging of user data complies with privacy law (GDPR, CCPA, etc.). No commercial support, SLAs, or liability disclaimer explicitly stated in the repo data.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
The library logs full HTTP bodies and headers in-app memory with no built-in encryption, data masking, or secure deletion. Sensitive headers (Authorization, API keys) and response bodies (user PII) are stored unencrypted and visible in the UI. Production deployments must implement filtering (ignoredUrls/ignoredPatterns) or disable the logger for sensitive endpoints. No security audit data provided.
Alternatives to consider
Wormholy
React Native network logger with in-app UI, but iOS-only and requires native setup; react-native-network-logger claims zero native dependencies for both platforms.
React Native Debugger + Charles Proxy
More powerful protocol analysis and mocking, but requires external tools and debug build; less suitable for field testing or production issue reproduction.
Reactotron
Broader DevTools alternative with networking, Redux, async storage insights, but only one interceptor can run at a time and requires separate client app.
Build on react-native-network-logger with DEV.co software developers
Our team can help you integrate react-native-network-logger, configure it safely for production, or recommend alternatives based on your architecture and security requirements.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
react-native-network-logger FAQ
Can I use this in production?
Does it log on release builds?
What if I'm already using Reactotron or another interceptor?
How do I export logs?
Custom software development services
Adopting react-native-network-logger is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source observability software in production.
Need Help Implementing or Evaluating Network Logging?
Our team can help you integrate react-native-network-logger, configure it safely for production, or recommend alternatives based on your architecture and security requirements.