Skip to content
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

fix(module-federation): dynamic remotes external to workspace should be skipped correctly #26551 #26692

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

Coly010
Copy link
Contributor

@Coly010 Coly010 commented Jun 26, 2024

Current Behavior

Module Federation utils were not checking if the remotes defined dynamically in the module-federation.manifest.json were in the project graph.

Expected Behavior

Check that the dynamic remotes exist in the project graph before trying to do work with them

Related Issue(s)

Fixes #26551

@Coly010 Coly010 requested a review from jaysoo as a code owner June 26, 2024 09:11
@Coly010 Coly010 self-assigned this Jun 26, 2024
Copy link

vercel bot commented Jun 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Jun 26, 2024 9:13am

@Coly010 Coly010 merged commit ce3f7f4 into master Jun 26, 2024
6 checks passed
@Coly010 Coly010 deleted the mf/fix-skipping-unknown-dyn-remotes branch June 26, 2024 14:09
FrozenPandaz pushed a commit that referenced this pull request Jun 26, 2024
…be skipped correctly #26551 (#26692)

<!-- 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 -->
Module Federation utils were not checking if the remotes defined
dynamically in the `module-federation.manifest.json` were in the project
graph.

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
Check that the dynamic remotes exist in the project graph before trying
to do work with them

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #26551

(cherry picked from commit ce3f7f4)
Copy link

github-actions bot commented Jul 2, 2024

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dynamic Module federation failing when referencing a remote not in same project as host
2 participants