Add a special logging tag to uncaught handler exceptions (#266)

## Why

We want to pipe uncaught errors in handlers to Sentry, we think it's ok
to do that via the logger as opposed to having a special error callback.

## What changed

- Add tag `uncaught-handler-error`
- Include `originalException` in `extras` (for proper stack traces)
- Change `extras` in logs from `unknown` to an optional `Record<string,
unknown>` (we're using it that way anyway, just makes it easier to
handle)

## Versioning

- [ ] Breaking protocol change
- [ ] Breaking ts/js API change

<!-- Kind reminder to add tests and updated documentation if needed -->

logging/log.ts

@@ -22,7 +22,8 @@ export type Tags =
   | 'invariant-violation'
   | 'state-transition'
   | 'invalid-request'
-  | 'unhealthy-session';
+  | 'unhealthy-session'
+  | 'uncaught-handler-error';
 
 const cleanedLogFn = (log: LogFn) => {
   return (msg: string, metadata?: MessageMetadata) => {
@@ -53,7 +54,7 @@ export type MessageMetadata = Partial<{
     traceId: string;
     spanId: string;
   };
-  extras: unknown;
+  extras?: Record<string, unknown>;
 }>;
 
 export class BaseLogger implements Logger {

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@replit/river",
   "description": "It's like tRPC but... with JSON Schema Support, duplex streaming and support for service multiplexing. Transport agnostic!",
-  "version": "0.200.3",
+  "version": "0.200.4",
   "type": "module",
   "exports": {
     ".": {

router/server.ts

@@ -515,7 +515,9 @@ class RiverServer<Services extends AnyServiceSchemaMap>
           },
           extras: {
             error: errorMsg,
+            originalException: err,
           },
+          tags: ['uncaught-handler-error'],
         },
       );
 

transport/impls/ws/connection.ts

@@ -1,7 +1,7 @@
 import { Connection } from '../../connection';
 import { WsLike } from './wslike';
 
-interface ConnectionInfoExtras {
+interface ConnectionInfoExtras extends Record<string, unknown> {
   headers: Record<string, string>;
 }