Is there a way to understand, why specific dependenciy is in lock file? #8012
JustFly1984
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm refactoring a repository with 107 packages.
One of them had a dependency on eslint-config-react-app
I had removed it from dependencies, removed node_modules, and made sure it does not appear in any place, removed pnpm-lock.yaml, run pnpm install -r, and for some reason it appears again in both, lock file and node_modules.
How to track where is it coming from? Npm has why command, but I do not see why command listed in pnpm -h
Genuinely interested, cos before, using yarn I could see something as dependency of other dependency, and in current case I see eslint-config-react-app in the root of lock file only
Beta Was this translation helpful? Give feedback.
All reactions