27 replies

Using `Effect.fn` with ManagedRuntime for Better Stack Traces in tRPC

I know stack traces with Effect can be tricky due to its laziness, and I also know that

Effect.fn

Effect.fn

should help solve some of these issues.

Is it then recommended to use

Effect.fn(...)(...)().pipe(MyRuntime.runPromise)

Effect.fn(...)(...)().pipe(MyRuntime.runPromise)

when using a

ManagedRuntime

ManagedRuntime

tRPC

tRPC

for example? We use

Effect.fn

Effect.fn

everywhere but our stack traces are still almost completely unusable.