Posts tagged: module-federation

9 posts

Series:

The same federated app wired to two different state stacks

State stacks under federation: the same React Native app built twice

TanStack Query and Zustand rebuild the app Redux Toolkit and RTK Query just built; both work, and what separates them is what happens when independent teams stop coordinating.

A federated remote adding its own slice to a shared store while another remote reaches across to it

Client state across the seam: remotes that bring their own slices in React Native

A remote injects the slice it alone owns into the shared store, the contract carries the one action that crosses, and a write arrives as a prop; dispatch before the slice exists and the add vanishes in silence.

A federated app drawn as territories owned by different teams, joined by thin shared rails and one small central shell

Who owns what: boundaries, teams and coupling in a federated React Native app

Who owns a boundary, a component, a data definition? Five tests for cutting a federated React Native app along team lines, and what moves each answer.

A host app holding one shared store that two separately shipped features fill with live API data

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

A remote and an installed package inject their endpoints into one host store and share one cache; get the sharing wrong and the screen hangs on a spinner that never resolves.

Separately built apps installing versioned packages (a typed contract and a shared screen) from one registry

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

No app can see what the others ship. Two packages, published and installed by version (a typed contract and the shared detail screen), give every side one definition and let 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.