Every finding under Risky — not recommended prints 0 B, because the row shows reclaimable, and reclaimable is deliberately zero for anything nothing will offer to move:
Risky — not recommended — 2 findings · 0 B
Build artifacts · 2 · 0 B
0 B ~/projects/dashboard/node_modules/react/index.js
matched rule node-modules: Regenerable via npm install.
referenced by 1 project
The zero is correct — keeping risky bytes out of the headline is the behaviour is_actionable in report.rs exists to guarantee, and it shouldn't change. But as a row in a list of files, 0 B reads as a bug or an empty file, and it hides the one number the user actually wants: how big is the thing I'm being told not to touch.
A 4 GB node_modules that three projects depend on and a 2 KB one look identical here.
Suggestion: show the file's real size on the row, and let the group subtotal keep carrying the reclaimable zero — the "Risky" heading already tells the user nothing here is on offer. Something like:
Build artifacts · 2 · 0 B reclaimable
604.0 MB ~/projects/dashboard/node_modules/react/index.js
Worth deciding the wording before implementing; the constraint is that no reader should come away thinking risky bytes count toward the reclaimable total.
Every finding under
Risky — not recommendedprints0 B, because the row showsreclaimable, andreclaimableis deliberately zero for anything nothing will offer to move:The zero is correct — keeping risky bytes out of the headline is the behaviour
is_actionablein report.rs exists to guarantee, and it shouldn't change. But as a row in a list of files,0 Breads as a bug or an empty file, and it hides the one number the user actually wants: how big is the thing I'm being told not to touch.A 4 GB
node_modulesthat three projects depend on and a 2 KB one look identical here.Suggestion: show the file's real size on the row, and let the group subtotal keep carrying the reclaimable zero — the "Risky" heading already tells the user nothing here is on offer. Something like:
Worth deciding the wording before implementing; the constraint is that no reader should come away thinking risky bytes count toward the reclaimable total.