try {
  client.service(payload.path).emit(payload.event, payload.data)
} catch (error) {
  console.error(error) // ❌ Library shouldn't log directly
}

Suggested:
try {
  client.service(payload.path).emit(payload.event, payload.data)
} catch (error) {
  sseService.emit('error', error) // ✅ Let the app decide what to do
}

Why this matters:
1. Library best practice - Applications should control their own logging/error
reporting
2. Event processing errors - This catches errors in user event handlers that apps may
want to handle differently
3. Consistency - SSE client already emits 'connected' and 'disconnected' events

Unlike internal parsing errors (which can be silently handled), this error occurs when
processing user events - something the application should be aware of and potentially
handle (invalid service paths, malformed payload data, user handler exceptions, etc.).