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
Not all targetDependencies execute #10028
Comments
As it turns out, #9942 only partially addressed this issue. That PR took care of the situation where there are two targetDependencies and dependent projects have both of them. Before that PR, only the first dependency would run. What that PR does not address is the situation where a dependent project only has the second of the two dependencies. In that situation, that second dependency still doesn't run. In our (fairly extensive) monorepo, this is a common scenario. I've updated the repo at https://github.com/arabull/nx-deps-not-running to reflect this. The README explains in more detail what I said above. @FrozenPandaz I'm not sure of the proper protocol here. Should this issue be reopened, or do I need to file a new one? |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Still an issue. |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
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. |
Current Behavior
If there are more than two blocks in a particular target's
targetDependencies
withinnx.json
, the second one never executes.This regressed in 13.10 due to the fix for #9714.
Expected Behavior
All
targetDependencies
should execute.Steps to Reproduce
There is a repo that exhibits the issue at https://github.com/arabull/nx-deps-not-running. The key is having two blocks in
targetDependencies
:Environment
This happens on all Nx versions >= 13.10.
The text was updated successfully, but these errors were encountered: