模块联邦入门
理解模块联邦的核心理念，以及它如何让应用动态暴露和使用模块。
模块联邦入门 是 CoddyKit 上的免费 Micro Frontends Architecture with Module Federation 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Micro Frontends Architecture with Module Federation 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
What is Module Federation?
Welcome! In this lesson, we'll dive into Module Federation, a powerful feature of Webpack that's key to building modern Micro Frontends.
It allows different JavaScript applications to share and consume code from each other dynamically at runtime.
The Monolith Problem
Traditionally, large web applications are built as a single, giant codebase – a monolith. This can lead to:
- Slow development cycles
- Difficulty scaling teams
- Tight coupling between parts
Module Federation helps overcome these challenges by enabling a more modular approach.
Dynamic Code Sharing
The core idea of Module Federation is dynamic code sharing. Instead of bundling all code together at build time, it lets applications load pieces of code from other applications at runtime.
Think of it like an app saying, "I need this component, and I know where to get it from another running app!"
Key Players: Host & Remote
In a Module Federation setup, we have two main types of applications:
- Remote Application: This app exposes its code (components, functions) for others to use.
- Host Application: This app consumes or uses the code exposed by a remote application.
An app can be both a host and a remote simultaneously!
Exposing Modules: Remote Apps
A remote application uses Webpack's ModuleFederationPlugin to declare which parts of its code it wants to expose. These exposed modules become available for other applications to consume.
Here's a simplified example of how a remote app might expose a Button component:
/* webpack.config.js (Remote App) */
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
// ... other webpack config
plugins: [
new ModuleFederationPlugin({
name: 'remoteApp',
filename: 'remoteEntry.js',
exposes: {
'./Button': './src/Button.js',
},
}),
],
};Consuming Modules: Host Apps
A host application also uses the ModuleFederationPlugin to specify which remote applications it wants to consume modules from. It provides a URL where the remote's entry file (e.g., remoteEntry.js) can be found.
Here's how a host app might declare its intent to use remoteApp:
/* webpack.config.js (Host App) */
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
// ... other webpack config
plugins: [
new ModuleFederationPlugin({
name: 'hostApp',
remotes: {
remoteApp: 'remoteApp@http://localhost:8081/remoteEntry.js',
},
}),
],
};How it Works: The Entry File
When a host application starts, it doesn't immediately load all remote code. Instead, it first loads a tiny file from the remote called remoteEntry.js.
This file acts as a manifest, telling the host what modules the remote exposes and how to dynamically load them if needed. Code is fetched only when requested!
The Power of Independent Deployments
One of the biggest advantages of Module Federation is enabling independent deployments.
Teams can develop, test, and deploy their micro frontends separately without coordinating a large, synchronized release for the entire application. This speeds up delivery and reduces risk.
Sharing More Than UI
Module Federation isn't just for sharing UI components. You can expose and consume various types of code:
- Utility functions
- Data services
- React hooks or similar logic
- Shared styles or themes
This allows for robust code reuse across your federated applications.
Test Your Knowledge
Module Federation introduces new ways for applications to interact. Which of the following statements correctly describe the core concepts?
Module Federation Recap
Great job! You've grasped the fundamental idea of Module Federation.
- It's a Webpack feature for dynamic code sharing.
- Apps can be hosts (consuming) or remotes (exposing).
- It enables independent deployments and efficient code reuse.
Next, we'll look deeper into how host and remote applications are set up!
常见问题解答
「模块联邦入门」课时是免费的吗？
是的 — 「模块联邦入门」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Micro Frontends Architecture with Module Federation 课程的其余内容，请升级到 CoddyKit PRO。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。
「模块联邦入门」这节课中我会学到什么？
理解模块联邦的核心理念，以及它如何让应用动态暴露和使用模块。 你通过在浏览器中直接运行的动手代码来练习 Micro Frontends Architecture with Module Federation，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Micro Frontends Architecture with Module Federation 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Micro Frontends Architecture with Module Federation 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「模块联邦入门」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Micro Frontends Architecture with Module Federation 课中编写并运行代码吗？
能。每节 Micro Frontends Architecture with Module Federation 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。