Angular MFE setup is broken after migration from 17 to 18 or 19 about nx HOT 4 OPEN

Hi @leosvelperez. Thanks a lot for so quick response. The changes you made fix the issue with broken run, but the issue with static server is our main problem. Even if we fix the devRemotes option issue, we need a way to opt out one static server for all remotes feature, or something that will allow us dynamically set remote definitions in manifest when running locally.

from nx.

Hi @VanTigranyan !

Indeed, dynamic federation has issues with the new approach which was introduced to save CPU and RAM resources on machines, particularly when there are a large number of remotes to be served.

We are iterating on potential solutions and I hope to get a fix merged as soon as possible.

I'm sorry for the inconvenience caused by this change and I do hope to resolve it as soon as I can.

from nx.

Indeed

Awesome. Thank you very much. I am glad that it is on your radar. I should've reported this earlier, but I thought we could come up with a workaround. Unfortunately, no solution worked for us. So we'll eagerly wait for a solution from you. As I mentioned, even a simple opt-out would suffice, like disabling the single server with an option in project.json. Anyways, thanks again.

from nx.

Hi @VanTigranyan. An update from our side. We have decided on a fix for this and will look to implement it in the coming weeks.

from nx.