Error in question:
> Uncaught Error: This Suspense boundary received an update before it finished hydrating. This caused the boundary to switch to client rendering. The usual way to fix this is to wrap the original update in startTransition.

The current error gives no indication which part of the code causes the error, making it very hard to debug. 

Two suggestions / questions:

**Indicate which suspense boundary**
Is there any way to indicate _which_ suspense boundary received an update? Showing the component tree like in other errors would be a very helpful first step. 

**Indicate which update**
Even better of course would be if there could be any indication which update was triggered, with a call stack. 




C
       i
      
       I
       p
       t
      
       W
       l
      const slotIndex = workInProgress.index;
      const numberOfForks = getForksAtLevel(workInProgress);
      pushTreeId(workInProgress, numberOfForks, slotIndex);
    }
  }
   Before entering the begin phase, clear pending update priority.
   TODO: This assumes that we're about to evaluate the component and process
   the update queue. However, there's an exception: SimpleMemoComponent
   sometimes bs out later in the begin phase. This indicates that we should
   move this assignment out of the common path and into each branch.
  workInProgress.lanes = NoLanes;
  switch (workInProgress.tag) {
    case IndeterminateComponent: {
      return mountIndeterminateComponent(
        current,
        workInProgress,
        workInProgress.type,
        renderLanes,
      );
    }
    case LazyComponent: {