Posts tagged: re-pack

6 posts

Series:

A host app holding one shared store that a federated remote fills with live API data

One shared store: server state across federated remotes in React Native

A remote loaded at runtime injects its endpoint into the host's store and shares one cache; get the sharing wrong and the screen hangs on a spinner that never resolves.

A host and a federated remote each installing their own version of one shared contract package from a registry

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

The host can't see what a remote exposes. A contract package, published and installed by version, gives both sides one definition and lets semver govern drift.

A React Native host app with a bottom tab bar, each tab loading a different remote at runtime

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, and each tab is a remote built, shipped and loaded on its own.

A host and a remote React Native app sharing one copy of a library through a single share scope

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; getting it wrong crashes the app on launch, not quietly.

A host React Native app loading a screen from a separate remote app at runtime

Your first federated remote in React Native

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

Why Module Federation in React Native

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