reactRouterTracingIntegration() is not a function

[gu-stav]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/react-router

SDK Version

9.22.0

Framework Version

7

Link to Sentry event

No response

Reproduction Example/SDK Setup

To setup tracing with react-router@7 the docs suggest to use https://docs.sentry.io/platforms/javascript/guides/react-router/tracing/ server-side (and browserTracingIntegration() client-side).

import * as Sentry from "@sentry/react-router";

Sentry.init({
  integrations: [Sentry.reactRouterTracingIntegration()],
});

I can see types being exported, but no function:

__vite_ssr_import_0__.reactRouterTracingIntegration is not a function

Steps to Reproduce

1. Setup react-router with vite@7
2. Setup tracing according to the documentation
3. See function not being exported

Expected Result

I expect to be able to call Sentry.reactRouterTracingIntegration() or an equivalent.

Actual Result

The function can not be called, because it is not exported.

[chargome]

Hey @gu-stav thanks for reaching out!

So the page you are referring to is talking about client-side tracing, not the server.

To summarize how to set up tracing in react-router:

• In your client init call you need to add integrations: [Sentry.reactRouterTracingIntegration()] and set a tracesSampleRate
• In your server init call you just need to set a tracesSampleRate

I'll update the docs page to make this more clear, sorry for the confusion here!

[gu-stav]

@chargome Got, it thank you! Sorry for the confusion, but getting tracing setup was a very frustrating story for us.

In case you need input on the docs, feel free to ping me anytime. Thank you!

[chargome]

but getting tracing setup was a very frustrating story for us

I'm sorry this was the case! Were there any other hiccups than the confusion between client/server setup?