Unused component outputs
What an unused-component-output finding of fallow dead-code means, why it matters and how to fix it.
What it reports
An Angular @Output() / signal output() output is emitted nowhere in its own component.
Dead code explains how fallow finds it.
Why it matters
A parent can bind to an output that the component never emits. The handler of the parent never runs, and no error tells anyone.
Example
user-card.component.ts declares @Output() close = new EventEmitter<void>() (or close = output<void>()) but this.close.emit(...) is called nowhere in the class.
Fix
Remove the unused output, or emit it from the class. If the output is part of a deliberately-stable public component API, suppress the line with // fallow-ignore-next-line unused-component-output.
Facts
| Fact | Value |
|---|---|
| Issue type | unused-component-output |
| Rule id in SARIF output | fallow/unused-component-output |
| Command | fallow dead-code |
| Default severity | warn |
Config key in rules | unused-component-outputs |
| Filter option | --unused-component-outputs |
| Suppression comment | // fallow-ignore-next-line unused-component-output |
Fixable with fallow fix | No |
| Opt-in | No |