Module Federation: eagerly shared lib and default shareScope using two module federation builds

Question

When a single build declares a shared { eager: true } lib everything works fine. When I add an import to a second remote module federation build unless I change the shareScope in the first build to something other than the default scope. The shareScope always resolves to a promise - and therefore I get the cannot load lib eagerly standard error.

Looking to understand if this is expected, and how to properly share eagerly shared libs across two different module federation build, if that is a typical use case.