Frontend Architecture90-150 min
Module Federation for Micro-frontends
Define host and remote apps, expose stable modules, share dependencies carefully, and add fallbacks for remote loading failures.
Webpack 5ReactMicro-frontends
Prerequisites
- At least two frontend apps with a real sharing need.
- Webpack or compatible tooling support.
- A deployment strategy for host and remote assets.
1
Plan the implementation
Start by choosing the exact page, route, API, or deployment surface you want to improve. A narrow target makes the implementation measurable and easier to verify.
- Write down the current behavior and the user-facing problem it creates.
- Pick one measurable success signal such as bundle size, latency, error rate, security coverage, or UI responsiveness.
- Identify the files, routes, providers, and environment variables involved.
- Create a rollback note before changing production-sensitive configuration.
2
Set up the required tools
Install or configure only the tools needed for this implementation. Keep config close to the feature so future developers can find the moving parts quickly.
Implementation snippet
npm install -D @module-federation/enhancedChecklist
- Dependencies are added to the correct workspace package.
- Environment variables are documented in `.env.example` when needed.
- Local development still starts without production-only secrets.
- The change is small enough to review in one pull request.
3
Implement the core pattern
- Choose one remote module with a stable public contract.
- Expose the module from the remote build.
- Consume the remote from the host behind a lazy boundary.
- Share React as a singleton to avoid duplicate runtime problems.
- Add loading and failure fallbacks for remote outages.
Implementation snippet
new ModuleFederationPlugin({
name: "shell",
remotes: { billing: "billing@https://cdn.example.com/remoteEntry.js" },
shared: { react: { singleton: true }, "react-dom": { singleton: true } },
});4
Handle edge cases
Checklist
- Remote URLs are environment-specific.
- Shared dependency versions are compatible.
- The host can still render a useful fallback if the remote fails.
- Ownership and deployment order are documented.
5
Verify before production
- Run the app locally and test the normal success path.
- Test one failure path, one empty state, and one slow-network or retry path.
- Run the project build and any related unit or integration tests.
- Check browser console, server logs, and network responses for hidden warnings.
- Document the final behavior, commands used, and any follow-up work.