effect-error-handling

Replace try/catch blocks with `Effect.try` and `Effect.tryPromise` to map errors to tagged types, and use `Option` to explicitly handle absent values, achieving predictable error propagation and type safety.

The best way to handle promise rejections is wrapping them with `Effect.tryPromise`, which safely catches rejections and maps them to specific tagged error types for explicit, exhaustive error management.

Match replaces complex if/else and switch statements with exhaustive, type-safe branching using discriminated unions, ensuring all potential cases are explicitly handled and preventing runtime errors.

Yes, you can refactor legacy codebase API interactions to use Effect's error handling, ensuring all potential errors are explicitly handled or propagated with type safety and exhaustiveness checking.

Use Option types to explicitly handle the absence of values instead of null or undefined checks, preventing runtime errors and ensuring predictable value management in your TypeScript projects.