- Description
- Code demos
- Shared dependencies
- Multi-frameworks with Module Federation
- Pitfalls
- Recommendations when using Module Federation
- Native Federation
- Other learning material
- Micro frontends
This repo came about as a result of my journey to learn how to use Webpack Module Federation as a vehicle to implement micro-frontend architectures.
Module federation allows a JavaScript application to dynamically load code from another application — in the process, sharing dependencies, if an application consuming a federated module does not have a dependency needed by the federated code — Webpack will download the missing dependency from that federated build origin. 1
The repo is structured as a learning guide to Webpack Module Federation. I advise you to go through each section in the order they are presented.
Note
This repo uses Angular as the frontend framework to explore Webpack Module Federation but a lot of the concepts explained are applicable regardless of the frontend framework.
Read the Code demos overall notes before exploring the code demos.
Note
You can use github.dev to explore the code demos without cloning the repo. As long as you're logged in to github.com, you can just press . (dot) on this repo page and the repo will be opened in the github.dev editor, a lightweight editing experience that runs entirely in your browser.
| Demo | Description |
|---|---|
| basic-ng16 Both shell and remote app use Angular 16. |
The most bare-bones possible example of how to setup Webpack Module Federation where the shell lazy loads an Angular module using Angular routing. This code demo does NOT make use of the @angular-architects/module-federation npm package which is usually used to setup module federation for Angular projects. The main idea is to show the basics for learning purposes. The remote webpack module contains an Angular module which the shell loads using Angular routing. |
| angular-architects-ng16 Both shell and remote app use Angular 16. |
Same as the basic-ng16 example but instead of manually doing all the module federation setup, it uses the @angular-architects/module-federation npm package which is a package that aims to streamline the module federation setup for Angular apps. The remote webpack module contains an Angular module which the shell loads using Angular routing. |
| dynamic-ng16 Both shell and remote app use Angular 16. |
Shows how to setup module federation without having to declare a remote in the shell's webpack configuration file. This code demo is called dynamic because it does NOT require the remote to be declared in the shell's webpack configuration. Despite not being part of this example, it would be simple to extend it and have the remote webpack module location fetched at runtime via an HTTP call. The remote webpack module contains an Angular module which the shell loads using Angular routing. |
| dynamic-manifest-ng16 Both shell and remote app use Angular 16. |
Same as the dynamic-ng16 example but shows how to use a manifest file to hold the configuration of the remotes. The remote webpack module contains an Angular module which the shell loads using Angular routing. |
| component-ng16 Both shell and remote app use Angular 16. |
The shell dynamically instantiates an Angular component and adds it to the DOM. This example also shows how to pass inputs to the Angular component. The remote webpack modules contain an Angular Module and an Angular component which the shell dynamically loads without using Angular routing. It shows 4 different ways to load the Angular module/component. |
| component-standalone-ng16 Both shell and remote app use Angular 16. |
The shell loads an Angular standalone component by using Angular routing and by dynamically instantiating an Angular standalone component and adding it to the DOM. This example also shows how to pass inputs to the Angular component and subscribe to its outputs. The remote webpack module contains an Angular standalone component. |
| component-directive-ng16 Both shell and remote app use Angular 16. |
Same as the component-ng16 example but using a reusable Angular directive. This example also shows how to pass inputs to the Angular component and subscribe to its outputs. The remote webpack module contains an Angular component. The Angular directive in this code demo could also be used with Angular standalone components. |
| routes-ng16 Both shell and remote app use Angular 16. |
Using Angular routing, the shell loads a couple of remote Angular standalone components from the routes that are exposed from the mfe1 app. The remote webpack module contains a variable that represents an array of Angular routes. |
| web-component-ng16 Both shell and remote app use Angular 16. |
Shows how to setup module federation where the shell loads a Web component created from an Angular standalone component. This example also shows how to use the inputs and outputs of the converted Angular component, which are mapped to Web component custom properties and custom events, and how to get strict type checking and IDE auto-completion on HTML for web components. The remote webpack module contains a function that registers the Web component. |
| web-component-directive-ng16 Both shell and remote app use Angular 16. |
Same as the web-component-ng16 example but using an Angular directive to bootstrap the Web component. The remote webpack module executes a function that registers the Web component. |
| web-component-angular-architects-wrapper-ng16 Both shell and remote app use Angular 16. |
The shell uses a generic Angular component that acts as a wrapper for the remotely loaded Web component. It shows how to use the generic component directly on the HTML and with Angular routing. This example also shows how to set properties and listen to events from the Web component. The remote webpack module executes a function that registers the Web component. |
| multi-version-ng The shell uses Angular 16 and the remote apps use Angular 16, Angular 14 and Angular 12. |
Shows how to setup module federation solution where the shell loads remote apps that are in different versions of Angular. |
| communication-custom-events-ng16 Both shell and remote app use Angular 16. |
The setup is the same as the web-component-ng16 code demo. The focus of this demo is on showing how communication between different micro frontend apps and the shell app can be implemented. |
| communication-event-bus-ng16 Both shell and remote app use Angular 16. |
The setup is the same as the web-component-ng16 code demo. The focus of this demo is on showing how you can create an abstraction on top of the browser Custom Events to act as an Event Bus/Aggregator, which you can use throughout the app to subscribe to strongly typed events. |
| advanced-ng16 Both shell and remote apps use Angular 16. |
This code demo focuses on showing how you can structure your shell app code in regards to loading micro frontend apps. It also provides an implementation of tooling that helps standardize how you load micro frontend apps in Angular as well as handle related errors. |
The shared section of the ModuleFederationPlugin configuration let's you define libraries that are shared between your federated modules. This means you can, among other things, prevent the same library from being loaded several times. For instance, if you have a shell using Angular 16 and 3 remotes also using Angular, you can define the Angular libraries as singletons in the shared section of the module federation configuration and the Angular libraries will only be downloaded once.
The shared section of the ModuleFederationPlugin configuration is also what you would use if you want to share cross cutting concerns across the shell and youre remotes. Things like authentication, logging or even some shared state.
For more information see the Shared modules in Webpack Module Federation documentation page.
The code demos in this repo focus on Angular apps. If you're interested in a multiple framework setup where you can use different frameworks like Angular, Vue, React, etc on a single app, then check the Webpack Module Federation and multi-frameworks documentation page.
See the following two articles for more information about common pitfalls and workarounds:
- Pitfalls with Module Federation and Angular: the goal of this article is to show typical pitfalls that come when using Module Federation together with Angular and strategies for avoiding them.
- Multi-Framework and -Version Micro Frontends with Module Federation: The Good, the Bad, the Ugly: combining Module Federation and Web Components brings several advantages. But there are also some pitfalls we need workarounds for.
This document presents some of my recommendations when using Webpack Module Federation.
As part of learning about Webpack Module federation I also came across Native Federation.
In order to be able to use the proven mental model of Module Federation independently of webpack, the Native Federation project was created. It offers the same options and configuration as Module Federation, but works with all possible build tools. It also uses browser-native technologies such as EcmaScript modules and Import Maps. This measure is intended to ensure long-term support from browsers and also allow alternative implementations.
Native Federation is called before and after the actual bundler in the build process. That's why it doesn't matter which bundler is actually used.
For more information on Native Federation and how to setup an app with it see:
- Micro Frontends with Modern Angular – Part 1: Standalone and esbuild.
- The Usage/Tutorial section of the
@angular-architects/native-federationnpm package.
Note
The concepts explained in this repo and other articles written about Module Federation also apply to Native Federation because they share the same API.
There are several links spread throughout the READMEs and the code of the code demos about documentation/articles/videos. However, I thought it would be good to call out a few links that either didn't make sense in any particular place of the code demos or that I found fundamental to learning about Module Federation.
You can find them on this page.
Module Federation is only a small part of the micro frontends universe. If you want to learn more explore the following links with a curated list of resources on micro frontends: