Skip to content

[pull] main from facebook:main #188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 22, 2025
Merged

[pull] main from facebook:main #188

merged 1 commit into from
Jul 22, 2025

Conversation

pull[bot]
Copy link

@pull pull bot commented Jul 22, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

#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).
@pull pull bot locked and limited conversation to collaborators Jul 22, 2025
@pull pull bot added the ⤵️ pull label Jul 22, 2025
@pull pull bot merged commit 7513996 into code:main Jul 22, 2025
1 of 13 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant