error-handling

To fix floating promises in TypeScript, you must ensure asynchronous operations are properly awaited or handled with catch blocks to prevent unhandled rejections. This skill identifies those promises and provides patterns to resolve them.

Throwing non-Error objects in JavaScript causes lost stack traces because the runtime cannot attach call stack information to plain objects. Enforcing the use of Error objects or custom error classes preserves stack traces for debugging.

The best way to eliminate silent catch blocks in Node.js is to ensure caught errors are logged with contextual information. This skill provides specific patterns to guarantee errors are captured for debugging instead of being swallowed.

Implementing custom error classes and result types in TypeScript involves creating specialized Error subclasses and structured return objects. This skill uses code examples to guide developers in applying these robust error management strategies.

You can use this error handling approach for both JavaScript and TypeScript codebases. The skill resolves common error handling deficiencies across both languages, addressing floating promises, silent catches, and non-Error object throws.