MFEs , Micro-Frontends with Module Federation and Angular
summary
Demonstrates a shell that lazy loads remotes via dynamic imports using Module Federation (Webpack 5), with remotes including a React app wrapped as a custom element and multiple Angular versions packaged with Angular Elements / web components; dependencies are shared to avoid loading frameworks repeatedly, and the demo is deployed to Azure Static Web Apps. It works end to end but surfaces concrete pitfalls: router ownership clashes, the need to cache Angular platform instances, zone.js versioning, and increased bundle size, so use only for migration or mergers.
AI-written summary · about
chapters (9)
- 0:00The problem with everything
- 2:50Why mix frameworks?
- 5:53Agenda and introduction
- 7:24Module federation basics
- 12:28Web components explained
- 17:19Combining technologies
- 21:14Demo and implementation
- 25:51Pitfalls and conclusion
- 30:55Outro
related talks
21mAngular based Micro frontends with module federation
30mFederated Angular: Micro Frontends with Module Federation
22mFederated Angular - Why and How
38mThe Microfrontend Revolution: Using Webpack 5 Module Federation with Angular
27mMicro-Frontends with Module Federation: Beyond the Basics
33mThe Microfrontend Revolution - Using Webpack 5 Module Federation with Angular
30mFederated Angular: Micro Frontends with Module Federation
35mMicro Frontends with Module Federation, Angular and Azure Static Web Apps
