Ng/improve error handling

[nikgraf]

No description provided.

[Copilot]

Pull Request Overview

This PR enhances error handling across the server by wrapping key operations in try/catch blocks, logging failures, and returning standardized error responses.

• Added try/catch in HTTP route handlers to catch, log, and respond to errors.
• Wrapped broadcast functions with try/catch to prevent unhandled exceptions during WebSocket operations.
• Introduced a WebSocket 'error' listener and try/catch in message processing for safer message handling.

Comments suppressed due to low confidence (2)

apps/server/src/index.ts:361

• Inconsistent error response formats: this handler uses plain text while the outer catch returns JSON. Standardize on a single JSON error schema (e.g., { message: string }) across all endpoints.

      res.status(401).send('Unauthorized');

apps/server/src/index.ts:600

• New error-handling branches in broadcast functions (e.g., broadcastSpaceEvents) are not covered by tests. Consider adding unit or integration tests to verify that errors during broadcasting are logged and that the system remains stable.

  try {

[Copilot]

[nitpick] Nested try/catch blocks in the /whoami route lead to redundant error handling. Consider consolidating into a single try/catch to simplify the flow and avoid duplicate catches.

[Copilot]

[nitpick] The repeated pattern of adding try/catch to each route suggests extracting common error handling into Express middleware or a helper function to reduce duplication and improve maintainability.