@sentry/hub - npm Package Versions

published 7.109.0 • 3 months ago

Changelog

7.109.0

This release deprecates some exports from the @sentry/replay package. These exports have been moved to the browser SDK (or related framework SDKs like @sentry/react).

feat(feedback): Make "required" text for input elements configurable (#11287)
feat(node): Add scope to ANR events (#11267)
feat(replay): Bump rrweb to 2.12.0 (#11317)
fix(node): Local variables skipped after Promise (#11248)
fix(node): Skip capturing Hapi Boom error responses (#11324)
fix(web-vitals): Check for undefined navigation entry (#11312)
ref(replay): Deprecate @sentry/replay exports (#11242)

Work in this release contributed by @soerface. Thank you for your contribution!

7.108.0

published 7.108.0 • 3 months ago

Changelog

7.108.0

This release fixes issues with Time to First Byte (TTFB) calculation in the SDK that was introduced with 7.95.0. It also fixes some bugs with Interaction to First Paint (INP) instrumentation. This may impact your Sentry Performance Score calculation.

feat(serverless): Add Node.js 20 to compatible runtimes (#11104)
feat(core): Backport ResizeObserver and googletag default filters (#11210)
feat(webvitals): Adds event entry names for INP handler. Also guard against empty metric value
fix(metrics): use correct statsd data category (#11187)
fix(node): Record local variables with falsy values (v7) (#11190)
fix(node): Use unique variable for ANR context transfer (v7) (#11162)
fix(node): Time zone handling for cron (#11225)
fix(tracing): use web-vitals ttfb calculation (#11231)
fix(types): Fix incorrect sampled type on Transaction (#11146)
fix(webvitals): Fix mapping not being maintained properly and sometimes not sending INP spans (#11183)

Work in this release contributed by @quisido and @joshkel. Thank you for your contributions!

7.107.0

published 7.107.0 • 3 months ago

Changelog

7.107.0

This release fixes issues with INP instrumentation with the Next.js SDK and adds support for the enableInp option in the deprecated BrowserTracing integration for backwards compatibility.

feat(performance): Port INP span instrumentation to old browser tracing (#11085)
fix(ember): Ensure browser tracing is correctly lazy loaded (#11027)
fix(node): Do not assert in vendored proxy code (v7 backport) (#11009)
fix(react): Set handled value in ErrorBoundary depending on fallback [v7] (#11037)

7.106.1

published 7.106.1 • 3 months ago

Changelog

7.106.1

fix(nextjs/v7): Use passthrough createReduxEnhancer on server (#11010)

7.106.0

published 7.106.0 • 3 months ago

Changelog

7.106.0

feat(nextjs): Support Hybrid Cloud DSNs with tunnelRoute option (#10958)
feat(remix): Add Vite dev-mode support to Express instrumentation (#10811)
fix(core): Undeprecate setTransactionName
fix(browser): Don't use chrome variable name (#10874)
fix(nextjs): Client code should not use Node global (#10925)
fix(node): support undici headers as strings or arrays (#10938)
fix(types): Add AttachmentType and use for envelope attachment_type property (#10946)
ref(ember): Avoid namespace import to hopefully resolve minification issue (#10885)
chore(sveltekit): Fix punctuation in a console.log (#10895)

Work in this release contributed by @jessezhang91 and @bfontaine. Thank you for your contributions!

7.105.0

published 7.105.0 • 3 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 • 4 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 • 4 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 • 4 months ago

Changelog