react

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

Files

Sebastian Markbåge 2ba7b07ce1 [DevTools] Compute a min and max range for the currently selected suspense boundary (#34201 )

This computes a min and max range for the whole suspense boundary even
when selecting a single component so that each component in a boundary
has a consistent range.

The start of this range is the earliest start of I/O in that boundary or
the end of the previous suspense boundary, whatever is earlier. If the
end of the previous boundary would make the range large, then we cap it
since it's likely that the other boundary was just an independent
render.

The end of the range is the latest end of I/O in that boundary. If this
is smaller than the end of the previous boundary plus the 300ms
throttle, then we extend the end. This visualizes what throttling could
potentially do if the previous boundary committed right at its end. Ofc,
it might not have committed exactly at that time in this render. So this
is just showing a potential throttle that could happen. To see actual
throttle, you look in the Performance Track.

<img width="661" height="353" alt="Screenshot 2025-08-14 at 12 41 43 AM"
src="https://github.com/user-attachments/assets/b0155e5e-a83f-400c-a6b9-5c38a9d8a34f"
/>

We could come up with some annotation to highlight that this is eligible
to be throttled in this case. If the lines don't extend to the edge,
then it's likely it was throttled.

2025-08-15 13:34:07 -04:00

src

[DevTools] Compute a min and max range for the currently selected suspense boundary (#34201 )

2025-08-15 13:34:07 -04:00

babel.config.js

feat[react-devtools]: support Manifest v3 for Firefox extension (#30824 )

2024-08-29 11:28:35 +01:00

buildUtils.js

feat[devtools]: add package for fusebox integration (#28553 )

2024-04-12 15:29:35 +01:00

package.json

[devtools] upgrade json5 (#33358 )