-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MFE resolveRemoteUrl no longer working #27793
Labels
Comments
Work around seems like doing - |
Coly010
added
the
scope: module federation
Issues related to module federation support
label
Sep 16, 2024
Coly010
added a commit
that referenced
this issue
Sep 16, 2024
FrozenPandaz
pushed a commit
that referenced
this issue
Sep 18, 2024
…initions #27793 (#27927) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> When the `@nx/angular/mf` file is loaded, it sets `remoteUrlDefinitions = {}`. As this is a global, this can lead to erroneous behaviour by resetting existing definitions. It is also always truthy, breaking logic on whether urls need to be set or not. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> The object should be conditionally set if undefined when calling `setRemoteDefinition` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #27793, #27842 (cherry picked from commit d682bae)
Thanks 💯, works in newer version again 😎 |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Current Behavior
remoteUrlDefinitions was changed to being an object by default not null in #27051, so the provided check always passes and resolveRemoteUrl won't be called.
Expected Behavior
resolveRemoteUrl should be called by the code
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
NX 19.6.5
The text was updated successfully, but these errors were encountered: