feat(tanstackstart-react): Trace server functions#18500
Merged
nicohrubec merged 20 commits intodevelopfrom Dec 17, 2025
Merged
Conversation
nicohrubec
commented
Dec 15, 2025
andreiborza
reviewed
Dec 16, 2025
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
andreiborza
reviewed
Dec 17, 2025
andreiborza
approved these changes
Dec 17, 2025
Member
andreiborza
left a comment
There was a problem hiding this comment.
LGTM overall, happy to go with this if you decide withSentry is the right api.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds tracing for tss server functions. To achieve this I added a new
wrapFetchWithSentrywrapper that can be used to instrument the tss server entry point:With this we get spans for server functions executed via
fetchcalls to the server. A limitation of this approach is that out-of-the-box this will only start a single span for the initial request made to the server. So for instance if a server function calls another server function, we will still only get a single span for the outer server function and users would need to wrap the inner call manually.Screenshot from my sample app with the current state:

Tests added:
Closes #18287