Async node MF (runtime loading), unable to use createInstance, still works with depreciated init (v0.15.0 -> v0.17.1)

[elliotBraem]

Describe the bug

I'm noticing issues using createInstance instead of init in the latest version 0.17.1.

In the reproduction I've provided, the main branch uses 0.17.1 with init and is properly registering and loading remotes, while branch v/mf-createInstance using the latest version and createInstance fails on loadRemote with error:

undefined is not an object (evaluating 'execOptions.factory.call')

To recreate, check out the reproduction and follow the readme. The only change is in mf.service.ts

I've moved a simple-transform plugin into the reproduction for easy testing, but this same error occurs with my published modules.

Reproduction

https://github.com/PotLock/usersdotfun/tree/v/mf-createInstance

Used Package Manager

npm

System Info

System:
    OS: macOS 15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-8557U CPU @ 1.70GHz
    Memory: 1.78 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.11.0 - ~/.nvm/versions/node/v22.11.0/bin/node
    Yarn: 4.9.2 - ~/.nvm/versions/node/v22.11.0/bin/yarn
    npm: 10.9.0 - ~/.nvm/versions/node/v22.11.0/bin/npm
    bun: 1.2.14 - ~/.bun/bin/bun
    Watchman: 2025.03.10.00 - /usr/local/bin/watchman
  Browsers:
    Brave Browser: 138.1.80.115
    Chrome: 137.0.7151.122
    Safari: 18.5

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.

[javinyx]

Hi, I am encountering the exact same issue, using init everything works as expected, while using createInstance and also using the instance to loadRemote nothing works.

[ScriptedAlchemy]

Does this solve it? PotLock/usersdotfun#1

[elliotBraem]

Does this solve it? PotLock/usersdotfun#1

Yes this does @ScriptedAlchemy, thank you! We can close this issue, unless other steps are recommended