[Chore] Strip debug console.debug/warn statements before production #4

New issue

Open

opened 2026-03-04 09:31:27 -08:00 by pyr0ball · 0 comments

pyr0ball commented

2026-03-04 09:31:27 -08:00

Owner

Debug logging currently active

Several diagnostic console.debug and console.warn statements were added during development:

LabelView.vue

[avocet] LabelView mounted
[avocet] fetchBatch start, queue length: N
[avocet] fetchBatch done, got N items, total: N
[avocet] handleSkip <id>
snapWidths() diagnostic function + requestAnimationFrame/setTimeout calls

EmailCardStack.vue

[avocet] swipe end <dir> lengthX: N

Decision

For a demo-facing tool, strip all debug logging before production/menagerie use. If runtime debugging is needed later, use Vue DevTools or a CF_DEBUG flag.

Acceptance Criteria

No console.debug or diagnostic console.warn in production build
snapWidths function and its timing calls removed
npm run build produces a clean bundle with no debug artifacts

## Debug logging currently active Several diagnostic `console.debug` and `console.warn` statements were added during development: **LabelView.vue** - `[avocet] LabelView mounted` - `[avocet] fetchBatch start, queue length: N` - `[avocet] fetchBatch done, got N items, total: N` - `[avocet] handleSkip <id>` - `snapWidths()` diagnostic function + `requestAnimationFrame`/`setTimeout` calls **EmailCardStack.vue** - `[avocet] swipe end <dir> lengthX: N` ## Decision For a demo-facing tool, strip all debug logging before production/menagerie use. If runtime debugging is needed later, use Vue DevTools or a `CF_DEBUG` flag. ## Acceptance Criteria - No `console.debug` or diagnostic `console.warn` in production build - `snapWidths` function and its timing calls removed - `npm run build` produces a clean bundle with no debug artifacts