Dependency Management in MFs
summary
A healthcare web platform composes more than 12 microfrontends with an App Shell that provides SSO and a shared component library implemented as web components with a React wrapper. Dependency strategies evaluated include Module Federation, import maps and SystemJS plus legacy UMD; practical problems include pdf.js and Zone.js refusing multiple instances and an update that forces deactivating one app. A process of target versions, parallel Angular 16/17 support and plans for linting and tooling run alongside Piral.Cloud for runtime discovery.
AI-written summary · about
chapters (14)
- 0:00Introduction and context
- 2:59Project background and goals
- 6:47Why share dependencies
- 9:19Types of dependencies
- 11:26Use cases for dependency sharing
- 13:33Common dependency management approaches
- 16:26UMD limitations and alternatives
- 17:51Module Federation explained
- 22:07Import Maps for dependency resolution
- 24:38SystemJS as a fallback
- 27:08Appell team responsibilities
- 29:20Project outcomes and challenges
- 30:45Improvements and future outlook
- 31:48Q&A session
related talks
44mApplications instead of libraries: Micro frontends implemented through module federation
31mMFEs , Micro-Frontends with Module Federation and Angular
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
25mAdvanced Micro Frontends: Multi-Version and Multi-Framework Scenarios
31mMicro frontends and the multiverse of Frameworks
48mMicrofrontend Architecture – technical implementation.
28mModule Federation: Theory vs Practice
36mMicro Frontends - Breaking Monoliths
