Skip to content
Fallow home
All docs pages

Docs home

Misconfigured dependency overrides

What a misconfigured-dependency-override finding of fallow dead-code means, why it matters and how to fix it.

What it reports

Package-manager override has an unparsable key or value.

Dependencies explains how fallow finds it.

Why it matters

An entry in pnpm-workspace.yaml#overrides (skipped when packageManager names a pnpm version that ignores it: pnpm before 10.5.1, or pnpm 10 or earlier when the root package.json declares non-empty pnpm.overrides or resolutions), package.json#pnpm.overrides (skipped when packageManager names pnpm 11 or later, which does not read it), npm or Bun's top-level package.json#overrides, or Bun's package.json#resolutions whose key or value cannot be interpreted in that source's override grammar. Common shapes include an empty key, an empty value, a malformed version selector (@types/react@<<18), or an unbalanced parent matcher (react>). The active package manager may reject or ignore the entry. To fix: correct the key or value according to that package manager's grammar, or remove the entry. See also: fallow/unused-dependency-override.

Example

The root package.json declares overrides: { "axios": "" }. An empty override value is invalid and the active package manager will reject or ignore it.

Fix

Fix the key or value to match the active package manager's grammar. For pnpm this includes bare or scoped package names, version selectors, parent matchers, and the supported -, $ref, and npm:alias values. For npm or Bun, preserve the supported nested object shape. Remove experimental entries that should not remain.

Facts

FactValue
Issue typemisconfigured-dependency-override
Rule id in SARIF outputfallow/misconfigured-dependency-override
Commandfallow dead-code
Default severityerror
Config key in rulesmisconfigured-dependency-overrides
Filter option--misconfigured-dependency-overrides
Fixable with fallow fixNo
Opt-inNo