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

Files

T

History

Sebastian Markbåge 7513996f20 [DevTools] Unify by using ReactFunctionLocation type instead of Source (#33955 )

In RSC and other stacks now we use a lot of `ReactFunctionLocation` type
to represent the location of a function. I.e. the location of the
beginning of the function (the enclosing line/col) that is represented
by the "Source" of the function. This is also what the parent Component
Stacks represents.

As opposed to `ReactCallSite` which is what normal stack traces and
owner stacks represent. I.e. the line/column number of the callsite into
the next function.

We can start sharing more code by using the `ReactFunctionLocation` type
to represent the component source location and it also helps clarify
which ones are function locations and which ones are callsites as we
start adding more stack traces (e.g. for async debug info and owner
stack traces).

2025-07-22 10:53:08 -04:00

src

[DevTools] Unify by using ReactFunctionLocation type instead of Source (#33955 )

2025-07-22 10:53:08 -04:00

package.json

[DevTools] Check in frontend.d.ts for react-devtools-fusebox, include in build output (#28970 )

2024-05-03 17:32:41 +01:00

README.md

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

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

webpack.config.frontend.js

[mcp] Add MCP tool to print out the component tree of the currently open React App (#33305 )

2025-06-02 21:42:34 -07:00

README.md

react-native-fusebox

This package is private and not expected to become public anytime soon. Consider using react-devtools-inline or react-devtools-core.

What is Fusebox?

"Fusebox" is the internal codename for the new React Native debugger stack based on Chrome DevTools.