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
Copy file name to clipboardExpand all lines: apps/website-new/docs/en/configure/experiments.mdx
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,13 +31,13 @@ new ModuleFederationPlugin({
31
31
32
32
### `Hoisted` Runtime
33
33
34
-
When Runtime is `hoisted` the following happens:
34
+
When the runtime is `hoisted`, the following occurs:
35
35
36
-
This is useful configurations that need:
37
-
- runtimeChunk: single
38
-
- no `import()` in the user code
39
-
- the runtime packages of module federation are moved into the runtime chunks and out of the entrypoint.
36
+
These configurations are useful for:
40
37
38
+
- Setting or using`runtimeChunk: 'single'`.
39
+
- Avoiding the `import()` at the top of the app or in the entry point of user code to prevent eager consumption errors. In the past, this was often mandatory and commonly seen as `import('./bootstrap.js')` in example apps.
40
+
- Moving the Module Federation runtime packages into runtime chunks, keeping them out of the entry point - reducing code duplication
0 commit comments