Feature Overview (aka. Goal Summary)

An upstream frontend dynamic plugin solution will not include scalprum. We will need to figure out how to support plugins that are built with an upstream non-scalprum tool chain as well as plugins built with scalprum. This feature is about introducing an additional loader that supports loading dynamic frontend plugins that have been built using the module federation extended tooling.

Goals (aka. expected user outcomes)

Enable the ability to migrate to upstream frontend dynamic plugin support

Requirements (aka. Acceptance Criteria):

• It should be possible to load scalprum based frontend plugins
• It should be possible to load non-scalprum based frontend plugins

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

• there should be minimal configuration changes needed, i.e. existing frontend dynamic configuration should still work

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>