Closed orlevii closed 4 months ago
Hey 👋 - when deleting projects Nx has no way of knowing what projects depended on it prior to the deletion. To do this, Nx would need to persist changes to the graph over time, and the size of that data would get out of hand quickly.
If we were to remove this logic, it would be possible that projects which should be affected were missed and that's much more dangerous than having the longer CI times.
I'm going to go ahead and close this out. Let me know if you have further questions.
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
When running
nx print-affected --select projects
(ornx show projects --affected
) the output returns all the projects in the repository when deleting a project.I tried to ask as a discussions, but no replies. https://github.com/nrwl/nx/discussions/20548
(Tested on Linux and MacOS)
Expected Behavior
No project should be returned.
GitHub Repo
https://github.com/orlevii/nx-examples
Steps to Reproduce
I forked the
nx-examples
repository and deleted a project from theapps
directory.git checkout delete_app
npx nx print-affected --select projects
You can see the changes of this branch here: https://github.com/nrwl/nx-examples/compare/master...orlevii:nx-examples:delete_app
Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
This issue has huge impact on CI time when deprecating projects, it basically requires to build & test the entire monorepo every time there's a change like that.