How surjitsahoo/mf-cra works
Project type and purpose
• This is an open-source, Lerna-managed monorepo containing:
• A CLI/library package (“mf-cra”) that injects Webpack Module Federation support into Create-React-App projects without ejecting
• Several example CRA micro-frontend apps (shell + remotes) demonstrating both static and dynamic federation
High-level components
• Monorepo root
• lerna.json (workspace orchestration)
• package.json (dev dependencies, scripts)
• packages/mf-cra (the core library/CLI)
• bin/mf-cra.js (CLI entry)
• scripts/overrides/webpack-config.js (patches CRA webpack config to add ModuleFederationPlugin)
• dynamicModuleFederation/* (runtime helpers: getOrLoadRemote, useFederatedComponent)
• examples/ (sample CRA apps)
• shell-app (host)
• app1, app2, redux-store (remotes)
• Each has moduleFederation.config.js, public/ + src/, bootstrap.tsx, index.ts
Core architectural patterns
• Monorepo (Lerna) for simultaneous versioning & local linking of library + samples
• Micro-frontend pattern via Webpack Module Federation:
• Build-time: mf-cra CLI reads moduleFederation.config.js → injects ModuleFederationPlugin into CRA’s webpack config → emits remoteEntry.js
• Runtime: host (shell-app) dynamically loads remoteEntry.js from remote apps and mounts exposed components (static import or via useFederatedComponent)
• Separation of concerns:
• CLI tooling (packages/mf-cra)
• Build configuration (moduleFederation.config.js in examples)
• Runtime federation logic (dynamicModuleFederation helpers)
Relationships and data flows
a. Developer invokes “mf-cra start/build” in an example app
b. CLI loads moduleFederation.config.js → patches CRA webpack config
c. Webpack builds each app, producing:
• host bundle + dynamic import hooks
• for each remote: remoteEntry.js + chunked modules
d. At runtime, host fetches remoteEntry.js from remotes → resolves exposed modules → renders federated components
• Optional: version badges or environment (NODE_ENV, PUBLIC_URL) callouts