This is a cool approach, WeakRef + FinalizationRegistry is exactly the right tool for this since you can't force GC to test for leaks otherwise. Curious how it handles the classic case of an event listener attached in useEffect without a cleanup function keeping the whole component instance alive even after unmount, does leak-doctor catch that specific pattern or is it more about detecting already-detached nodes still referenced somewhere?
Tarun Sharma
React.js Frontend Web Developer | Next.js Specialist
This is a cool approach, WeakRef + FinalizationRegistry is exactly the right tool for this since you can't force GC to test for leaks otherwise. Curious how it handles the classic case of an event listener attached in useEffect without a cleanup function keeping the whole component instance alive even after unmount, does leak-doctor catch that specific pattern or is it more about detecting already-detached nodes still referenced somewhere?