fix(useTrackerSuspense): resolve unresponsiveness in StrictMode and on query/deps changes

[welkinwong]

Problem Description

This PR fixes two distinct unresponsiveness issues in the useTrackerSuspense hook:

1. Unresponsiveness to data changes in StrictMode (dev only) - In development environment with StrictMode enabled, components fail to respond properly when data changes
2. Unresponsiveness after query/dependencies changes - UI becomes unresponsive after query conditions change (for the no deps version) or dependencies change (for the with deps version)

Fixes Included

Commit 1: fix(useTrackerSuspense): fix unresponsiveness under StrictMode (dev only)

Resolved the issue where components don't respond to data changes in React StrictMode (dev only)

Commit 2: fix(useTrackerSuspense): fix unresponsiveness after query conditions change

Fixed the unresponsiveness that occurs after query conditions change (no deps version) or dependencies change (with deps version)

Testing & Verification

• Verified responsiveness to data changes in StrictMode environment
• Tested various query condition and dependency change scenarios to confirm issues are resolved
• Ensured existing functionality remains unaffected

Impact

• Only affects the behavior of useTrackerSuspense hook
• Provides better debugging experience in development StrictMode

[italojs]

Using the delete operator in V8 (the engine behind Node.js and Chrome) is generally not good for performance, especially in long-running or high-throughput applications.

When you use delete obj.key, V8 must change the object’s internal structure . This invalidates V8’s optimizations and forces the engine to fall back to slower property storage mechanisms .

Set it to undefined instead

refs:
https://phillcode.hashnode.dev/javascript-delete
https://alexanderobregon.substack.com/p/what-happens-when-you-delete-properties

Run this benchmark

[welkinwong]

👍 Okay, I'll make the changes here

[italojs]

Why settimeout(0) instead of processNextTick?

[welkinwong]

The code at line 149 is only called by the client. The server directly uses resolveAsync:

export const useTrackerSuspenseServer: typeof useTrackerSuspenseClient = (key, reactiveFn) => {
  return resolveAsync(key, Tracker.nonreactive(reactiveFn))
}