Currently, this logic is flawed so that if you set packageDir option to either string or array - it will override the readPkgUp logic.
I think this logic should remain, here is my use case:
- Mono repo with X packages
- I am prohibiting use of
devDependencies for all nested packages.
- Instead, all
devDependencies are defined in the workspace/repo root.
- All circular dependencies on sibling mono repo packages are defined in
peerDependencies.
- This means, since it's only a peer dep - using
packageDir cause this rule to miss the defined peer dep because it will only search what is defined in packageDir.
Currently, this logic is flawed so that if you set
packageDiroption to either string or array - it will override thereadPkgUplogic.I think this logic should remain, here is my use case:
devDependenciesfor all nested packages.devDependenciesare defined in the workspace/repo root.peerDependencies.packageDircause this rule to miss the defined peer dep because it will only search what is defined inpackageDir.