mirror of https://github.com/facebook/react.git synced 2025-11-01 09:12:30 +00:00

Files

T

Sebastian Markbåge cdfde3ae11 Always rethrow original error when we replay errors (#20425 )

We replay errors so you can break on paused exceptions. This is done in
the second pass so that the first pass can ignore suspense.

Originally this threw the original error. For suppression purposes
we copied the flag onto the original error.

https://github.com/facebook/react/blob/f1dc626b29b8bf0f14c75a8525e8650b7ea94a47/packages/react-reconciler/src/ReactFiberScheduler.old.js#L367-L369

During this refactor it changed to just throw the retried error:

https://github.com/facebook/react/pull/15151

We're not sure exactly why but it was likely just an optimization or
clean up.

So we can go back to throwing the original error. That helps in the case
where a memoized function is naively not rethrowing each time such as
in Node's module system.

Unfortunately this doesn't fix the problem fully.
Because invokeGuardedCallback captures the error and logs it to the browser.
So you still end up seeing the wrong message in the logs.

This just fixes so that the error boundary sees the first one.

2020-12-10 05:50:41 -08:00

public

using the wrong renderer's act() should warn (#15756 )

2019-05-29 22:56:04 +01:00

src

Always rethrow original error when we replay errors (#20425 )

2020-12-10 05:50:41 -08:00

.gitignore

act() - s / flushPassiveEffects / Scheduler.unstable_flushWithoutYielding (#15591 )

2019-05-16 17:12:36 +01:00

package.json

Update to Jest 25 (#18480 )