mirror of https://github.com/facebook/react.git synced 2026-02-24 04:33:04 +00:00

Files

Sebastian Markbåge 9cc74fec74 [Flight] Emit the time we awaited something inside a Server Component (#33402 )

Stacked on #33400. 

<img width="1261" alt="Screenshot 2025-06-01 at 10 27 47 PM"
src="https://github.com/user-attachments/assets/a5a73ee2-49e0-4851-84ac-e0df6032efb5"
/>

This is emitted with the start/end time and stack of the "await". Which
may be different than the thing that started the I/O.

These awaits aren't quite as simple as just every await since you can
start a sequence in parallel there can actually be multiple overlapping
awaits and there can be CPU work interleaved with the await on the same
component.

```js
function getData() {
  await fetch(...);
  await fetch(...);
}
const promise = getData();
doWork();
await promise;
```

This has two "I/O" awaits but those are actually happening in parallel
with `doWork()`.

Since these also could have started before we started rendering this
sequence (e.g. a component) we have to clamp it so that we don't
consider awaits that start before the component.

What we're conceptually trying to convey is the time this component was
blocked due to that I/O resource. Whether it's blocked from completing
the last result or if it's blocked from issuing a waterfall request.

2025-06-03 17:29:41 -04:00

npm

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

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

src

[Flight] Emit the time we awaited something inside a Server Component (#33402 )

2025-06-03 17:29:41 -04:00

flight.js

Remove Flight Relay DOM/Native (#26828 )

2023-05-17 20:33:25 -04:00

package.json

Remove loose-envify dep and browserify configs (#28480 )