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/guide/basic/runtime.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -412,9 +412,9 @@ registerRemotes([
412
412
413
413
`Federation Runtime` is one of the main features of the new version of `Module Federation`. It supports registering shared dependencies at runtime, dynamically registering and loading remote modules, and can expand the capabilities of `Module Federation` at runtime through `Plugin`. Build plugins are based on the basic implementation of Runtime.
414
414
415
-
There are the following differences between `Federation Runtime` and `CompilerPlugin`:
415
+
There are the following differences between `Federation Runtime` and `BuildPlugin`:
| Can be used independently of build plugins, and can directly use pure runtime for module loading in projects like `webpack4` | Build plugins require Webpack5, Rspack, Vite, or above |
420
420
| Supports dynamic registration of modules | Does not support dynamic registration of modules |
@@ -435,8 +435,8 @@ Compared to module loaders like Systemjs and esmodule, this brings the following
435
435
436
436
However, this model also brings the following impacts on the flexibility of the project and the maintenance cost of the build plugin:
437
437
438
-
- Different build tools such as Webpack, Rspack, and Vite all need to implement Module Federation separately: Builder build tools and runtime, which affects maintenance costs and feature consistency.
438
+
- Different build tools such as Webpack, Rspack, and Vite all need to implement `Module Federation`'s build tools and runtime separately, which impacts maintenance costs and feature consistency.
439
439
- Unable to consume remote modules in build plugins that do not support Module Federation, such as Webpack 4.
440
440
- Lack of flexibility, unable to dynamically add modules, change module behavior, and add more framework capabilities.
441
441
442
-
Therefore, in the new version of `Module Federation` design, `Runtime` has been separated, and different build tools implement the export build of modules, collection of shared module information, and handling of remote module references based on `Runtime`. Other specific behaviors such as shared dependency reuse and remote module loading are all built into Runtime.
442
+
Therefore, in the new version of `Module Federation` design, `Runtime` has been separated, and different build tools implement the export build of modules, collection of shared module information, and handling of remote module references based on `Runtime`. Other specific behaviors such as shared dependency reuse and remote module loading are all built into `Runtime`.
0 commit comments