Back to blog

Posts tagged: re-pack

5 posts

A host and a federated remote each installing their own version of one shared contract package from a registry
29 June 2026 · 15 min read RN Module Federation

The contract package: a versioned seam between federated remotes in React Native

A remote is built and shipped on its own, so the host can't see what it exposes. A shared contract package, published to a registry and installed by version, gives both sides one definition. Then semver governs what happens when they drift.
A React Native host app with a bottom tab bar, each tab loading a different remote at runtime
22 June 2026 · 7 min read RN Module Federation

The host shell: federated remotes as tabs in React Native

Turn the host from a single screen into a real app shell. It owns the tab bar and navigation; each tab is a separate remote, built and shipped on its own, loaded at runtime.
A host and a remote React Native app sharing one copy of a library through a single share scope
15 June 2026 · 9 min read RN Module Federation

The shared-singleton contract in React Native Module Federation

Share react, react-native, and a native library across a host and its remote the right way, and see why getting it wrong crashes the app on launch instead of failing quietly.
A host React Native app loading a screen from a separate remote app at runtime
8 June 2026 · 10 min read RN Module Federation

Your first federated remote in React Native

Build it from zero: two React Native apps, one loading the other's screen at runtime over Module Federation 2.0 with Re.Pack. Every step, copy-paste, ending in a running app.
Module Federation in React Native
1 June 2026 · 8 min read RN Module Federation

Why Module Federation in React Native

What runtime micro-apps buy a React Native app, what they cost, and when the trade is worth making. The intro to a series that builds a federated setup from scratch.