better-result-adopt

Migrate error handling to typed Result patterns by replacing try/catch blocks and Promise rejections at I/O, API, and database boundaries with Result.try and Result.tryPromise, enabling consistent error typing and railway-style workflows.

A TaggedError class is a custom typed error definition used in Result-based patterns to create safer, composable error flows. Defining TaggedError types enables union error handling and consistent error propagation across modules.

Refactor callers to propagate Result values by removing try/catch blocks and handling the returned Result object directly. This shift enables railway-oriented programming where successful and failed states flow through typed operations without untyped exceptions.

Use Result.tryPromise when migrating asynchronous Promise-based boundaries like API or database calls, and use Result.try for synchronous operations. Both wrap existing error handling to return typed Result values instead of throwing untyped errors.

The best way to handle database and API errors without try/catch is wrapping those I/O boundaries with Result.tryPromise, defining TaggedError classes for specific failures, and refactoring callers to process the resulting typed Result values.