error-handling

Fix floating promises by awaiting them, casting to void with a catch block, or assigning them for later handling. This resolves @typescript-eslint/no-floating-promises errors by ensuring all async operations are properly tracked.

Empty catch blocks hide errors and reduce application visibility. Replace silent catches with proper logging, context addition, or rethrowing to preserve error details and maintain debugging visibility.

Throwing non-Error values like strings or plain objects loses stack traces and breaks error handling. Enforce throwing Error objects or custom error classes to preserve stack traces and enable robust debugging.

Resolve no-floating-promises by ensuring async operations are awaited, explicitly cast to void with a catch, or assigned. This Skill applies static analysis patterns to detect and fix unhandled promise rejections.

Yes, this applies to JavaScript and TypeScript projects across backend and frontend, covering async operations, promises, and exception handling in API route handlers and long-running background tasks.

Handle promise chain errors by replacing silent catches with logging or rethrowing, ensuring promises are awaited, and throwing Error objects to maintain stack traces for robust exception management.