HighFile-scopeJavaScript / TypeScript Plug & play

Log errors instead of failing silently

Every catch block must log or report the error at least once before handling or rethrowing.

Why this matters

Guarantees minimum observability of failures.

Side-by-side examples engineers can pattern-match during review.

Avoid

catch(e){ return null }

Prefer

catch(e){ logger.warn('parse failed',{e}); return null }

Bad

catch(e){ /* noop */ }

Good

catch(e){ logger.error(e) }

From the same buckets as this rule.

Critical
Avoid equality operators in loop termination conditions
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.
error-handlingreadability-refactor
Critical
Avoid Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Avoid Using Boolean Expressions in `except` Statements
Detect `except` clauses that use `or` or `and` to catch multiple exceptions. This does not work as intended. Recommend using a tuple of exceptions instead.
error-handlingstack-python