remotes initialized but is empty in other containers (federation runtime)

[hosseinmd]

Describe the bug

i have called init method of federation runtime in main container(or host)
import { init } from '@module-federation/runtime';
other containers doesn't know what the remotes are initialized in main container for solving this i add a patch to @module-federation/runtime-core

-            remotes: [],
+            remotes: CurrentGlobal.__FEDERATION__?.remotes || [],
             shared: {},

dev mode working after this change

to repreduce
https://github.com/callstack/super-app-showcase
in super-app-showcase remove remotes from ModuleFederationPluginV2 of all containers and add an init in host

Reproduction

https://github.com/callstack/super-app-showcase

Used Package Manager

npm

System Info

"@module-federation/enhanced": "0.8.7",

Validations

• Read the docs.
• Read the common issues list.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Module federation issue and not a framework-specific issue.
• The provided reproduction is a minimal reproducible example of the bug.

[ScriptedAlchemy]

Why do you want to access other containers remotes, if you consume them then you should register them in your plugin

[hosseinmd]

In our use case just first loaded container know what is the remotes and init them based on so many conditions. So i don't want to register them again, because of that conditions.

[hosseinmd]

Containers are using remotes but they don't know where is the remotes