Module Federation in 2024: Beyond Webpack
summary
Module Federation detaches from webpack into a library-style runtime with a new runtime plugins middleware, remote federated types, hot refresh across remotes, and deterministic lockfile snapshots that make sharing stable at ByteDance scale (15,000 front-ends, 10,000+ frontend engineers, ~10,000 weekly deployments). An accompanying platform, Zephyr cloud, cuts deploy/iteration loops down (claimed ~200 ms in ideal cases) and enforces snapshots; a Rust bundler, RS Pack, runs ~11× faster than webpack. Reported outcomes: ~80% smaller initial JS and a ~300% increase in engineering throughput.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:29Module Federation basics
- 2:33Redesign needs and scale
- 7:31Module Federation V2 goals
- 8:54Runtime API introduction
- 11:01Runtime plugins explained
- 13:30Runtime plugin examples
- 15:58Error handling with hooks
- 17:22Dynamic remotes
- 20:50TypeScript integration
- 23:15Fast refresh across apps
- 23:57Lock files and snapshots
- 26:44DevTools and visualization
- 27:50Hot reload in production
- 28:10Zephyr deployment tool
- 32:24Zephyr benefits and metrics
- 37:16RSBuild and Rspack
- 39:01Rspack future features
- 41:15Rspack ecosystem
- 42:17Rspack ROI and savings
- 44:26RS Doctor and analysis
- 45:53Modern.js meta framework
- 47:18RS Lib and packaging
- 48:00Federation roadmap
- 50:31Future developments
- 51:15Q&A session
related talks
34mModule Federation, Bundlers, and Future State
28mModule Federation: Theory vs Practice
30mLandscape of Module Federation: 2024 and Beyond
31mModule Federation in Webpack 5
01h 02mWebpack 5 Module Federation
29mHow module federstion makes our life easier
01h 13mThe Microfrontend Revolution, module federation, Webpack 5
21mMicro Frontends Made Easy with Module Federation