Installation
The package, the Metro config line, and what the package expects of your project.
npm install @axonpack/react-native-devtools-tabIn an Expo app, npx expo install @axonpack/react-native-devtools-tab does the same. Keep it in
dependencies, not devDependencies: Metro reads metro.config.js for release builds too.
Wrap your Metro config
This is what serves the tab to the DevTools page. Without it the package is installed and nothing appears.
const { getDefaultConfig } = require("expo/metro-config");
const {
withReactNativeDevtoolsTab,
} = require("@axonpack/react-native-devtools-tab/metro");
module.exports = withReactNativeDevtoolsTab(getDefaultConfig(__dirname));A bare React Native app is the same line with its own default config, from
@react-native/metro-config.
With no metro.config.js yet, npx expo customize metro.config.js writes Expo's default for you to
wrap. If the file already wraps its config in something else, put withReactNativeDevtoolsTab(...)
around the outermost call. An app with @axonpack/expo-devtools may already have withDevtools
there: that is the same wrap, so keep one of them.
Restart Metro afterwards. A running dev server does not pick up a config change, and a tab that never appears is almost always this.
What it expects
React 19.2 or newer is the one declared peer, and the Metro side wants Node 20 or newer. An older
React only warns at install and the install goes ahead, so check the version in package.json
first. The tab lives in React Native DevTools, so the app has to be one whose debugger is that
rather than the old Chrome remote debugger. It is built and tested on Expo SDK 57 and 58.
iOS 27 needs Expo SDK 58 or later. After moving an app to SDK 58, regenerate its iOS project with
npx expo prebuild --clean -p ios, since a stale ios/ folder crashes at launch.
@react-native/debugger-frontend and @react-native/dev-middleware are not declared as
dependencies. Both already arrive with react-native and are versioned in lockstep with it, so the
Metro helper resolves them at run time from whatever is serving your project. The copy it uses is
the copy your dev server uses.
Check it works
There is no native build: Expo Go and development builds both work. With Metro restarted, this
prints 200, which means Metro is serving the tab:
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8081/axonpack-rn-devtools-tab/host.jsAfter the quick start registers a tab, open the app,
press j in Metro, and the tab is beside Console and Sources.
Give your AI agent the skill
If you work with a coding agent, install the Axonpack skill into the project:
npx skills add axonpack/skillsThen you can ask it to "Set up @axonpack/react-native-devtools-tab in this app", and it follows this page and the quick start from the live docs. Agent skill has more ways to install it.
Next: Quick start.