Webpack 5 Module Federation - Shared library issue

Описание: Hello everyone! I hope this video has helped solve your questions and issues. This video is shared because a solution has been found for the question/problem. I create videos for questions that have solutions. If you have any other issues, feel free to reach out to me on Instagram:   / ky.emrah  

Below, you can find the text related to the question/problem. In the video, the question will be presented first, followed by the answers. If the video moves too fast, feel free to pause and review the answers. If you need more detailed information, you can find the necessary sources and links at the bottom of this description. I hope this video has been helpful, and even if it doesn't directly solve your problem, it will guide you to the source of the solution. I'd appreciate it if you like the video and subscribe to my channel!Webpack 5 Module Federation - Shared library issue

I have an npm module which I'd like to share between my host and remote apps, but when I'm debugging the app, it is obvious that for example a singleton class (from the npm module) is instantiated twice, first the debugger hits the module loaded by the host app, and then the same thing happens but this time using the module loaded from the remote app.
I have set all the settings (singleton, requiredVersion, eager: true) as per documentation, versions perfectly match - what am I missing? Is there a working example I could look at? Thanks.
(Btw a very similar issue is described with more details here: WP5 Module Federation: Singleton instantiated multiple times)
WP5 Module Federation: Singleton instantiated multiple times


Tags: webpack,webpack-5,micro-frontend,webpack-module-federationSource of the question:
https://stackoverflow.com/questions/7...

Question and source license information:
https://meta.stackexchange.com/help/l...
https://stackoverflow.com/