'What is even then point of eager shared libraries with Module Federation if they can never be shared?
I have two module federation builds (one loads the other), both using the same library, the host eager, the loaded one not, and no matter how I try to achieve this, it’s always loaded twice. If eager disables sharing why do you even list it under shared? I’m using the same shareScope for both modules, so I have no idea why it’s alway loaded twice. I literally tried almost every possible situation. Eager: true just doesn’t allow sharing. If I set eager to false on both it’s only loaded once, so I know my configuration is correct. I’ve set break points in the code to prove all of this.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|
