createDevtoolsClient

import { createDevtoolsClient } from '@axonpack/expo-devtools';

export const devtools = createDevtoolsClient(config?);

Call it once, at module scope, and export the instance. Everything else hangs off it. Every option is optional, and the defaults are what most apps want.

Top level

webviewSources uses a const type parameter, so the literal names flow into the WebView helpers' parameter types: passing an undeclared name is a compile error, and at runtime a message from an undeclared source is dropped.

Network

The switches name the kind of traffic, not the mechanism that carried it. A request is a request whether it went out through fetch, through XMLHttpRequest, from a JSI client or from inside a page.

With sse off, the app's own stream is still recognised as one — its endless body has to be, or it would be read as a response — so the row remains and only the events are dropped. A page's stream has no request underneath it that anything here can see, so that one disappears entirely.

Console

Performance

Storage

See Storage adapters for how to build one.

Crash

Crash capture is the only part of this package that can run without init().

Before init(), an app relying on enableWhileDevtoolsDisabled alone installs nativeExceptions only, whatever the other two say: the JS tiers report errors the app survived, which is a developer's concern, and the sheet there is in front of a user. A fatal JS error still arrives, because React Native turns it into a native exception on the way to killing the process.

disableDefaultLogBox uninstalls LogBox rather than muting it, which takes the yellow warning toasts with it — LogBox is one component and the two cannot be separated. Warnings are still captured by the Console tab. It only does anything in development; LogBox is already an empty stub in a release build.

Client methods

User timing

devtools.mark('checkout');
await buildCart();
devtools.measure('checkout'); // measures from the mark of the same name

measure follows the W3C User Timing signatures, and calls are forwarded to the real performance.mark and performance.measure too, so the entries exist on the platform timeline as well. Nothing is observed from that timeline, which is why React's own internal measures never appear in the list.