Hoisted runtime feature doesn't work

[smelukov]

Describe the bug

Seems like experiments: { federationRuntime: 'hoisted' } does not work as expected - embedded runtime is ignoring by webpack

1. create a simple mf-project or get some basic mf-examples
2. add experiments: { federationRuntime: 'hoisted' } to remote
3. start dev server
4. open host in browser and go to the network tab
5. try to find some part of embedded runtime code in bundles (for example Federation runtime accessed before instantiation or installation)

There is nothing to find

Expected behaviour:

• host creates a real runtime
• remotes use hoisted option, so use already created runtime

Reproduction

see above

Used Package Manager

pnpm

System Info

seems like it doesn't matter

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]

Sounds like you are using a ESM output, set library.type = 'import' not module
federation remotes are external, when hoisting the runtime you can end up in a situation where the imports that need the runtime are eagerly loaded before the runtime.

if you set it to import, it will use import(), and thus not have this issue as import from

[ScriptedAlchemy]

also if its modernjs, dont add hoisted runtime - we probably handle it under the hood.

[smelukov]

Sounds like you are using a ESM output, set library.type = 'import' not module

Nope, we have a webpack config with mf-plugin that does not specify any library.type

[ScriptedAlchemy]

can you share a repo or your build configs

[ScriptedAlchemy]

Hoisted runtime does not allow recycling the runtime across host remote, it hoists the modules into each runtime - and out of the entrypoints.