js/listener-cleanup

Dlaczego

In a single-page app, a view that adds a resize listener, a setInterval or an IntersectionObserver and never removes it keeps running after navigation: memory grows, handlers fire twice after the view comes back, and they act on elements that no longer exist.

Poprawka

Create one AbortController per view or component, pass { signal } to every addEventListener and to fetch, and call abort() on teardown (the effect cleanup, onUnmounted, disconnectedCallback, DestroyRef.onDestroy). Clear timers with clearInterval and call disconnect() on observers in the same place.

Przykłady

// bad
connectedCallback() { window.addEventListener('resize', this.layout) }
// good
connectedCallback() {
  this.controller = new AbortController()
  window.addEventListener('resize', this.layout, { signal: this.controller.signal })
}
disconnectedCallback() { this.controller.abort() }

Źródła

• MDN, EventTarget.addEventListener() (the signal option)
• MDN, AbortController

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain js/listener-cleanup