The Microfrontend Revolution - Using Webpack 5 Module Federation with Angular
summary
Concrete recipe for microfrontends with Module Federation and Webpack 5 using Angular: a shell loads remotely compiled remotes at runtime via a tiny remote entry script tag, shared libraries live in a shared array to avoid duplicate Angular bundles, and a custom webpack config or patched CLI is required today with official CLI support targeted around v11. Demo proves it works end to end (a shell loading a remote snake strategy) but warns about version conflicts, needing conventions or a monorepo and e2e tests to avoid runtime breakage.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:22Do you remember them?
- 2:25Monolith
- 2:50Microservices
- 4:06Microfrontends
- 4:30Autonomous Teams
- 13:18Webpack 5 Module Federation
- 15:47How to Get the Microfrontend's URL?
- 18:17Conflicting Shared Libs
- 25:13Well...
- 27:25Free eBook
- 29:44Challange
- 30:50Conclusion
related talks
38mThe Microfrontend Revolution: Using Webpack 5 Module Federation with Angular
41mThe Microfrontend Revolution
29mThe Micro Frontend Revolution: Webpack 5 Module Federation and Angular
21mAngular based Micro frontends with module federation
30mFederated Angular: Micro Frontends with Module Federation
30mFederated Angular: Micro Frontends with Module Federation
35mMicro Frontends with Module Federation, Angular and Azure Static Web Apps
27mMicro-Frontends with Module Federation: Beyond the Basics
