Rules overview

eslint-plugin-runtime-cleanup rules target runtime resource lifetimes that are easy to leak when allocation and teardown drift apart.

Stable rules

• no-floating-timers requires timer handles to be retained so they can be cleared during cleanup.
• no-unmanaged-event-listeners requires event listeners to use an AbortSignal option or a matching removeEventListener cleanup call.
• no-floating-observers requires native observer instances to be retained so they can be disconnected during cleanup.
• no-floating-workers requires worker handles to be retained so they can be terminated during cleanup.
• no-floating-child-processes requires child process handles to be retained so they can be killed during cleanup.

Future rules should continue to target explicit runtime resource lifetimes, including timers, listeners, observers, abort controllers, workers, streams, child processes, and disposable handles.

Rule authoring expectations

Runtime cleanup rules should be conservative:

• report only resource allocation patterns with a clear cleanup obligation
• avoid whole-file heuristics that create noisy false positives
• use type information only when it materially improves precision
• prefer suggestions over autofixes when cleanup placement is ambiguous
• document the exact lifecycle pattern the rule expects

Presets

The preset pages describe the exported config keys and are ready for future rules:

• minimal
• recommended
• recommended-type-checked
• strict
• all
• experimental