better-result-migrate-v2

To migrate better-result TaggedError classes, convert v1 class-based definitions to the v2 factory-based TaggedError("Tag")<{ ... }>() pattern. This updates class syntax, static helpers, and imports across TypeScript files.

Refactoring TypeScript error handling to factory-based APIs involves converting class definitions to factory patterns and adjusting constructors. The migration handles simple, computed, validation, and runtime-augmented errors with a safe, repeatable workflow.

Yes, the better-result v2 migration supports computed and runtime-augmented TaggedError types. It implements specific migration rules to transform simple, computed, validation, and runtime-augmented error definitions across multiple files.

When migrating to better-result v2, static helpers and imports are updated by switching usage from TaggedError.* methods to new API equivalents. The migration adjusts import statements accordingly across the TypeScript codebase.

Yes, you can automate TaggedError migration across multiple TypeScript files. The migration provides a safe workflow to analyze, transform, and apply changes across the codebase, ensuring consistent conversion from v1 to v2 API.

Migrating better-result TaggedError definitions to a factory-based API aligns legacy error handling with the modern API surface. This transition updates class syntax and static helpers to match the v2 factory pattern.