Remote Routing

Remote Routing Overview

At its core, remote routing is about doing one thing well inside your Module Federation project. Once you understand the pattern, you can apply it consistently across features and teams.

Good remote routing pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

// 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 Routing 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 Routing example and grow it only as needed.
• Keep configuration explicit so Remote Routing behaves the same in every environment.
• Name things clearly so teammates understand your Remote Routing at a glance.
• Add tests around Remote Routing early to lock in expected behaviour.

Module Federation Cheatsheet

Key Module Federation settings related to remote routing.

How Remote Routing Works in Module Federation

Remote Routing 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 Routing

In production, remote routing 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 routing.
• Leaving remote routing untested, so regressions slip into production.
• Over-engineering remote routing before you actually need the extra flexibility.
• Ignoring documentation, which makes remote routing hard for the next developer to change.

Key Takeaways

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