The hook returns a stable function that returns whether the component is currently mounted. Storing the flag in a ref keeps reads cheap and avoids triggering re-renders. The cleanup callback in useEffect is what flips the flag false on unmount, and returning a function (not the ref directly) lets call sites read the latest value at the moment they need it. Use it as if (!isMounted()) return; inside async callbacks before calling any setter.

Sprinkling if (!isMounted()) return inside every async callback is repetitive. useSafeState wraps useState so the setter quietly no-ops after unmount, which keeps the call site identical to plain React state. This is the right tradeoff for fire-and-forget side effects (analytics, optimistic logging) where missing the final write is acceptable. For network requests where you actually want to cancel the work, prefer AbortController over silently dropping the result.

Sometimes you want to propagate the result back to a caller, but only if the component is still mounted. useSafeCallback resolves to undefined after unmount so downstream code can early-return. Storing fn in a ref keeps the wrapper referentially stable across renders, which avoids re-creating effects in dependent hooks. Pair this with React Query or SWR for production-grade fetching, but reach for it directly when the call lives outside any data-fetching library.