Consumo de dependencias compartidas
Domine cómo compartir bibliotecas y dependencias comunes de forma eficiente entre aplicaciones federadas.
Consumo de dependencias compartidas es una lección gratuita de Micro Frontends Architecture with Module Federation en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Micro Frontends Architecture with Module Federation, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Micro Frontends Architecture with Module Federation incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
Why Share Dependencies?
In Micro Frontends, different parts of your application might use the same libraries, like React, Vue, or Lodash. Without careful management, each Micro Frontend could bundle its own copy of these libraries.
This means users would download the same code multiple times, increasing load times and wasting bandwidth. Sharing dependencies solves this problem!
The Problem: Duplicate Bundles
Imagine your main 'Host' application uses React, and a 'Remote' Micro Frontend also uses React. If both bundle React independently, your user's browser ends up downloading React twice.
- Host Bundle: Includes React
- Remote Bundle: Includes React (again!)
This leads to larger overall application sizes and slower performance.
Module Federation's Solution
Webpack's Module Federation offers a powerful solution: the shared configuration. It allows you to declare common libraries that should be shared across your federated applications.
Module Federation then ensures these libraries are loaded only once, even if multiple Micro Frontends depend on them.
Configuring `shared`
You define shared dependencies within the ModuleFederationPlugin in your webpack.config.js file. The shared property is an object where each key is the name of a module you want to share.
Here's a basic look at how it's structured:
new ModuleFederationPlugin({
// ... other configs
shared: {
// 'module-name': { options }
'react': { /* ... */ },
'react-dom': { /* ... */ }
}
})Sharing with `requiredVersion`
The requiredVersion option is crucial for compatibility. It specifies the acceptable version range for a shared dependency using semantic versioning (e.g., ^18.0.0).
Module Federation will try to use a compatible version already loaded; if none exists or it's incompatible, it will load a new one.
shared: {
react: {
requiredVersion: '^18.0.0',
// other options like singleton: true
},
'react-dom': {
requiredVersion: '^18.0.0'
}
}The `eager` Property Explained
Normally, shared modules are loaded asynchronously, on demand. However, sometimes a shared module is needed immediately at startup, before any remote modules are even requested.
For such cases, you can use the eager: true option. Be cautious, as this can impact initial load performance by forcing the module to load upfront.
shared: {
'my-critical-lib': {
requiredVersion: '^1.0.0',
eager: true // Load this module immediately
}
}Host & Remote `shared` Configs
Both your host and remote applications should typically define the same common libraries as shared. This tells Module Federation that these dependencies are part of the shared pool.
Module Federation then orchestrates which application actually loads the dependency and makes it available to others, ensuring only one copy exists in the browser.
Practical Use of Shared Deps
When react and react-dom are configured as shared, your application code can simply import them as usual. Module Federation handles the underlying logic to ensure they are loaded efficiently and only once.
This minimal React entry point demonstrates how standard imports leverage shared dependencies:
import React from 'react';
import ReactDOM from 'react-dom/client';
// This is a minimal React app entry point.
// If 'react' and 'react-dom' are shared in Module Federation,
// these imports will efficiently use a single instance.
function App() {
return (
<div>
<h1>Shared Dependencies Demo</h1>
<p>This app uses React, which can be shared!</p>
</div>
);
}
const rootElement = document.getElementById('root');
if (rootElement) {
const root = ReactDOM.createRoot(rootElement);
root.render(
<React.StrictMode>
<App />
</React.StrictMode>
);
} else {
console.error("Root element not found!");
}Benefits of Sharing Libraries
- Smaller Bundle Sizes: Prevents common libraries from being duplicated across different Micro Frontends, directly reducing the total amount of code users download.
- Improved Performance: Less code to download, parse, and execute means faster initial page load times and a more responsive user experience.
- Consistent Versions: Helps ensure all parts of your federated application use the same version of a library, reducing potential conflicts and unexpected behavior.
Shared Dependencies Check
Module Federation's shared configuration is crucial for efficient Micro Frontends. Which option correctly describes a key benefit of using shared dependencies?
Recap & Next Steps
We've learned how Module Federation's shared configuration is vital for optimizing Micro Frontends. By defining common libraries as shared, you prevent them from being bundled multiple times.
This leads to smaller initial load times, better performance, and more consistent dependency versions across your federated applications.
Next, we'll dive deeper into managing Singleton Modules & Versioning to ensure robust shared dependency handling.
Preguntas frecuentes
¿La lección «Consumo de dependencias compartidas» es gratis?
Sí — el texto completo de «Consumo de dependencias compartidas» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Micro Frontends Architecture with Module Federation, actualiza a CoddyKit PRO. El curso de Micro Frontends Architecture with Module Federation incluye 4 lecciones en total.
¿Qué aprenderé en «Consumo de dependencias compartidas»?
Domine cómo compartir bibliotecas y dependencias comunes de forma eficiente entre aplicaciones federadas. Practicas Micro Frontends Architecture with Module Federation con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Micro Frontends Architecture with Module Federation?
No se requiere experiencia previa. Micro Frontends Architecture with Module Federation en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.
¿Cuánto tiempo toma la lección «Consumo de dependencias compartidas»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Micro Frontends Architecture with Module Federation?
Sí. Cada lección de Micro Frontends Architecture with Module Federation incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Consumo de dependencias compartidas
- Módulos Singleton y control de versiones
- Carga dinámica de módulos
- Uso compartido de estado y utilidades entre remotos