You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example shows how to handle indipendent and nested routings in a MFE setup based on [webpack-module-federation](https://github.com/module-federation). The setup consists of:
3
+
4
+
-`app1` & `app2`: apps using a browser history strategy when acting as hosts and an in-memory history strategy when acting as remotes.
5
+
-`shell`: host app based on a browser history strategy that handles high-level routing. Shell routing determines mounting/unmounting of `app1` and `app2` remotes.
6
+
7
+
The shell is the only component responsible for updating browser url. The two level of history strategies (browser + in-memory) are kept in sync through an event-based communication between shell and remotes.
8
+
9
+
<br>
10
+
11
+
# Running Demo
12
+
- Install deps by running `npm install` in each of the MFE root folder (i.e. `app1`, `app2`, `shell`).
13
+
- Start apps by running `npm start` in each of the MFE root folder.
14
+
15
+
<br>
16
+
17
+
# Credits
18
+
The setup is inspired to https://github.com/StephenGrider/mfe.
0 commit comments