npm @sentry/browser 5.16.0

latest releases: 7.116.0, 8.2.1, 8.2.0...
3 years ago

If you are a @sentry/apm and did manual instrumentation using hub.startSpan please be aware of the changes we did to the API. The recommended entry point for manual instrumentation now is Sentry.startTransaction and creating child Span by calling startChild on it. We have internal workarounds in place so the old code should still work but will be removed in the future. If you are only using the Tracing integration there is no need for action.

  • [core] feat: Send transactions in envelopes (#2553)
  • [core] fix: Send event timestamp (#2575)
  • [browser] feat: Allow for configuring TryCatch integration (#2601)
  • [browser] fix: Call wrapped RequestAnimationFrame with correct context (#2570)
  • [node] fix: Prevent reading the same source file multiple times (#2569)
  • [integrations] feat: Vue performance monitoring (#2571)
  • [apm] fix: Use proper type name for op (#2584)
  • [core] fix: sent_at for envelope headers to use same clock (#2597)
  • [apm] fix: Improve bundle size by moving span status to @sentry/apm (#2589)
  • [apm] feat: No longer discard transactions instead mark them deadline exceeded (#2588)
  • [apm] feat: Introduce Sentry.startTransaction and Transaction.startChild (#2600)
  • [apm] feat: Transactions no longer go through beforeSend (#2600)
  • [browser] fix: Emit Sentry Request breadcrumbs from inside the client (#2615)
  • [apm] fix: No longer debounce IdleTransaction (#2618)
  • [apm] feat: Add pageload transaction option + fixes (#2623)
  • [minimal/core] feat: Allow for explicit scope through 2nd argument to captureException/captureMessage (#2627)

Don't miss a new browser release

NewReleases is sending notifications on new releases.