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
We need to instrument the client router of RR, since the browserTracingIntegration is only creating navigation spans by listening on popstate changes – which is way too late for our server instrumentation to make sense.
Current state with browserTracingIntegration:
React Router in framework mode uses a HydratedRouter on the client.
This ticket is about finding out if we can reuse parts of our existing RR client-side instrumentation for this router and handle navigation timing correctly.
The text was updated successfully, but these errors were encountered:
Description
We need to instrument the client router of RR, since the browserTracingIntegration is only creating navigation spans by listening on popstate changes – which is way too late for our server instrumentation to make sense.
Current state with
browserTracingIntegration
:React Router in framework mode uses a
HydratedRouter
on the client.This ticket is about finding out if we can reuse parts of our existing RR client-side instrumentation for this router and handle navigation timing correctly.
The text was updated successfully, but these errors were encountered: