Possiblity to integrate MF2.0 with native webpack module federation

[milkgod1]

Background

While some legacy projects could have many remote modules, it's impossible to upgrade all of their tech to MF2.0, I am wondering about if we could take intermediate ways.

Possible solutions

We only upgrade few modules to MF2.0 one time.

Question

MF2.0 and MF1.0 remote entry export are same with init/get function and could run remote as I tried while I am not sure if it's safe since its functionalities are totally different with lifecycle, share, runtime.

[milkgod1]

@ScriptedAlchemy Hi sorry for interruption, is it possible?

[ScriptedAlchemy]

It might be. But we stopped considering v1 over a year ago.
We didn't do anything to intentionally break it though. Just don't use any new capabilities. Best would be to try and see

[milkgod1]

@ScriptedAlchemy Thank you for your answer! I have tried already and it worked with right share (host v1 with remote v2 webpack plugin).
Could we just say that except what's new in MF2 like lifecycle, runtime, plugin etc. What v1 basically provide (I just mean share/remote/entry) would work same as v2 and they could work together.