Federated Angular: Micro Frontends with Module Federation
summary
Module Federation with Webpack 5 loads separately compiled Angular apps at runtime so a shell pulls a remote entry and exposes modules; demo shows a shell + MF1 on localhost:5000/3000 with the remote module fetched as ~11.6 KB and Angular shared so it does not ship twice. Configuration uses a module-federation plugin, optional Angular Architects module federation helper for the CLI, and an experimental CLI opt-in for Webpack 5; dynamic federation and version-conflict options are shown.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:27Leonardos Helicopter
- 1:16Microfrontence
- 2:36Outline
- 3:01Who am I
- 3:29What is Module Federation
- 3:54Dynamic Import
- 5:07Module Federation
- 7:56Remote Entry Point
- 8:44Sharing
- 9:17Making the CLI use Module Federation
- 12:01Debugging with Module Federation
- 12:15Demo
- 16:51Source Code
- 17:18Configuration
- 25:37Demonstration
- 26:50Testing
- 28:58Free ebook
- 29:28Summary
- 30:07Contact Manfred
related talks
29mThe Micro Frontend Revolution: Webpack 5 Module Federation and Angular
21mAngular based Micro frontends with module federation
38mThe Microfrontend Revolution: Using Webpack 5 Module Federation with Angular
22mFederated Angular - Why and How
41mThe Microfrontend Revolution
33mThe Microfrontend Revolution - Using Webpack 5 Module Federation with Angular
27mMicro-Frontends with Module Federation: Beyond the Basics
35mMicro Frontends with Module Federation, Angular and Azure Static Web Apps
