Skip to content

docs(concepts): close issue #5308 #5309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 19, 2021
Merged

docs(concepts): close issue #5308 #5309

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions src/content/concepts/module-federation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -290,7 +290,7 @@ T> There is also an `'auto'` value available to [`output.publicPath`](/configura

## Troubleshooting

**`Uncaught Error: Shared module is not available for eager consumption`**
### `Uncaught Error: Shared module is not available for eager consumption`

The application is eagerly executing an application that is operating as an omnidirectional host. There are options to choose from:

Expand Down Expand Up @@ -348,7 +348,7 @@ new ModuleFederationPlugin({
});
```

**`Uncaught Error: Module "./Button" does not exist in container.`**
### `Uncaught Error: Module "./Button" does not exist in container.`

It likely does not say `"./Button"`, but the error message will look similar. This issue is typically seen if you are upgrading from webpack beta.16 to webpack beta.17.

Expand All @@ -363,7 +363,11 @@ new ModuleFederationPlugin({
});
```

**`Uncaught TypeError: fn is not a function`**
### `Uncaught TypeError: fn is not a function`

You are likely missing the remote container, make sure it's added.
If you have the container loaded for the remote you are trying to consume, but still see this error, add the host container's remote container file to the HTML as well.

### Collision between modules from different remotes

If you're going to load multiple modules from different remotes, it's advised to set the [`output.uniqueName`](/configuration/output/#outputuniquename) option for your remote builds to avoid collisions between multiple webpack runtimes.