Guides
The Guides pages of the Fallow documentation.
- Adopt in an existing repo: Adopt fallow in a repository with many findings: set a policy, fix the entry points, clean the backlog in order and stop new findings.
- Auto-fix: Preview, review, apply and verify the changes of fallow fix, which removes unused exports and unused dependencies.
- Trace a finding: Use the trace commands of fallow to see why it reports an export, a file, a dependency or a clone, or why it does not.
- False positives: When fallow reports code that your project uses, trace the finding, match the cause to the fix, and report a bug when fallow is wrong.
- Suppress a finding: Accept one finding on purpose with the narrowest suppression, give the reason, and remove the suppression when fallow reports it as stale.
- Baselines: Save the current findings in a baseline, commit it, and make CI fail only on new findings while you clean the backlog.
- Monorepo: Check that fallow finds each package of a monorepo, scope a run to one package or to the changed packages, and give a package its own rules.
- CRAP with Vitest: Configure Vitest coverage, pass the coverage file to fallow health, read the measured CRAP scores, and gate new risk in CI.
- Custom plugins: Write a plugin file that tells fallow the conventions of a framework it does not know, check it with fallow plugin-check, and share it.
- File types: Which file types fallow analyzes besides JavaScript and TypeScript, what it reads from each type, and what it reports.
- Known limits: Find the facts that fallow cannot know from your source code, the findings that they cause, and the fix for each.