better-result-adopt

To migrate TypeScript error handling from try/catch to typed Result patterns, convert imperative checks into Result chains and use Result.try/tryPromise at I/O boundaries. This progressively replaces thrown exceptions with deterministic Result.ok/err flows.

A TaggedError in TypeScript domain logic is a class that models domain failures with rich context. It replaces generic thrown exceptions, enabling precise error handling and typed Result-based pattern matching across your codebase.

Result.gen handles async boundaries in TypeScript by enabling deterministic composition through generator-based workflows. You use Result.await within Result.gen to sequence asynchronous operations without nested try/catch blocks.

Yes, you need the better-result library and standard TypeScript tooling as prerequisites to use TaggedError and Result.gen. These provide the foundational Result.try/tryPromise and generator-based workflow capabilities.

The best way to refactor a legacy module to adopt Result-based error handling is to run a guided migration targeting boundary operations first. Progressively migrate inner domain logic to Result chains and TaggedError definitions.

You should not use typed Result patterns over try/catch when migrating deeply nested imperative logic that lacks clear I/O boundaries or domain logic. Result-based patterns work best at boundary operations and domain logic.