You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated from Nx 17.0.2. Before update we started our app with nx serve shell and all module federation remotes automatically started. The were provided via manifest file.
After migration to 17.0.1 remotes are no longer started. The console shows this:
NX Starting module federation dev-server for myapp with 0 remotes
Current Behavior
I updated from Nx 17.0.2. Before update we started our app with nx serve shell and all module federation remotes automatically started. The were provided via manifest file.
After migration to 17.0.1 remotes are no longer started. The console shows this:
Relates to this issue too, I think: #19812 (comment)
This issue I think can be found here:
@nx/webpack/src/utils/module-federation/get-remotes-for-host.js ... new file introduced in Nx 17
There is a method called: extractRemoteProjectsFromConfig
As a result we are now having an array element in the remotes array object pushed.
Later in the main method there: getRemotes .. you are doing something like this :)
The collectRemoteProjects now get an array as first parameter r and trying to resolve the remote name in its method
But the remote is not some kind of string. It's the array of key names itself from the manifest file and returning undefined!
Bähmm :)
Please fix :)
Expected Behavior
Serving host should automatically work like in Nx 16.x
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
npm 9.8.1
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: