Integration of: Module Federation Shared Dependency Monitor

[YanPes]

Clear and concise description of the problem

Hi guys,

I created a brower extension to easily monitor the shared dependencies on your current runtime using the __FEDERATION__ object.

https://chromewebstore.google.com/detail/module-federation-shared/iihmjeoimfipagokghlfeighikoonila

After sharing this on a stream in Twitch, @Nsttt requested to bring it to module-federation/core.

I would like to get some feedback from other contributors if you see this in the core repo or if referencing the plugin in the docs is sufficient.

I will create a PR after my vacation.

Suggested solution

Application already working live.
Either adding the extension in the docs (google chrome / firefox) links OR move the code to "core"

Alternative

No response

Additional context

Context and motivation can be read here: https://chromewebstore.google.com/detail/module-federation-shared/iihmjeoimfipagokghlfeighikoonila

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[2heal1]

Hey, thanks for the PR!

I tried the Chrome DevTools integration, and it looks nice. However, from what I can see, the feature set seems very similar to our existing Chrome DevTools. Could you clarify what new functionality or improvement this PR adds?

Also, if there are any features I missed, please let me know. Thanks!

https://module-federation.io/guide/debug/chrome-devtool.html

[YanPes]

Hi @2heal1,

My extension is designed around a specific use case and solves a personal painpoint of mine - monitoring the shared dependencies on large scale MF systems is cumbersome. The extension helps me to jump on a page and in less than 3 seconds see if there are issues on the versions and - most importantly - which team or application caused it.

I thought that other platform engineers or infrastructure people would benefit from it as well.
While the official MF extension provides a broad range of functionality, it is intentionally general-purpose and does not focus on this specific operational workflow.

In contrast, my extension focuses on a targeted experience centered on ecosystem visibility, dependency alignment, and actionable insights.

I can use the PR to just add my plugin to the docs as additional resource if that would be better suited :)