Comment syntax
Reference
| Comment | Scope |
|---|---|
// fallow-ignore-next-line | All issues on the next line |
// fallow-ignore-next-line <type> | Specific issue on the next line |
// fallow-ignore-file | All issues in the file |
// fallow-ignore-file <type> | Specific issue type for the file |
Issue type tokens
Use these tokens with suppression comments:| Token | Issue |
|---|---|
unused-file | Unused file |
unused-export | Unused export |
unused-type | Unused type |
unused-dependency | Unused dependency |
unused-dev-dependency | Unused devDependency |
unused-enum-member | Unused enum member |
unused-class-member | Unused class member |
unresolved-import | Unresolved import |
unlisted-dependency | Unlisted dependency |
duplicate-export | Duplicate export |
code-duplication | Code duplication |
When to use suppression
Prefer config-level solutions (rules, ignoreExports) for broad patterns. Use inline suppression for:- Individual false positives
- Intentional exceptions (e.g., exports for external consumers)
- Temporary suppression during migration
Config-level vs inline suppression
See also
Rules & Severity
Control issue severity at the project level.
Configuration
Full config file reference including ignoreExports and ignorePatterns.