Empty catalog groups
What an empty-catalog-group finding of fallow dead-code means, why it matters and how to fix it.
What it reports
Named catalog group has no entries.
Dependencies explains how fallow finds it.
Why it matters
A named group under catalogs: in pnpm-workspace.yaml or Bun root package.json has no package entries. Empty named groups are leftover catalog structure after the last entry is removed. The default catalog map is intentionally ignored because some projects keep it as a stable hook.
Example
The catalog source declares catalogs: { react17: {} } after the last react17 entry was removed.
Fix
Delete the empty named group from the catalog source file. Comments between the deleted header and the next sibling can stay in place for manual review.
Facts
| Fact | Value |
|---|---|
| Issue type | empty-catalog-group |
| Rule id in SARIF output | fallow/empty-catalog-group |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | empty-catalog-groups |
| Filter option | --empty-catalog-groups |
Fixable with fallow fix | No |
| Opt-in | No |