tsentials-errors

You can create typed error values in TypeScript by using Err factory methods like Err.validation or Err.failure to build structured AppError objects with consistent error codes, descriptions, and metadata instead of relying on untyped exceptions.

You can attach metadata to structured TypeScript errors by using ErrorMetadata helpers such as fromRecord to generate a ReadonlyMap, passing it directly into Err factory methods like Err.validation when creating your typed AppError values.

The best way to convert caught exceptions into typed error objects is using Err.fromException, which transforms untyped caught exceptions into structured AppError values while allowing you to optionally override the error type and code.

Yes, you can combine multiple TypeScript errors into a single collection by using Err.combine, which collects multiple AppError objects together, and you can also use Err.equals to check structural equality by code, description, and type.

Structured error handling in TypeScript ensures your application returns consistent error codes, descriptions, and metadata across sync and async flows, avoiding the unpredictability and lack of type safety associated with throwing untyped exceptions.

Yes, using this Skill requires an ErrorType enum alongside Err factory methods and ErrorMetadata helpers, and you must use the .description property rather than .message when defining your typed AppError values.