Expo uses babel.config.js rather than the Metro transformer path to configure the component annotate plugin. The #6098 autoInjectSentryLabel option needs to work in both flows.
What to verify:
- Expo apps using the Sentry Expo plugin pick up the new option correctly
- The
sentry-label injection works at build time in an Expo managed workflow
- The
sentry-label injection works in an Expo bare workflow
- No build errors or unexpected behavior
How to test:
- Use the Expo sample app at
samples/expo/
- Enable
autoInjectSentryLabel in the Babel config
- Build and verify that static text children produce
sentry-label props at runtime
Could be combined with the Metro config enablement task or done as a separate verification pass.
Expo uses
babel.config.jsrather than the Metro transformer path to configure the component annotate plugin. The #6098autoInjectSentryLabeloption needs to work in both flows.What to verify:
sentry-labelinjection works at build time in an Expo managed workflowsentry-labelinjection works in an Expo bare workflowHow to test:
samples/expo/autoInjectSentryLabelin the Babel configsentry-labelprops at runtimeCould be combined with the Metro config enablement task or done as a separate verification pass.