-
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
skipRemotes option broken due to reference to projectGraph #17473
Labels
outdated
scope: angular
Issues related to Angular support in Nx
scope: react
Issues related to React support for Nx
type: bug
Comments
Coly010
added
scope: react
Issues related to React support for Nx
scope: angular
Issues related to Angular support in Nx
labels
Jun 8, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 8, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 9, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
to Coly010/nx
that referenced
this issue
Jun 30, 2023
Coly010
added a commit
that referenced
this issue
Jul 5, 2023
FrozenPandaz
pushed a commit
that referenced
this issue
Jul 7, 2023
This was referenced Aug 1, 2023
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
outdated
scope: angular
Issues related to Angular support in Nx
scope: react
Issues related to React support for Nx
type: bug
Current Behavior
When you run projects using the module-federation-dev-server,
skipRemotes
now only can detect projects that are returned fromreadCachedProjectGraph
, effectively making it unusable.If the projects are in a different repository and are not running (which is my use-case and is also other's use-case as well I'm sure), it won't be able to find them.
Expected Behavior
Specifying projects in
skipRemotes
that are not in the same repository should work perfectly fine.GitHub Repo
No response
Steps to Reproduce
skipRemotes
input with the remote's project name.Nx Report
Failure Logs
No response
Operating System
Additional Information
Caused by #17185
The text was updated successfully, but these errors were encountered: