You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Historically our library has always been bridgeless, in the sense that we never really used the bridge to communicate from JS and instead relied on internal APIs to get a pointer to the JS runtime and expose our C++ library code through JS by constructing JS objects and functions via JSC and later JSI calls.
We did migrate the way we load our native code on Android to use a TurboModule, but the mechanism we use to initialize our native binding on iOS is still a hack and rely on the bridge. Since React Native 0.74.0 enables bridgeless by default when the new architecture is enabled, this refactor is overdue.
kraenhansen
changed the title
Support "bridgeless" -mode by exposing a TurboModule on iOS
Support "bridgeless" mode by exposing a TurboModule on iOS
May 6, 2024
Historically our library has always been bridgeless, in the sense that we never really used the bridge to communicate from JS and instead relied on internal APIs to get a pointer to the JS runtime and expose our C++ library code through JS by constructing JS objects and functions via JSC and later JSI calls.
We did migrate the way we load our native code on Android to use a TurboModule, but the mechanism we use to initialize our native binding on iOS is still a hack and rely on the bridge. Since React Native 0.74.0 enables bridgeless by default when the new architecture is enabled, this refactor is overdue.
Relevant documentation:
The text was updated successfully, but these errors were encountered: