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
{{ message }}
This repository has been archived by the owner. It is now read-only.
While being able to explicitly call ReactExperienceLoader.load() at strategic points during runtime is nice, it would be a nice enhancement if react-native-lazy-index could make those calls by itself in certain scenarios. For instance, could we leverage AppRegistry.registerComponent() (and BatchedBridge.registerCallableModule()) to determine that we should call ReactExperienceLoader.load() before the app is loaded?
The text was updated successfully, but these errors were encountered:
While being able to explicitly call
ReactExperienceLoader.load()
at strategic points during runtime is nice, it would be a nice enhancement ifreact-native-lazy-index
could make those calls by itself in certain scenarios. For instance, could we leverageAppRegistry.registerComponent()
(andBatchedBridge.registerCallableModule()
) to determine that we should callReactExperienceLoader.load()
before the app is loaded?The text was updated successfully, but these errors were encountered: