构建简单的联邦化应用
使用模块联邦开发一个基础且可运行的微前端应用示例。
构建简单的联邦化应用 是 CoddyKit 上的免费 Micro Frontends Architecture with Module Federation 课时。 这是第 3 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Micro Frontends Architecture with Module Federation 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。
本课时的部分内容尚未翻译,以英文显示。
Our First Federated App
Welcome to building your first Micro Frontend application! In previous lessons, we learned about setting up Webpack for Module Federation and the core concepts of exposing and consuming modules.
Now, we'll bring those concepts together to build a basic, runnable example. Our goal is to create a Host Application that consumes a simple Button component from a separate Remote Application.
Remote App: The Component
First, let's create a simple React component in our Remote Application that we intend to share. This will be a basic button.
Imagine this component lives in src/components/MyButton.js within your remote project.
import React from 'react';
const MyButton = () => {
return (
<button style={{
padding: '10px 15px',
backgroundColor: '#61dafb',
color: 'white',
border: 'none',
borderRadius: '5px',
cursor: 'pointer'
}}>
Remote Button
</button>
);
};
export default MyButton;Remote App: Entry Point
This is the main entry file for our Remote Application. It will render its own content and also make the MyButton component available for exposure.
This code represents src/index.js in your Remote App.
import React from 'react';
import ReactDOM from 'react-dom';
import MyButton from './components/MyButton';
const App = () => {
return (
<div style={{ padding: '20px', border: '2px dashed #61dafb', margin: '10px' }}>
<h2>Remote App Content</h2>
<p>This part is rendered directly by the Remote App.</p>
<MyButton />
<p>The button above is our shared component.</p>
</div>
);
};
ReactDOM.render(<App />, document.getElementById('root'));Remote App: Webpack Exposing
To make MyButton available to other applications, we configure the Remote App's webpack.config.js using the ModuleFederationPlugin. We specify its name, the filename for its manifest, and the exposes property.
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
// ... other webpack configuration
plugins: [
new ModuleFederationPlugin({
name: 'remoteApp',
filename: 'remoteEntry.js',
exposes: {
'./MyButton': './src/components/MyButton',
},
shared: {
react: { singleton: true, requiredVersion: '^17.0.2' },
'react-dom': { singleton: true, requiredVersion: '^17.0.2' },
},
}),
],
};Host App: Main Structure
Now, let's look at our Host Application. Initially, it's a standard React application. We'll modify its main entry file (src/index.js) to consume the remote component.
import React from 'react';
import ReactDOM from 'react-dom';
const App = () => {
return (
<div style={{ padding: '20px', border: '2px solid #50b0ff', margin: '10px' }}>
<h2>Host Application Content</h2>
<p>This content is rendered by the Host App.</p>
{/* The remote button will appear below this text */}
</div>
);
};
ReactDOM.render(<App />, document.getElementById('root'));Host App: Webpack Consuming
The Host App's webpack.config.js needs to know about the Remote App. We use the remotes property within ModuleFederationPlugin to define the remote and its entry file URL.
Remember to adjust the http://localhost:8081 URL to where your remote application is actually served.
const { ModuleFederationPlugin } = require('webpack').container;
module.exports = {
// ... other webpack configuration
plugins: [
new ModuleFederationPlugin({
name: 'hostApp',
remotes: {
remoteApp: 'remoteApp@http://localhost:8081/remoteEntry.js', // Adjust port if needed
},
shared: {
react: { singleton: true, requiredVersion: '^17.0.2' },
'react-dom': { singleton: true, requiredVersion: '^17.0.2' },
},
}),
],
};Host App: Loading Remote Component
With the Webpack configuration in place, we can now dynamically import and render the MyButton component from our Remote App into the Host App. We use React's lazy and Suspense for this.
This code updates src/index.js in your Host App.
import React, { Suspense } from 'react';
import ReactDOM from 'react-dom';
// Dynamically import the remote component
const RemoteMyButton = React.lazy(() => import('remoteApp/MyButton'));
const App = () => {
return (
<div style={{ padding: '20px', border: '2px solid #50b0ff', margin: '10px' }}>
<h2>Host Application Content</h2>
<p>This content is rendered by the Host App.</p>
<Suspense fallback={<div>Loading Remote Button...</div>}>
<RemoteMyButton />
</Suspense>
<p>The button above is loaded from the Remote App!</p>
</div>
);
};
ReactDOM.render(<App />, document.getElementById('root'));Running Both Applications
To see your federated application in action, you need to run both the Remote and Host applications concurrently. Each application will typically have its own development server.
- Step 1: Start the Remote App
Navigate to your Remote App's directory in a terminal and runnpm start(or similar command). - Step 2: Start the Host App
Open another terminal, navigate to your Host App's directory, and runnpm start. - Step 3: Open the Host App
Access the Host App's URL in your browser (e.g.,http://localhost:8080if that's its port).
Verify the Integration
When you open the Host App in your browser, you should see:
- Content rendered directly by the Host Application.
- A 'Loading Remote Button...' fallback message briefly.
- The 'Remote Button' component, visually styled and provided entirely by the Remote Application, appearing within the Host App's layout.
This demonstrates a basic, yet powerful, example of Module Federation in action!
Federated App Check
Let's check your understanding of building a simple federated app.
Recap: Federated Success!
Congratulations! You've successfully built a basic Micro Frontend application using Module Federation.
- We defined a component in a Remote App.
- Configured the Remote App's Webpack to expose that component.
- Set up the Host App's Webpack to consume from the remote.
- Used React's
lazyandSuspenseto dynamically load the remote component.
This foundational example opens the door to creating more complex, independently deployable Micro Frontends!
常见问题解答
「构建简单的联邦化应用」课时是免费的吗?
是的 — 「构建简单的联邦化应用」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 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 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 3 节课,共 4 节。
「构建简单的联邦化应用」课时需要多长时间?
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。
我能在这节 Micro Frontends Architecture with Module Federation 课中编写并运行代码吗?
能。每节 Micro Frontends Architecture with Module Federation 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 项目创建与配置
- 共享模块与组件
- 构建简单的联邦化应用
- 在本地运行和调试联邦应用