Petition - re-open #11922 (support marking a subset of packages as 'affected' due to root level file change)

[Druotic]

Current Behavior

See: Changing a file referenced by a namedInput using {workspaceRoot} affects all packages #11922

This is an ongoing issue. Wanting to mark e.g. 3 out of 10 packages as 'affected' when a root level file changes seems like a fairly typical behavior. This functionality was previously supported here pre-v14.4. The new namedInputs equivalent seems to be all-or-nothing. See original ticket.

Let me know if there's a better way to '+1' the issue to help gauge interest. Because the original issue has been closed, I am unable to +1 the issue. I suspect there are other people out there that would have otherwise +1'd the issue, but moved on to another solution instead.

Expected Behavior

n/a

GitHub Repo

No response

Steps to Reproduce

n/a

Nx Report

n/a

Failure Logs

No response

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[zackarydev]

+1 We are having big issues with rebuilding the entire code base whenever a root file change occurs (Ex: a README should not rebuild all apps!)
#19277

[khalilou88]

Following this issue because i have similar issue here : khalilou88/jnxplus#423

[xeinebiu]

#19000 (comment)

[mpsanchis]

I'm also interested. Using https://github.com/khalilou88/jnxplus at the moment, and trying to trigger only the necessary modules

[github-actions]

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.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[Druotic]

I'm surprised this hasn't seen any activity lately. Is there a newer workaround for this? It still seems to be an issue.

[FrozenPandaz]

This was fixed with #22573. 🎉

[github-actions]

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.