
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.
Tag archive

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.

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.

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.

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.

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.
Error: Invalid src prop (https://cdn.myapp.com/banner.jpg) on `next/image`, hostname...
Your Next.js Module Federation setup builds fine. Remotes appear to load. Components render...
Micro Frontends: The Ultimate Guide — React, Vite, Next.js, React Native & Module...
Frontend applications are growing in complexity. As teams scale and codebases expand, a single...

From Token Drift to a Single Source of Truth 1) Context & Problem When you scale a Module...
The Ultimate Guide: Bootstrapping Microfrontends with Rsbuild, React, and Module Federation...

We've all been there: you set up Module Federation, split your app into micro-frontends, and suddenly...