solid-core-lifecycle

SolidJS lifecycle management uses `onMount` for DOM access post-render and `onCleanup` for resource disposal. You register cleanup functions to run when a component unmounts or an effect is disposed, preventing memory leaks from lingering event listeners or subscriptions.

Accessing refs outside `onMount` is an anti-pattern because the DOM element is not yet rendered. SolidJS lifecycle management requires `onMount` to execute code after the component is added to the DOM, ensuring DOM manipulation and third-party library initialization target valid elements.

The best way to prevent memory leaks in SolidJS is registering cleanup logic within `onCleanup`. Attach event listeners and start intervals in `onMount`, then remove listeners and clear intervals inside `onCleanup` to ensure proper resource disposal when the component unmounts.

SolidJS effect lifecycle management runs cleanup functions within `createEffect` before re-execution or disposal. This ensures that previous effect resources are correctly disposed of, separating component cleanup from effect cleanup to maintain reactivity without leaking subscriptions.

Yes, AbortController is a best practice for managing subscriptions in SolidJS. You initialize the controller during component mounting and call `abort()` within `onCleanup` to simultaneously cancel fetch requests and subscriptions upon component unmounting or effect disposal.

You should use `onCleanup` in SolidJS whenever a component creates resources like event listeners, subscriptions, or intervals. It runs during component unmounting or effect disposal, serving as the primary mechanism to prevent memory leaks and ensure proper resource cleanup.