This plugin is deprecated and maintained only for compatibility reasons.
You should be using Module Federation Plugin V2 which provides enhanced features like dynamic type hinting, manifest support and Federation Runtime - learn more in the Module Federation 2.0 documentation.
This plugin is designed to configure Module Federation. It's an enhanced version of the standard Module Federation plugin that's specifically tailored for React Native environments.
This documentation describes only Re.Pack-specific configuration options.
For the complete configuration reference, please use the official bundler specific documentation:
boolean
true
Enable or disable adding React Native deep imports to shared dependencies. When enabled, the plugin will automatically add:
react-native/
for deep imports from React Native core@react-native/
for deep imports from official React Native packagesThis ensures proper sharing of deep imports and single instances of things like assetsRegistry
.
Deep imports are when you import from a specific subdirectory or file within a package rather than the package's main entry point. For example:
React Native uses deep imports extensively in its internal implementation. The reactNativeDeepImports
option ensures these imports are properly shared between federated modules.
This feature solves a common Module Federation issue where deep imports create separate instances in host and remote apps - see this Stack Overflow discussion for the original problem.