Deleting config lib files make affected conmmand take every project as affected

[antoineducrot]

When deleting the .eslintrc.js file for example inside a library in an Nx workspace, the nx affected command unexpectedly considers all projects as affected. This behavior is unexpected because the .eslintrc.js file is specific to a single library and should not impact the entire workspace.

Steps to Reproduce:

Create an Nx workspace with multiple projects and libraries.

Ensure each library has its own .eslintrc.js file.

Delete the .eslintrc.js file from a specific library.

Run:

nx affected --base=main --head=HEAD

Observe that Nx considers all projects as affected.

Expected Behavior:

Nx should only mark the library (and potentially its dependents) as affected rather than the entire workspace.

Actual Behavior:

Nx marks all projects as affected, even those unrelated to the deleted .eslintrc.js file.