Frontend Development 8 min read

Announcing Module Federation 2.0: New Features, Documentation, and Future Roadmap

Module Federation 2.0, released by ByteDance Web Infra and the original author, introduces best‑practice documentation, runtime‑tool decoupling, TypeScript type safety, a devtool, manifest protocol, and cross‑tool support to make micro‑frontend module sharing more flexible and developer‑friendly.

ByteDance Web Infra
ByteDance Web Infra
ByteDance Web Infra
Announcing Module Federation 2.0: New Features, Documentation, and Future Roadmap

Today we are excited to announce the official release of Module Federation 2.0, a new version co‑created by the ByteDance Web Infra team and Module Federation author Zack Jackson. This release addresses many issues of the previous version and is built on ByteDance’s internal practice and the existing community ecosystem.

Repository: https://github.com/module-federation/core

Official documentation: https://module-federation.io/

Why Use Module Federation 2.0?

Best‑practice documentation : A new standalone documentation site gathers best‑practice guides to help you use Module Federation more efficiently.

Runtime and build‑tool decoupling : The runtime is separated from build tools, standardising implementation across tools and making module loading more flexible.

Type safety : The build plugin automatically generates and loads TypeScript definitions, synchronising types in development mode to ensure accurate typing.

Debugging tools : A devtool is introduced to simplify debugging, giving developers a smoother experience when working with Module Federation.

Deployment platform support : The new mf‑manifest.json protocol simplifies version resource management and control on deployment platforms.

New Documentation Site

The new docs detail applicable scenarios and features of Module Federation, covering everything from creating a project with Rspack to the full lifecycle of using Module Federation, with in‑depth configuration explanations.

More Flexible Module Loading

The original Module Federation runtime embedded in Webpack has been extracted into an independent SDK, allowing dynamic registration and loading of remote modules without any build‑tool dependency. Pre‑loading and runtime plugin usage have also been enhanced for stronger control over the loading process.

Decoupling from Webpack – Supporting Cross‑Tool Module Sharing

The new plugin adopts a fresh runtime architecture, removing the strong binding between build tools and the runtime. Developers can now freely combine artifacts from different build tools (e.g., Webpack, Rspack) and assemble them at runtime, while maintaining consistent and standardised runtime behaviour.

Dynamic Type Hints

A breakthrough feature provides dynamic module type hints, automatically generating and using remote types and offering a real‑time type‑update experience similar to npm‑link when all projects run locally.

Module Federation Devtool

The Devtool visualises module dependency relationships, exposes and shared configurations, and can proxy remote modules to a local development environment with hot‑update support, delivering a smooth development experience.

Manifest Protocol

The build plugin generates a Manifest file containing essential information such as remoteEntry, shared, exposes, remotes, and type. This data is crucial for analysing inter‑project dependencies, enabling fine‑grained version and gray‑scale management across deployment platforms, and powering advanced features like the dynamic type‑hinting introduced in this version.

Acknowledgements

The development of the new Module Federation would not have been possible without the inspiration and support of many community projects, including the original Webpack Module Federation (forked and redesigned) and the Rspack project, which ensures full compatibility with the Rspack ecosystem.

Future Plans

Optimise developer experience : Enhance the debugging tool (e.g., visualise shared module reuse) beyond the current Chrome DevTools support.

Provide high‑performance solutions : Address the micro‑frontend “request waterfall” issue with strategies such as server‑side rendering (SSR) and data pre‑fetching.

Collaborate with the community : Extend the SDK to other build tools, combine with higher‑level frameworks, and publish best‑practice guides for micro‑frontend architectures based on Module Federation.

Try It Out

Repository: https://github.com/module-federation/universe

Quick Start guide: https://module-federation.io/zh/guide/start/quick-start.html

module federationWebpackfrontend architectureType Safetymicro frontendsdevtool
ByteDance Web Infra
Written by

ByteDance Web Infra

ByteDance Web Infra team, focused on delivering excellent technical solutions, building an open tech ecosystem, and advancing front-end technology within the company and the industry | The best way to predict the future is to create it

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.