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

Files

T

Josh Story 2a540194ad [Flight] do not emit error after abort (#30683 )

When synchronously aborting in a non-async Function Component if you
throw after aborting the task would error rather than abort because
React never observed the AbortSignal.

Using a sigil to throw after aborting during render isn't effective b/c
the user code itself could throw so insteead we just read the request
status. This is ok b/c we don't expect any tasks to still be pending
after the currently running task finishes.

However I found one instance where that wasn't true related to
serializing thenables which I've fixed so we may find other cases. If we
do, though it's almost certainly a bug in our task bookkeeping so we
should just fix it if it comes up.

I also updated `abort` to not set the status to ABORTING unless the
status was OPEN. we don't want to ever leave CLOSED or CLOSING status

2024-08-13 20:59:45 -07:00

esm

Don't minify symbols in production builds (#28881 )

2024-04-20 11:23:46 -04:00

npm

Don't minify symbols in production builds (#28881 )

2024-04-20 11:23:46 -04:00

src

[Flight] do not emit error after abort (#30683 )

2024-08-13 20:59:45 -07:00

client.browser.js

Split out Edge and Node implementations of the Flight Client (#26187 )