@sentry/hub - npm Package Versions

published 7.105.0 • 2 months ago

Changelog

7.105.0

Important Changes

feat: Ensure withActiveSpan is exported everywhere (#10877)

You can use the withActiveSpan method to ensure a certain span is the active span in a given callback. This can be used to create a span as a child of a specific span with the startSpan API methods:

const parentSpan = Sentry.startInactiveSpan({ name: 'parent' });
if (parentSpan) {
  withActiveSpan(parentSpan, () => {
    // This will be a direct child of parentSpan
    const childSpan = Sentry.startInactiveSpan({ name: 'child' });
  });
}

7.104.0

published 7.104.0 • 2 months ago

Changelog

7.104.0

Important Changes

feat(performance): create Interaction standalone spans on inp events (#10709)

This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support is released with the upcoming 24.3.0 release of self-hosted.

To opt-in to this feature, you can use the enableInp option in the browserTracingIntegration:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      enableInp: true,
    });
  ]
})

Other Changes

feat(feedback): Flush replays when feedback form opens (#10567)
feat(profiling-node): Expose nodeProfilingIntegration (#10864)
fix(profiling-node): Fix dependencies to point to current versions (#10861)
fix(replay): Add errorHandler for replayCanvas integration (#10796)

7.103.0

published 7.103.0 • 2 months ago

Changelog

7.103.0

Important Changes

feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)

7.102.1

published 7.102.1 • 3 months ago

Changelog

7.102.1

fix(performance): Fixes latest route name and source for interactions not updating properly on navigation (#10702)
fix(tracing): Guard against missing window.location (#10659)
ref: Make span types more robust (#10660)
ref(remix): Make @remix-run/router a dependency (v7) (#10779)

7.102.0

published 7.102.0 • 3 months ago

Changelog

7.102.0

fix: Export session API (#10712)
fix(core): Fix scope capturing via captureContext function (#10737)

7.101.1

published 7.101.1 • 3 months ago

Changelog

7.101.1

In version 7.101.0 the @sentry/hub package was missing due to a publishing issue. This release contains the package again.

fix(nextjs): Remove webpack:// prefix more broadly from source map sources field (#10641)

7.100.1

published 7.100.1 • 3 months ago

Changelog

7.100.1

This release contains build fixes for profiling-node.

build(profiling-node): make sure debug build plugin is used #10534
build: Only run profiling e2e test if bindings have changed #10542
fix(feedback): Replay breadcrumb for feedback events was incorrect #10536

7.100.0

published 7.100.0 • 3 months ago

Changelog