Remote Entry

Remote Entry Overview

Remote Entry lets you structure Module Federation work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep remote entry focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

// remote (webpack.config.js)
const { ModuleFederationPlugin } = require('webpack').container;

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      name: 'catalog',
      filename: 'remoteEntry.js',
      exposes: {
        './ProductList': './src/ProductList',
      },
      shared: ['react', 'react-dom'],
    }),
  ],
};

A remote exposes modules through remoteEntry.js so hosts can load them at runtime.

Remote Entry Example

new ModuleFederationPlugin({
  name: 'app',
  filename: 'remoteEntry.js',
  exposes: { './Widget': './src/Widget' },
  remotes: { other: 'other@http://host/remoteEntry.js' },
  shared: { react: { singleton: true } },
});

• Start from a minimal Remote Entry example and grow it only as needed.
• Keep configuration explicit so Remote Entry behaves the same in every environment.
• Name things clearly so teammates understand your Remote Entry at a glance.
• Add tests around Remote Entry early to lock in expected behaviour.

Module Federation Cheatsheet

Key Module Federation settings related to remote entry.

How Remote Entry Works in Module Federation

Remote Entry builds on Module Federation's ability to load code from another independently built and deployed application at runtime. Each app can be a host, a remote, or both.

A remote exposes modules through remoteEntry.js so hosts can load them at runtime.

• Remotes expose modules through a remoteEntry.js manifest.
• Hosts declare remotes and import exposed modules dynamically.
• Shared dependencies are deduplicated, ideally as singletons.
• Each micro frontend builds and deploys on its own schedule.

Practical Guidance for Remote Entry

In production, remote entry needs careful version management and graceful failure handling. Align shared dependency versions and always render a fallback when a remote cannot load.

Common Mistakes

• Skipping error handling and edge cases when wiring up remote entry.
• Leaving remote entry untested, so regressions slip into production.
• Over-engineering remote entry before you actually need the extra flexibility.
• Ignoring documentation, which makes remote entry hard for the next developer to change.

Key Takeaways

• Remote Entry is a core part of working effectively with Module Federation.
• Start small and keep remote entry focused on a single responsibility.
• Apply consistent patterns so remote entry scales across your project.
• Test and document remote entry to keep it maintainable over time.