Skip to content

Strip hot-path console.log and enforce no-console lint rule #3

Description

@rupertgermann

Parent

#1

What to build

Remove debug console.log calls from hot paths (per-frame, per-shot, per-spawn code) and add an ESLint no-console rule (warn level, explicit allowlist for console.warn/console.error) so they cannot silently return.

Acceptance criteria

  • No console.log in entity update/fire paths, collision loop, wave spawn loop, or manager constructors
  • ESLint flags new console.log usage in src/
  • npm run lint passes
  • Game boots and plays unchanged

Blocked by

None - can start immediately

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentTriaged, ready for autonomous agent pickup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions