Support for new architecture and bridgeless

[brentvatne]

Summary

Hi there! I'm working on supporting the roll out of the new architecture + bridgeless with Expo and Meta, and as part of that we identified which are depended on by the largest apps or the most popular native libraries on EAS Build to help prioritize which libraries to investigate. newrelic-react-native-agent came up on that list. See the list on Google Sheets (request edit access if you'd like to update the status of newrelic-react-native-agent after testing, or if you prefer to report back here on this issue it's fine too).

We want to start recommending folks try out the new architecture in the next release, react-native 0.74 / Expo SDK 51. Ideally we can get the ecosystem ready to switch over to the new architecture within the next few releases. So, we'll have from now until 0.74 release (before May) to give Meta feedback on anything that might not be working as expected with the new arch/bridgeless enabled.

Folks at Meta would really appreciate it if you could test your libraries against the latest release and report any issues that you find. This new version enables an interop layer by default, so hopefully many things will just work, but the more off of the beaten path of a simple module / view that a library goes the more likely it is to encounter possible issues ;) The following gist includes a step by step process for how to test your library and report issues: https://gist.github.com/cipolleschi/82b7a9561b8861330efabbd3eb08c6f5.

Desired Behavior

newrelic-react-native-agent supports new architecture and bridgeless mode coming in React Native 0.74.

Possible Solution

https://gist.github.com/cipolleschi/82b7a9561b8861330efabbd3eb08c6f5

Additional context

Covered in summary.

[ndesai-newrelic]

@brentvatne We've made progress on testing the newer app with the new architecture, and it's been successful so far. However, I'm encountering difficulties when attempting to apply migration to the older app. Are there any known issues related to migration that could be causing this problem?

[brentvatne]

@ndesai-newrelic - thanks for the update! can you elaborate on what you mean by an older app? in my opinion, it's not needed to support the new architecture for react-native@<0.74 - there are many improvements in new arch in react-native@0.74 and it's pragmatic to focus only on that latest version right now.