Problem
There are roughly 18 console.log calls across src/. Debug logging left in shipped code clutters the browser console, can leak internal state or payloads to end users, and makes real errors harder to spot.
What needs to be done
- Locate the
console.log calls in src/ (grep -rn "console.log" src).
- Remove those that were debugging aids.
- For logging that is genuinely useful, route it through a small logger helper that is silent in production builds (for example gated on
import.meta.env.DEV), or convert it to console.warn/console.error where it represents a real problem.
- Add an ESLint rule (
no-console, allowing warn/error) to prevent regressions, coordinated with the lint-script issue.
Files
- files under
src/ containing console.log
eslint.config.js
Acceptance deliverables
- No stray
console.log remains in application code.
- Lint fails if a new
console.log is introduced.
Tests to pass
npm run lint exits 0 with the no-console rule enabled.- Existing tests continue to pass.
Problem
There are roughly 18
console.logcalls acrosssrc/. Debug logging left in shipped code clutters the browser console, can leak internal state or payloads to end users, and makes real errors harder to spot.What needs to be done
console.logcalls insrc/(grep -rn "console.log" src).import.meta.env.DEV), or convert it toconsole.warn/console.errorwhere it represents a real problem.no-console, allowingwarn/error) to prevent regressions, coordinated with the lint-script issue.Files
src/containingconsole.logeslint.config.jsAcceptance deliverables
console.logremains in application code.console.logis introduced.Tests to pass
npm run lintexits 0 with theno-consolerule enabled.