From 16a202371426e9c89b4843d3b1638d018f7cc538 Mon Sep 17 00:00:00 2001 From: zhangrenyang Date: Fri, 25 Dec 2020 08:16:48 +0800 Subject: [PATCH] Update ModuleFederationWebpack5.md Seems to be missing an `I` and a period? --- content/ModuleFederationWebpack5.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/ModuleFederationWebpack5.md b/content/ModuleFederationWebpack5.md index 4c158ce..fe38f17 100644 --- a/content/ModuleFederationWebpack5.md +++ b/content/ModuleFederationWebpack5.md @@ -204,7 +204,7 @@ There is a `ModuleFederationPlugin` to use Module Federation. Different properti To create a container the `exposes` property is the important one. Here all modules are specified that should be accessible for a consumer of the container. One can give them a public name, which is the name that the consumer has to use and point it a module in their own codebase (internal request). Any module is supported, it might be javascript, typescript, CSS, WebAssembly, assets, anything webpack can process in your codebase. -They consume other containers the `remotes` property is the goto property. t's an object with all containers that should be usable in the current build The key is a module scope at which the containers exposed modules should be accessible in the own codebase. Any request starting with this key will create a remote module that will be loaded at runtime. The value is the location of the container. By default `script` externals are used as container locations. Here one would specify an URL of a script file and a global. This script will be loaded at runtime and the container is accessed from the global. +They consume other containers the `remotes` property is the goto property. It's an object with all containers that should be usable in the current build. The key is a module scope at which the containers exposed modules should be accessible in the own codebase. Any request starting with this key will create a remote module that will be loaded at runtime. The value is the location of the container. By default `script` externals are used as container locations. Here one would specify an URL of a script file and a global. This script will be loaded at runtime and the container is accessed from the global. To share modules on any side the `shared` property should be used. For simple cases, a list of module specifiers can be provided which flag these modules (when used in the codebase) as a shared module. They will be provided in the currently installed version and consumed in a version range specified in the package.json of the consuming package.