Commits on May 3, 2022

1. Do not replay erroring beginWork with invokeGuardedCallback when susp… …

   …ended or previously errored
   
   When hydrating a suspense boundary an error or a suspending fiber can often lead to a cascade of hydration errors. While in many cases these errors are simply discarded (e.g. when teh root does not commit and we fall back to client rendering) the use of invokeGuardedCallback can lead to many of these errors appearing as uncaught in the browser console. This change avoids error replaying using invokeGuardedCallback when we are hydrating a suspense boundary and have either already suspended or we have one previous error which was replayed.

   

   gnoff committed May 3, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for 710429e
   • Browse repository at this point

   Copy the full SHA

   710429e View commit details

   Browse the repository at this point in the history