Were there any dependency issues when using Module Federation?

When using Module Federation, dependency issues can indeed arise, especially if different micro-frontends use different versions of the same libraries. The main challenges are:

• Duplicating libraries in bundles, which increases the size of the final code.
• Version conflicts, where one part of the application expects one version, and another expects a different one.
• Inconsistent component behavior due to different dependency versions.

To minimize these problems, it is common to:

• Share common dependencies in a shared scope and configure them as singleton so that all micro-frontends use the same version.
• Carefully monitor library versions and try to synchronize them.
• Use strict rules for updating dependencies.

Example of configuring shared dependencies in webpack Module Federation:

new ModuleFederationPlugin({
  name: 'app1',
  remotes: { /* ... */ },
  shared: {
    react: { singleton: true, requiredVersion: '^17.0.0' },
    'react-dom': { singleton: true, requiredVersion: '^17.0.0' },
  },
});