Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Module Federation Documentation: Main Docs MIT 0 0 0 0 27 0 0

Overview

Project website module-federation.io/docs/en/mf-docs/0.19/getting-started
Project maintainers User avatar omfgnuts
Translation license MIT Module Federation Documentation: Main Docs
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,333 31,924 228,410
Translated 100% 1,333 100% 31,924 100% 228,410
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 1,333 100% 31,924 100% 228,410
Failing checks 2% 27 2% 700 2% 6,649
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 1,333 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

31,924
Hosted words
1,333
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
// Example 10: Providing an eager module
shared: {
...deps,
react: {
eager: true,
singleton: true,
requiredVersion: deps.react,
},
"react-dom": {
eager: true,
singleton: true,
requiredVersion: deps["react-dom"],
},
},
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Also, you may want your shared modules to be provided synchronously by making them "eager". Eager shared modules are not placed in an asynchronous chunk, enabling their use in the initial chunk. However, be careful with this feature as all provided and fallback modules will always be downloaded, which can lead to performance issues. It's recommended to use this feature judiciously, providing eager modules only at a single point of your app, such as the shell.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Shared modules can operate in a singleton mode where only a single version of the shared module is allowed. Any remote in the application can provide this version, even if it's a deeply nested remote requiring a higher version of the shared module. This version would then be used for the entire application.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Singleton Mode and Eager Loading
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
If the container attempts to provide a shared module that has already been used, a warning will be issued, and the provided shared module will be ignored. However, the container might still use it as a fallback.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Finally, we call `container.get` with the module path we want to load from the container. The `get` method returns a promise, so we use the `await` keyword to pause execution until the promise is resolved.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Then, we call `container.init` and pass `__webpack_share_scopes__.default` as the argument. This action initializes the container, and it may provide shared modules.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
Next, we assign a specific container (in this case, `someContainer`) to the `container` variable. You might retrieve the container from the window object or any other source depending on your application architecture.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
First, we initialize the share scope using `__webpack_initialize_sharing__`. This action fills the share scope with known provided modules from this build and all remotes.
10 months ago
User avatar None

Source string added

  1. Module Federation Documentation
  2. Module Federation Documentation: Main Docs
  3. English
In the above code:
10 months ago
Browse all changes for this language