argent-metro-debugger

React Native Metro debugging requires a running Metro server and a connected app to establish a CDP target. You use the returned logical device id to target specific simulator or physical devices for debugging, network, and profiler calls.

React Native component inspection retrieves the full React component tree from the connected app. You can inspect a visible element to map it back to the component hierarchy and source file locations when source maps are available.

You can evaluate JavaScript in the React Native runtime through the Metro CDP connection to validate assumptions about state, props, or runtime behavior. This allows you to test expressions on-device or in the simulator without redeploying the app.

React Native log analysis through Metro CDP summarizes log clusters and guides you to grep or read relevant log entries from the underlying flat log file. This helps diagnose console output, UI rendering issues, and runtime logic errors.

React Native Metro debugging supports iOS simulators and Android devices or emulators. You must target the correct device_id from the connected app when making debugger, network, and profiler calls to ensure diagnostics reach the right target.

To run React Native diagnostics via Metro CDP, you need a running Metro dev server and your React Native app connected to Metro. Call the debugger-status tool after setup to establish the debugging session and retrieve the device id.