Mitration from nx 17.3.2 to 18.3.5 breaks compilation (input production env NX_MF_DEV_SERVER_STATIC_REMOTES) about nx

[Coly010]

This seems like it may be a caching issue or a stale Nx Graph, such that your removal of

{
  "env": "NX_MF_DEV_SERVER_STATIC_REMOTES"
}

is invalidating the stale graph and allowing for a rebuild, as {env: string} is a valid input.

The other thing to check is whether "production" is in your namedInputs in the nx.json.

[ekiliqua]

Thank you for your response.

After reporting the issue, I continued testing and investigating. It seems that the error is caused because there is no configuration for "namedInputs". Shouldn't this be added automatically during the migration? If I remove these two lines, everything works perfectly:

And if we don't want to remove those two lines, we need to configure the namedInputs. I took these from a new project generated with nx@19. Shouldn't this be added automatically during the migration?:

Once I fixed that, I encountered a problem related to routing. The static servers for the applications that I haven't specified in "devRemotes" are not loading correctly. I've been reviewing the configuration of all the nx files, but I can't find the issue. I've seen related posts, but I can't seem to solve it... With a freshly generated project, routing works correctly, but after migrating the old project, it doesn't.

When I try to access any application, the same one always loads, regardless of which one I try to access. However, if I access an application specified in --devRemotes, that one works correctly...

Any ideas?

Thanks

[Coly010]

There is an issue with the migration but it is not that it needs to add those namedInputs, rather it should only add them if they exist.

Can you open a new issue for the remotes issue, with the version of Nx, and as much information as possible, including errors in the terminal and browser