You can consider the module federation capabilities provided by this repository as "module federation 2.0". "Module Federation 2.0" differs from the "Module Federation" built into webpack 5 by offering not only the core features of module export, loading, and dependency sharing but also additional dynamic type hinting, a "Manifest", a "Federation Runtime", and a "Runtime Plugin System". These features make "Module Federation" more suitable for use as a micro-frontend architecture in large-scale web applications.
-
Module Federation is a concept that allows developers to share code and resources across multiple JavaScript applications
-
Module Federation can be used to split monolithic applications into micro-front-end architectures
-
Module Federation reuses common dependencies between modules as much as possible
- 🎨 Module Federation Runtime
- 🧩 Runtime Plugins System
- 📝 Manifest
- 🚀 Dynamic type prompt
- 🛠️ Chrome Devtool
To get started with Module Federation, see the Quick Start.
Come and chat with us on Discussions or Discord! The Module federation team and users are active there, and we're always looking for contributions.
New contributors welcome!
Please read the Contributing Guide.
Working on this repository requires Node.js 24 and pnpm 10.28.0. The repository's development, test, build, and release workflows run on Node.js 24.
Published packages that execute in Node.js, including build plugins, command-line tools, type generation, workers, and server-side runtime code, remain compatible with Node.js 20.19.5. CI builds the packages on Node.js 24, installs the resulting package tarballs in a clean Node.js 20.19.5 project, and verifies their CommonJS, ES module, command-line, and type entry points. The clean TypeScript project is also built with both Webpack and Rspack, and the resulting Node.js bundles are executed on Node.js 20.19.5.
Browser runtime compatibility is defined by the browser build targets rather than the Node.js version used to maintain this repository. Node.js 20 compatibility is provided for legacy consumers even though Node.js 20 no longer receives upstream maintenance.
This repo has adopted the Code of Conduct. Please check Code of Conduct for more details.