Browser Extension

[infoxicator]

This could be better as an addition to Medusa.

But it would be convenient to have a browser extension that overlays a tooltip with the federated module and version that is loaded on the page (Similar to what https://bit.dev/ do)

Also, to be able to swap remotes at runtime from the extension for testing.

[viktoriialurie]

@infoxicator hi! thank you for posting this topic!

we've been thinking in this direction and something that we have on our roadmap is about the chrome extension with the following description (for the MF case):

Short description
By leveraging a chrome extension, developers, QA engineers, and business users within an organization can more rapidly and reliably see federated updates without impacting end users.

Longer Description
When working with module federation there is often a need to be able to change which federated remote you are using and the state of that federated remote. Sometimes, as an example, a developer will be using the staging environment for their base application with a single module pointing to their local environment. This will allow them to see how a federated remote works in concert with other peers in an environment. Additionally a remote can be taken into an offline state or have its data replaced in real-time by the chrome extension to aid with troubleshooting specific issues. The chrome extension can also serve as a discovery point for federated remotes within an organization.

Business Value
Reduces environment costs because of flexibility for testing, reduces time to debug and test, and increases the reliability of the site.

Acceptance Criteria

• could be extra features when Medusa is enabled
• needs to work with both SSR and CSR
• highlighting remote entries similar to Bit.Dev does for highlighting components
• should be able to test remote and local modules and be able to switch them at runtime.

There is a chrome extension that is also available on the Medusa roadmap. With Medusa, it would also include the ability to publish the change to the environments (for example: updating prod to use a new federated remote that I just viewed/tested).

@zackarychapple any ideas/thoughts to add?

[zackarychapple]

I believe with the addition of the comment around highlighting remotes this is on par with what folks are expecting.