Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(angular): dynamic module federation should not reset remoteUrlDef…
…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)
- Loading branch information