Utilizzo delle dipendenze condivise
Imparate a condividere in modo efficiente librerie e dipendenze comuni tra applicazioni federate.
Utilizzo delle dipendenze condivise è una lezione Micro Frontends Architecture with Module Federation gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Micro Frontends Architecture with Module Federation, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Micro Frontends Architecture with Module Federation include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
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.
Domande Frequenti
La lezione «Utilizzo delle dipendenze condivise» è gratuita?
Sì — il testo completo di «Utilizzo delle dipendenze condivise» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Micro Frontends Architecture with Module Federation, passa a CoddyKit PRO. Il corso Micro Frontends Architecture with Module Federation include 4 lezioni in totale.
Cosa imparerò in «Utilizzo delle dipendenze condivise»?
Imparate a condividere in modo efficiente librerie e dipendenze comuni tra applicazioni federate. Eserciti Micro Frontends Architecture with Module Federation con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare Micro Frontends Architecture with Module Federation?
Non è richiesta alcuna esperienza precedente. Micro Frontends Architecture with Module Federation su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.
Quanto tempo richiede la lezione «Utilizzo delle dipendenze condivise»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione Micro Frontends Architecture with Module Federation?
Sì. Ogni lezione Micro Frontends Architecture with Module Federation include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Utilizzo delle dipendenze condivise
- Moduli singleton e versionamento
- Caricamento dinamico dei moduli
- Condividere stato e utility tra i remote