Angular Host Application

Angular Host Application Overview

Angular Host Application 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 angular host application focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

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

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

// usage
const ProductList = React.lazy(() => import('catalog/ProductList'));

The host declares remotes by URL and lazy-loads exposed modules like any dynamic import.

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

Module Federation Cheatsheet

Key Module Federation settings related to angular host application.

How Angular Host Application Works in Module Federation

Angular Host Application 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.

The host declares remotes by URL and lazy-loads exposed modules like any dynamic import.

• 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 Angular Host Application

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

Common Mistakes

• Copying angular host application snippets without understanding what each line does.
• Skipping error handling and edge cases when wiring up angular host application.
• Leaving angular host application untested, so regressions slip into production.
• Over-engineering angular host application before you actually need the extra flexibility.

Key Takeaways

• Angular Host Application is a core part of working effectively with Module Federation.
• Start small and keep angular host application focused on a single responsibility.
• Apply consistent patterns so angular host application scales across your project.
• Test and document angular host application to keep it maintainable over time.