Federated modules and Monorepo
summary
matamus consolidates many plugin-driven web, mobile and server repos into a single monorepo using npm workspaces and webpack Module Federation. Build and dev scripts run each workspace and start multiple webpack dev servers, mapped to one dev URL; shared deps (React, React‑DOM, react‑intl) extract into common bundles. CI and deploy previews unify across services. Major friction: resolving dynamic dev URLs and updating CSPs, and a planned migration of the plugin API into Module Federation for third‑party plugins.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:27Why Monorepo
- 2:18Folder structure
- 3:27Multiproduct architecture
- 3:52Workspaces
- 4:45Model Federation
- 6:16Challenges
- 7:19Next steps
related talks
28mModule Federation: Theory vs Practice
29mHow module federstion makes our life easier
30mSuperpowered Micro Frontends with Monorepos
22mRoad to Module Federation
01h 02mWebpack 5 Module Federation
31mModule Federation in Webpack 5
55mModule Federation in 2024: Beyond Webpack
21mMicro Frontends Made Easy with Module Federation
