HighFile-scopeJavaScript / TypeScript Plug & play

Clear timers on teardown/unmount

Whenever you start an interval/timeout, also define a deterministic cleanup path that clears it.

Why this matters

Prevents memory leaks and background work after scope end.

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

Avoid

setInterval(tick,1000);

Prefer

const id=setInterval(tick,1000); /* on teardown */ clearInterval(id);

Bad

setTimeout(t,500)

Good

const id=setTimeout(t,500); clearTimeout(id)

From the same buckets as this rule.

High
Add cleanup mechanisms for resource management
Ensure close/stop/dispose is called for resources (clients, channels, scopes) using use{} or try/finally; cancel coroutines on shutdown.
maintainabilityui-robustness
High
Add dispose methods to prevent memory leaks
Dispose controllers, focus nodes, animations, timers, and cancel subscriptions in `dispose()`.
stack-flutterui-robustness
High
Avoid array indexes as keys in React lists
Ensure that React list items do not use array indexes as keys. This practice can cause reordering issues and unexpected behavior. Recommend using unique identifiers instead.
performance-efficiencystack-react+1