Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why Module Federation — Building an Enterprise MFE Platform (Part 1)

This series walks through an actual enterprise microfrontend platform, end to end: one Host shell, three shared platform microfrontends, a manifest-driven mechanism for mounting any number of independently-owned domain microfrontends, a full OIDC auth flow, and a CI/CD pipeline. Every code snippet in this series is real and traceable to the actual boilerplate it's built from, on GitHub . Part 1…

This article series explores the creation of an enterprise microfrontend platform, from start to finish. It details the use of Webpack 5 Module Federation as the method for combining every team's page into a single app. The Host ships with an empty list of remote apps; instead, it fetches the necessary information from a manifest that is updated when a team's page is deployed.

The use of Module Federation allows teams to deploy their pages by simply adding or updating entries in the manifest without requiring a rebuild of the Host.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Ownership, and Making This Template Your Own (Part 5)

Part 4 covered how this platform actually ships — scaffolding, CI/CD, and the two deployment shapes. This closing part is the two things every one of the last four parts has assumed: who actually owns…

  • Ownership defined: each component belongs to a single team
  • Store, Components, manifest, and identity provider owned by Platform team
  • MFEs own their respective components and domain

More from Sunday 30 August →