Support for React-Native

[jbroma]

Clear and concise description of the problem

Re.Pack supports MF V1, for V2 supports we need adjust how containers are loaded in React-Native environment.

Suggested solution

• create separate loadScript and createScript handlers for React Native environment in @module-federation/sdk
• disable auto preload since it only supports browser env atm - related PR: chore: no auto preload when calling loadRemote #2741

Alternative

• auto preload can be disabled through loaded-first strategy and that can come from Re.Pack's own runtime plugin

Additional context

Related Re.Pack issue: callstack/repack#518
Related Re.Pack PR: callstack/repack#674

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[2heal1]

hey i don't sure why it depends on the disable autoPreload . And i support the shareStrategy option , which you can config in runtime/build configuration , maybe this can satisfy your need ?

[jbroma]

hey i don't sure why it depends on the disable autoPreload . And i support the shareStrategy option , which you can config in runtime/build configuration , maybe this can satisfy your need ?

hey, shareStrategy is definitely sufficient for this exact purpose, I've been using it in the POC ever since it was implemented and it works as expected 👍

As to why it's necessary: RN startup is complicated - we need to have eager access to react and react-native packages there, but at the same time we want to share them with other federated modules. When it's set to version-first, I think both of these dependencies were set to Promises and this caused Errors in RN env since we need to have sync startup.

[github-actions]

Stale issue message

[zackarychapple]

@jbroma can you add some more flavor to this one since we had the week working on it.