LowFile-scopeJavaScript / TypeScript Plug & play

Use Promise.allSettled for batch operations with partial failures

For many independent tasks, prefer Promise.allSettled and handle per-item results.

Why this matters

One failure should not mask other successes.

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

Avoid

await Promise.all(tasks.map(t=>t())) // one error cancels everything

Prefer

const results = await Promise.allSettled(tasks.map(t=>t())); const failed = results.filter(r=>r.status==='rejected');

Bad

await Promise.all([...])

Good

await Promise.allSettled([...])

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