react

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

Files

Sebastian Markbåge 0825d019be [DevTools] Prefer I/O stack and show await stack after only if it's a different owner (#34101 )

Stacked on #34094.

This shows the I/O stack if available. If it's not available or if it
has a different owner (like if it was passed in) then we show the
`"awaited at:"` stack below it so you can see where it started and where
it was awaited. If it's the same owner this tends to be unnecessary
noise. We could maybe be smarter if the stacks are very different then
you might want to show both even with the same owner.

<img width="517" height="478" alt="Screenshot 2025-08-04 at 11 57 28 AM"
src="https://github.com/user-attachments/assets/2dbfbed4-4671-4a5f-8e6e-ebec6fe8a1b7"
/>

Additionally, this adds an inferred await if there's no owner and no
stack for the await. The inferred await of a function/class component is
just the owner. No stack. Because the stack trace would be the return
value. This will also be the case if you use throw-a-Promise. The
inferred await in the child position of a built-in is the JSX location
of that await like if you pass a promise to a child. This inference
already happens when you pass a Promise from RSC so in this case it
already has an await - so this is mainly for client promises.

2025-08-06 11:21:01 -04:00

src

[DevTools] Prefer I/O stack and show await stack after only if it's a different owner (#34101 )

2025-08-06 11:21:01 -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 )