better-result-adopt

To migrate TypeScript error handling to Result types, you replace try/catch blocks and Promise rejections with TaggedError classes and wrap I/O boundaries using Result.try or Result.tryPromise. This enables safer, predictable railway-oriented programming.

Railway-oriented programming in TypeScript is an error-handling approach where functions return Result values instead of throwing exceptions. It standardizes error flow by propagating Result types and leveraging pattern matching for predictable code execution.

To define domain errors using TaggedError classes, you create specific error classes extending TaggedError and map them to Result.err. This allows callers to pattern match on specific domain failures instead of catching generic exceptions.

Yes, you can wrap Promise rejections with Result-based error handling by using Result.tryPromise. This standardizes asynchronous error flows by catching Promise rejections at I/O boundaries and converting them into typed Result values.

Yes, migrating to better-result works with existing thrown exceptions. It targets codebases using thrown errors or try/catch blocks, applying TaggedError classes and Result boundaries to refactor callers into safer, typed error propagation.

The best way to standardize error flow at I/O boundaries in TypeScript is wrapping boundary functions with Result.try or Result.tryPromise. This converts unpredictable thrown exceptions and Promise rejections into typed Result values for reliable propagation.