Team Ownership

Team Ownership Overview

Team Ownership is a building block you will reach for often in Module Federation. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn team ownership properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real Module Federation projects.

const { ModuleFederationPlugin } = require('webpack').container;

module.exports = {
  plugins: [
    new ModuleFederationPlugin({
      name: 'shell',
      remotes: { catalog: 'catalog@http://localhost:3001/remoteEntry.js' },
      exposes: {},
      shared: { react: { singleton: true }, 'react-dom': { singleton: true } },
    }),
  ],
};

ModuleFederationPlugin configures which modules an app exposes, consumes, and shares.

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

Module Federation Cheatsheet

Key Module Federation settings related to team ownership.

How Team Ownership Works in Module Federation

Team Ownership 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.

ModuleFederationPlugin configures which modules an app exposes, consumes, and shares.

• 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 Team Ownership

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

Key Takeaways

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