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
Add support for TanStack Router integration, an alternative to React Router.
Context
There is currently support for React Router v6 or v4/v5.x. TanStack Router is gaining popularity and it would be nice to be able to support users that use this newer router alternative.
The text was updated successfully, but these errors were encountered:
I'm integrating Faro into my React + TanStack Router app but am new to both Faro and the Grafana stack.
I’d like to understand the benefits of passing { router: ... } to new ReactIntegration(). What additional functionality does this provide compared to not passing it?
For creating a TanStack Router integration with Faro, I assume the goal is to allow Faro to extract useful information from the router when emitting events to the collector—does that sound right? What kind of information does Faro need, and what interface does it expect to interact with in order to extract this data?
Description
Add support for TanStack Router integration, an alternative to React Router.
Context
There is currently support for React Router v6 or v4/v5.x. TanStack Router is gaining popularity and it would be nice to be able to support users that use this newer router alternative.
The text was updated successfully, but these errors were encountered: