fix(js): filtering of local dependencies when running nx release version

[kraenhansen]

This closes #19990 by moving the filter onto the flat list of local dependencies instead of requiring just one of the local dependencies to match the target.

Current Behavior

If just one local dependent project / dependency match the target all dependents would be included as dependentProjects resulting in the behaviour outlined in #19990.

Expected Behavior

The dependentProjects include only dependent projects / local dependencies that are actually relevant for a particular project, resulting in the expected package.json when running nx release version.

Related Issue(s)

Fixes #19990

[vercel]

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	Nov 11, 2023 5:33pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f910106. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=fec681be13ab901775c0f31c660db8b4ac94c0ca --head=f910106364a14d7bbb1a8f8ff80ef8e8b6ebefe9 --parallel=1
• nx affected --targets=lint,test,build --base=fec681be13ab901775c0f31c660db8b4ac94c0ca --head=f910106364a14d7bbb1a8f8ff80ef8e8b6ebefe9 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=fec681be13ab901775c0f31c660db8b4ac94c0ca --head=f910106364a14d7bbb1a8f8ff80ef8e8b6ebefe9
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=fec681be13ab901775c0f31c660db8b4ac94c0ca --head=f910106364a14d7bbb1a8f8ff80ef8e8b6ebefe9

---

Sent with 💌 from NxCloud.

[JamesHenry]

Thank you @kraenhansen! You're not only using an undocumented alpha feature but also submitting fixes for it to 💙

Please do be aware thought that there are likely some more breaking config changes coming within the next couple of weeks that will not be automatically migrated.

As soon as we document it and remove that alpha label, all the usual migrations etc will be applied to future versions

[kraenhansen]

The failures seem unrelated to my change or at least from what I can see. I just rebased, to give the tests another go.

[JamesHenry]

Thanks again @kraenhansen!

[github-actions]

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.