Remove console.log statements from pubsub module
Problem
The server/lib/broadcast/pubsub.js module contains console.log statements that output to stdout during normal operation:
📥 Client ${clientId} subscribed to "${channel}"
📤 Client ${clientId} unsubscribed from "${channel}"
📣 Published to "${channel}" (0 subscribers)
📣 Publishing to "${channel}" (${subscribers.size} subscribers)
Libraries should not log to console by default because:
- Pollutes application output - Mixes framework noise with application logs
- No user control - Can't filter, format, or redirect these logs
- Production overhead - Unnecessary I/O in production environments
- Not actionable - The "0 subscribers" case is valid behavior (fire-and-forget), not an error
Expected Behavior
api-ape should be silent by default. Users who want visibility into pub/sub activity can add their own logging in handler functions.
Proposed Solution
Remove all console.log statements from pubsub.js (and any other modules with similar logging).
Files Affected
server/lib/broadcast/pubsub.js
server/socket/send.js (has binary registration logs)
Remove console.log statements from pubsub module
Problem
The
server/lib/broadcast/pubsub.jsmodule containsconsole.logstatements that output to stdout during normal operation:Libraries should not log to console by default because:
Expected Behavior
api-ape should be silent by default. Users who want visibility into pub/sub activity can add their own logging in handler functions.
Proposed Solution
Remove all
console.logstatements frompubsub.js(and any other modules with similar logging).Files Affected
server/lib/broadcast/pubsub.jsserver/socket/send.js(has binary registration logs)