@kaitlynbassford/depwhy
v1.0.0
Published
Explains why a package is in your dependency tree, from the lockfile. npm, pnpm, yarn, bun, uv, poetry, cargo, and go.
Maintainers
Readme
depwhy
Why is this package in my dependency tree? depwhy reads your lockfile
(package-lock.json, pnpm-lock.yaml, uv.lock, Cargo.lock) and tells you, offline
by default, which direct dependencies pull a package in, what removing a direct
dependency would free, and which packages are installed at more than one version.
npm install -g @kaitlynbassford/depwhy # installs the `depwhy` command
npx @kaitlynbassford/depwhy lodash # or run it once
depwhy lodash
depwhy --remove express
depwhy --dupesThis npm package is a thin launcher. On install it downloads the matching native
binary for your platform from the
GitHub release of the same
version, checks its SHA-256 against the release's checksums.txt, and runs it. If
your npm skips install scripts (--ignore-scripts, or npm 12's default), the binary
is downloaded the first time you run depwhy instead.
The package is scoped because npm refused the plain name depwhy as too similar to the
existing package dep-why. The installed command is still depwhy.
Supported: Linux, macOS and Windows on x64 and arm64, Node.js 18 or newer.
Full documentation, flags, and the JSON format: https://github.com/dpologdvinity/depwhy
