Webpack 5 Module Federation
summary
Module Federation for Webpack 5 lets apps import modules from other builds at runtime so separately deployed SPAs share code without rebuilding; it uses a small container runtime and a generated remote entry.js to fetch chunks, negotiates versions via share scopes and semantic version rules, supports an omnidirectional host model, and demo shows five independent builds composing into one shell with a 9.2 KB extra download and working cross-version React via an adapter. Built-in fallback, dashboard version control and IPFS-friendly distribution are described as workable next steps.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:40Intro
- 2:48Context on Module Federation
- 6:54Existing Options
- 10:07The Next Step in JavaScript Architecture
- 10:35Terminology
- 16:30What is Module Federation
- 19:23An Example
- 26:56Container Plugin Deep Dive
- 32:36Example at Scale
- 33:34Demo Video
- 35:05Applied Architecture
- 35:38Another Example
- 38:29Decentralized Routing
- 40:41Non Webpack Compatibility
- 41:12Federation Dashboard
- 42:25Find Out More
- 43:17Q&A
related talks
31mModule Federation in Webpack 5
29mHow module federstion makes our life easier
51mBuilding a Micro-Frontend Application with Webpack 5 Module Federation
28mModule Federation: Theory vs Practice
01h 13mThe Microfrontend Revolution, module federation, Webpack 5
55mModule Federation in 2024: Beyond Webpack
29mThe Micro Frontend Revolution: Webpack 5 Module Federation and Angular
30mFederated Angular: Micro Frontends with Module Federation
