Description
The Expo config plugin documentation at https://docs.sentry.io/platforms/react-native/manual-setup/expo/ only shows @sentry/react-native/expo as the plugin path in app.json/app.config.ts:
{
"plugins": [
["@sentry/react-native/expo", { ... }]
]
}
However, the package ships app.plugin.js at its root which proxies to ./expo:
// node_modules/@sentry/react-native/app.plugin.js
module.exports = require('./expo');
This means the bare package name also works as a config plugin:
{
"plugins": [
["@sentry/react-native", { ... }]
]
}
Why this matters
When running npx expo install @sentry/react-native, Expo CLI automatically adds @sentry/react-native (bare path) to the plugins array. This conflicts with the docs which only show the /expo subpath, causing confusion about which is correct.
Suggestion
Document that both paths are valid, or align with what Expo CLI generates by recommending the bare @sentry/react-native path in the docs.