Skip to content

Update dependency @grafana/faro-react to v2

sys-0403-p-rundeck requested to merge renovate-major-faro-web-sdk-monorepo into master

This MR contains the following updates:

Package Change Age Confidence
@grafana/faro-react (source) ^1.19.0 → ^2.0.0 age confidence

Release Notes

grafana/faro-web-sdk (@​grafana/faro-react)

v2.1.0

Compare Source

  • Feature (@grafana/faro-react): support for React 19 and React Router 7

  • Fix (@grafana/faro-web-sdk): CSP violation events now correctly capture all SecurityPolicyViolationEvent attributes. Previously, properties like blockedURI, documentURI, and others were missing because native browser event properties are getters on the prototype chain, not own enumerable properties (#​1491)

  • Fix (@grafana/faro-web-sdk): circular dependency between events and userActions APIs (#​1793)

v2.0.2

Compare Source

  • Breaking (@grafana/faro-web-sdk): User action events now have a standardized event name (faro.user.action), with the specific user action name moved to a parameter for improved consistency and filtering capabilities. Migration note: If you previously filtered user action events by event name, update your queries to use the new event name (faro.user.action) and filter by the userActionName attribute for the specific action.

  • Breaking (@grafana/faro-web-sdk): Web vitals now always tracks attribution data. The trackWebVitalsAttribution and webVitalsInstrumentation.trackAttribution configuration flags have been removed. Attribution data is now collected by default and cannot be disabled. Migration note: If you were using trackWebVitalsAttribution: false or webVitalsInstrumentation: { trackAttribution: false } to disable attribution, remove these options from your configuration. Attribution data will now always be included in web vitals measurements.

  • Breaking (@grafana/faro-web-sdk): Removed the trackUserActionsPreview option from Faro configuration. User actions instrumentation is now always enabled by default (#​1772). Migration note: If you previously used trackUserActionsPreview: true or left it unset, simply remove this option - no further action is required. If you had set trackUserActionsPreview: false to disable user actions tracking, you now need to exclude the UserActionInstrumentation from your instrumentations array manually.

  • Feature (@grafana/faro-web-sdk) [experimental]: Added navigation instrumentation to track soft navigations (same-document navigations). The instrumentation monitors URL changes, DOM mutations, HTTP requests, and user interactions to automatically detect and report navigation events with details including fromUrl, toUrl, and duration. Enable by setting experimental.trackNavigation: true in the configuration.

  • Fix (@grafana/faro-web-sdk): Fixed an issue where custom severity and custom trigger properties were not being included in user action attributes (#​1551)

  • Fix (@grafana/faro-web-sdk): Fixed an error when initializeFaro is called without any window object present (#​1643)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited by sys-0403-p-rundeck

Merge request reports