Unused devDependencies
What an unused-dev-dependency finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Dev dependency listed but never imported.
Dependencies explains how fallow finds it.
Why it matters
Every install on every developer machine and in every CI run downloads the package. Its security advisories and version updates still need a review, for a package that no code uses.
Example
package.json lists left-pad, but no source, script, config, or plugin-recognized file imports it.
Fix
Remove the dependency after checking runtime/plugin usage. If another workspace uses it, move the dependency to that workspace.
Facts
| Fact | Value |
|---|---|
| Issue type | unused-dev-dependency |
| Rule id in SARIF output | fallow/unused-dev-dependency |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | unused-dev-dependencies |
| Filter option | --unused-deps |
Fixable with fallow fix | Yes |
| Opt-in | No |
Note. --unused-deps controls unused-dependency, unused-dev-dependency, unused-optional-dependency, type-only-dependency, test-only-dependency, and dev-dependency-in-production.