Demystify module federation, and deployment strategy on AWS
summary
Claims that an Angular feature can be developed, built and deployed independently using webpack module federation, actual steps: create a products app (port 4201) and expose a module, point host (4200) to remote entry, use angular-architects CLI to generate webpack config and webpack magic comments for dynamic import; adds a Stencil web component (port 4202) imported at runtime. Deployment uses S3 + CloudFront + ACM + WAF with restricted S3 access and shows a profile change reflected in the main app without redeploying it.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:32Add a Profile Feature
- 7:34How To Import the Web Component into the Angular Application
- 8:08Step 2 Is To Add the Custom Element Tag in the Html Template
- 10:40Integration with Main Application
- 11:34Demo
- 14:47What Aws Has To Offer
- 18:07Recap
related talks
30mFederated Angular: Micro Frontends with Module Federation
30mFederated Angular: Micro Frontends with Module Federation
21mAngular based Micro frontends with module federation
41mThe Microfrontend Revolution
35mMicro Frontends with Module Federation, Angular and Azure Static Web Apps
29mThe Micro Frontend Revolution: Webpack 5 Module Federation and Angular
38mThe Microfrontend Revolution: Using Webpack 5 Module Federation with Angular
33mThe Microfrontend Revolution - Using Webpack 5 Module Federation with Angular
