Are eager: true and singleton: true supposed to work together?

[Aaronius]

We're using module federation and were hoping we could use both eager: true and singleton: true for each shared module in our shared config. We wanted to use eager: true so that the load of our host app would be faster since we know we'll need these modules in our host app right away. We wanted to use singleton: true so that only one instance each of the shared modules is loaded.

However, it appears that when both eager: true and singleton: true are set, that singleton: true gets ignored and multiple instances of a shared module are loaded (one from the host and one from the remote) if their semver ranges don't overlap.

Does anyone know if this behavior is intentional? Is using eager: true and singleton: true an anti-pattern?