fix(useTrackerSuspense): fix unmount error in StrictMode (dev only)

[welkinwong]

This commit addresses an issue where component unmounting in React StrictMode was causing errors to be thrown. The problem was isolated to development environments only, as StrictMode additional checks are not performed in production. The fix ensures proper cleanup during unmount lifecycle without triggering these development-only warnings.

[Grubba27]

Dang, you are on 🔥 !! very good job! I'll make a release with this change soon!

---

Somewhat related to these improvements, I know we somewhat handle the removal of items in the cacheMap, one thing I think we could explore (and if you think it makes sense) is to use WeakMap instead of Map? What do you think? I can make an issue explaining the reasoning

[Grubba27]

Published [email protected]

[welkinwong]

Somewhat related to these improvements, I know we somewhat handle the removal of items in the cacheMap, one thing I think we could explore (and if you think it makes sense) is to use WeakMap instead of Map? What do you think? I can make an issue explaining the reasoning

@Grubba27 I'm really sorry 🙏, I didn't notice this passage earlier.

Based on my current understanding, WeakMap is equivalent to a manually managed Map, with the major advantage of not having to worry about memory leaks, but the drawback is that primitive values can't be used and objects must be references.

One thing I can think of is that it could eliminate the key for suspense/useTracker (by holding the reactiveFn, but this requires that reactiveFn is wrapped with useCallback or similar). I had previously considered whether we could use reactiveFn.toString() as the key for the map.

We can continue discussing future improvements in the issue : )