angular-destroyref

To prevent memory leaks in Angular components and services, use the DestroyRef API and takeUntilDestroyed operator to automatically unsubscribe observables and ensure deterministic teardown of resources during the component lifecycle.

Migrating from ngOnDestroy and Subject-based cleanup to takeUntilDestroyed involves injecting DestroyRef into your component or service, then applying the takeUntilDestroyed operator within your RxJS pipeline to handle automatic subscription teardown without manual lifecycle hooks.

The best way to automatically unsubscribe RxJS observables in Angular 16+ is using the DestroyRef API combined with the takeUntilDestroyed operator from @angular/core/rxjs-interop, which provides deterministic teardown for subscription lifecycles.

DestroyRef works for cleaning up resources in both Angular components and services, allowing you to inject it wherever needed and manage observable teardown and resource destruction without relying solely on the component ngOnDestroy lifecycle hook.

Manual Subject cleanup causes memory leaks in Angular when teardown logic is incomplete or improperly triggered, making the deterministic DestroyRef pattern a safer approach for managing subscription lifecycles and preventing unpredictable behavior.