You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tanstack Start's server integration doesn't send to sentry #16985
I just took a look at your reproduction and you are definitely right to question this. The SDK is currently in Alpha state and mainly offers functionality for the client-side. Automatic error monitoring on the server-side is not yet included. I updated the docs and the tracking issue to make the current state more obvious.
I will close this as this is not a bug, but a feature that was not yet implemented. You can always capture errors manually with captureException. However, automatic error capturing requires the Nitro server to be instrumented.
If you call the functions manually it works, but automatic instrumentation (without you having to call the functions) for TanStack Start's current server setup is not yet implemented.
As TanStack Start is still on v0 and they plan to use Nitro on the server with v1, we want to optimize for their Nitro setup in v1.
Are you not seeing logs because you are running tanstack start on a serverless environment, like Cloudflare Workers? That would shut off the compute before sentry could flush
Activity
andreiborza commentedon Jul 15, 2025
Hi @nick-potts, thanks for filing this and providing a reproduction repo. We'll take a look.
s1gr1d commentedon Jul 16, 2025
I just took a look at your reproduction and you are definitely right to question this. The SDK is currently in Alpha state and mainly offers functionality for the client-side. Automatic error monitoring on the server-side is not yet included. I updated the docs and the tracking issue to make the current state more obvious.
I will close this as this is not a bug, but a feature that was not yet implemented. You can always capture errors manually with
captureException. However, automatic error capturing requires the Nitro server to be instrumented.nick-potts commentedon Jul 17, 2025
Thanks for the info, just to be clear - nothing works server side yet? No spans, errors, logs etc?
s1gr1d commentedon Jul 17, 2025
If you call the functions manually it works, but automatic instrumentation (without you having to call the functions) for TanStack Start's current server setup is not yet implemented.
As TanStack Start is still on v0 and they plan to use Nitro on the server with v1, we want to optimize for their Nitro setup in v1.
Bryson14 commentedon Apr 11, 2026
Are you not seeing logs because you are running tanstack start on a serverless environment, like Cloudflare Workers? That would shut off the compute before sentry could flush