Hey we don’t directly use them either but they do get used. It may seem excessive but when running the affected commands with Nx my guess is that those config files are used so the process would go something like Make some changes in lib1 Run test affected Nx would find the change in lib1 based on whatever base branch you specified Then it will ng test –project=lib1 and the run the tests using lib1 s jest config (or karma if you are using karma)
They are also useful if you need special configurations for some libs or apps but not others.
It may seem excess but they are there for a reason.
The same goes for building as it will ng build using the tsconfig in the lib.