0Pricing
Micro Frontends Architecture with Module Federation · Aula

Compartilhamento de módulos e componentes

Aprenda a expor componentes de uma aplicação remota e consumi-los em uma aplicação hospedeira.

Compartilhamento de módulos e componentes é uma aula grátis de Micro Frontends Architecture with Module Federation no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Micro Frontends Architecture with Module Federation, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Micro Frontends Architecture with Module Federation inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Intro to Module Sharing

In this lesson, we'll dive into the heart of Micro Frontends: sharing code!

We'll learn how one application can "expose" its components or modules, and how another application can "consume" them. This is key to building truly independent yet collaborative federated apps.

Understanding Exposed Modules

An exposed module is a piece of code (like a React component, a utility function, or even a data store) that one Micro Frontend application decides to make available to other applications.

  • Think of it like publishing a library.
  • The application making it available is called the Remote Application.
  • It's configured within the Remote's Webpack setup.

How a Remote Exposes

To expose a module, you configure the ModuleFederationPlugin in your remote application's webpack.config.js. The exposes property is where the magic happens.

You define a public name for the module and point it to its local path.

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

module.exports = {
  // ... other webpack config ...
  plugins: [
    new ModuleFederationPlugin({
      name: 'remoteApp',
      filename: 'remoteEntry.js',
      exposes: {
        './Button': './src/components/Button.jsx',
        './Header': './src/components/Header.jsx'
      },
      shared: ['react', 'react-dom']
    })
  ]
};

Example: Our Shared Button

Let's imagine a simple React button component that our remote application wants to share. This component lives in ./src/components/Button.jsx.

It's just a regular React component until we expose it.

// src/components/Button.jsx
import React from 'react';

const Button = ({ onClick, children }) => {
  return (
    <button
      onClick={onClick}
      style={{
        padding: '10px 20px',
        backgroundColor: '#007bff',
        color: 'white',
        border: 'none',
        borderRadius: '5px',
        cursor: 'pointer'
      }}
    >
      {children}
    </button>
  );
};

export default Button;

Consuming Remote Modules

On the flip side, a remote module is a module that an application wants to use, but it's hosted by another federated application.

  • The application consuming it is called the Host Application.
  • The Host needs to know where to find the Remote Application's exposed modules.

How a Host Consumes

The host application also uses the ModuleFederationPlugin. Here, you define the remotes property, mapping a local alias to the remote application's entry point.

The entry point is typically remoteEntry.js, generated by the remote app's Webpack build.

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

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

Importing & Using Shared Components

Once configured, the host application can import the remote component as if it were a local module. Webpack (via Module Federation) handles the dynamic loading from the remote URL.

Try running this simple example:

// This simulates a host app importing a remote component.
// In a real setup, 'remoteApp/Button' would resolve to the
// component exposed by the 'remoteApp' through Module Federation.
import React from 'react';
import ReactDOM from 'react-dom/client';

// Imagine 'remoteApp/Button' is the component we exposed earlier
// This import is resolved by Webpack's Module Federation Plugin
const RemoteButton = React.lazy(() => import('remoteApp/Button'));

function App() {
  return (
    <div>
      <h1>Host Application</h1>
      <React.Suspense fallback={<div>Loading Remote Button...</div>}>
        <RemoteButton onClick={() => alert('Button Clicked!')}>
          Click Me From Remote!
        </RemoteButton>
      </React.Suspense>
    </div>
  );
}

// Full entry point for a runnable React app
const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(<App />);

Behind the Scenes: Dynamic Loading

When the host application tries to import remoteApp/Button, Webpack doesn't look for it in the local node_modules. Instead, it uses the remotes configuration to:

  • Fetch the remoteEntry.js from the specified URL.
  • Load the exposed Button module from within that remote entry.
  • This happens dynamically at runtime, allowing independent deployments!

Best Practices for Sharing

When defining your exposes and remotes, keep these tips in mind:

  • Clear Naming: Use descriptive names for your exposed modules (e.g., ./UserProfileCard).
  • Consistent Aliases: Ensure your remote aliases in the host are easy to understand (e.g., marketingApp).
  • Relative Paths: Use relative paths (./src/...) for exposed modules within the remote app.

Test Your Understanding

You've learned how to expose and consume modules. Let's check your understanding of the core configuration!

Lesson Summary & Next Steps

Great job! You've learned the fundamental mechanics of sharing modules with Webpack Module Federation:

  • Exposing: Remote apps use exposes to make components public.
  • Consuming: Host apps use remotes to import and use those components.
  • This dynamic loading allows for independent development and deployment.

Next, we'll build a simple federated application from scratch, putting these concepts into practice!

Perguntas Frequentes

A aula “Compartilhamento de módulos e componentes” é grátis?

Sim — o texto completo de “Compartilhamento de módulos e componentes” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Micro Frontends Architecture with Module Federation, atualize para CoddyKit PRO. O curso de Micro Frontends Architecture with Module Federation inclui 4 aulas no total.

O que vou aprender em “Compartilhamento de módulos e componentes”?

Aprenda a expor componentes de uma aplicação remota e consumi-los em uma aplicação hospedeira. Você pratica Micro Frontends Architecture with Module Federation com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Micro Frontends Architecture with Module Federation?

Nenhuma experiência prévia é necessária. Micro Frontends Architecture with Module Federation no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Compartilhamento de módulos e componentes”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Micro Frontends Architecture with Module Federation?

Sim. Cada aula de Micro Frontends Architecture with Module Federation inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Configuração do projeto
  2. Compartilhamento de módulos e componentes
  3. Construção de uma aplicação federada simples
  4. Executando e Depurando seu Aplicativo Federado Localmente
← Voltar para Micro Frontends Architecture with Module Federation