@sentry/node - npm Package Versions

8.0.0-beta.2

Important Changes

• feat(browser): Update propagationContext on spanEnd to keep trace consistent

To ensure consistency throughout a route's duration, we update the scope's propagation context when the initial page load or navigation span ends. This keeps span-specific attributes like the sampled decision and dynamic sampling context on the scope, even after the transaction has ended.

• fix(browser): Don't assume window.document is available (#11602)

We won't assume window.dodument is available in the browser SDKs anymore. This should prevent errors in environments where window.document is not available (such as web workers).

Other changes

• feat(core): Add server.address to browser http.client spans (#11634)
• feat(opentelemetry): Update OTEL packages & relax some version ranges (#11580)
• feat(deps): bump @opentelemetry/instrumentation-hapi from 0.34.0 to 0.36.0 (#11496)
• feat(deps): bump @opentelemetry/instrumentation-koa from 0.37.0 to 0.39.0 (#11495)
• feat(deps): bump @opentelemetry/instrumentation-pg from 0.38.0 to 0.40.0 (#11494)
• feat(nextjs): Skip OTEL root spans emitted by Next.js (#11623)
• feat(node): Collect Local Variables via a worker (#11586)
• fix(nextjs): Escape Next.js' OpenTelemetry instrumentation (#11625)
• fix(feedback): Fix timeout on feedback submission (#11619)
• fix(node): Allow use of NodeClient without calling init (#11585)
• fix(node): Ensure DSC is correctly set in envelope headers (#11628)

8.0.0-beta.1

This is the first beta release of Sentry JavaScript SDK v8. With this release, there are no more planned breaking changes for the v8 cycle.

Read the in-depth migration guide to find out how to address any breaking changes in your code. All deprecations from the v7 cycle, with the exception of getCurrentHub(), have been removed and can no longer be used in v8.

Version Support

The Sentry JavaScript SDK v8 now supports Node.js 14.8.0 or higher. This applies to @sentry/node and all of our node-based server-side sdks (@sentry/nextjs, @sentry/remix, etc.).

The browser SDKs now require ES2018+ compatible browsers. New minimum browser versions:

• Chrome 63
• Edge 79
• Safari/iOS Safari 12
• Firefox 58
• Opera 50
• Samsung Internet 8.2

For more details, please see the version support section in migration guide.

Package removal

The following packages will no longer be published

• @sentry/hub
• @sentry/tracing
• @sentry/integrations
• @sentry/serverless
• @sentry/replay

Important Changes since v8.0.0-alpha.9

• feat(browser): Create spans as children of root span by default (#10986)

Because execution context isolation in browser environments does not work reliably, we deciced to keep a flat span hierarchy by default in v8.

• feat(core): Deprecate addTracingExtensions (#11579)

Instead of calling Sentry.addTracingExtensions() if you want to use performance in a browser SDK without using browserTracingIntegration(), you should now call Sentry.registerSpanErrorInstrumentation().

• feat(core): Implement suppressTracing (#11468)

You can use the new suppressTracing API to ensure a given callback will not generate any spans:

return Sentry.suppressTracing(() => {
  // Ensure this fetch call does not generate a span
  return fetch('/my-url');
});

• feat: Rename ESM loader hooks to import and loader (#11498)

We renamed the loader hooks for better clarity:

8.0.0-alpha.8

This is a partially broken release and was superseded by version 8.0.0-alpha.9.

8.0.0-alpha.7

This is the seventh alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the in-depth migration guide to find out how to address any breaking changes in your code.

Important Changes

• feat(nextjs): Use OpenTelemetry for performance monitoring and tracing (#11016)

We now use OpenTelemetry under the hood to power performance monitoring and tracing in the Next.js SDK.

• feat(v8/gatsby): Update SDK initialization for gatsby (#11292)

In v8, you cannot initialize the SDK anymore via Gatsby plugin options. Instead, you have to configure the SDK in a sentry.config.js file.

We also removed the automatic initialization of browserTracingIntegration. You now have to add this integration yourself.

Removal/Refactoring of deprecated functionality

• feat(v8): Remove addGlobalEventProcessor (#11255)
• feat(v8): Remove deprecated span id fields (#11180)
• feat(v8): Remove makeMain export (#11278)
• feat(v8/core): Remove deprecated span.sampled (#11274)
• feat(v8/core): Remove getActiveTransaction (#11280)
• feat(v8/core): Remove spanMetadata field (#11271)
• feat(v8/ember): Remove deprecated StartTransactionFunction (#11270)
• feat(v8/replay): Remove deprecated replay options (#11268)
• feat(v8/svelte): Remove deprecated componentTrackingPreprocessor export (#11277)
• ref: Remove more usages of getCurrentHub in the codebase (#11281)
• ref(core): Remove scope.setSpan() and scope.getSpan() methods (#11051)
• ref(profiling-node): Remove usage of getCurrentHub (#11275)
• ref(v8): change integration.setupOnce signature (#11238)
• ref: remove node-experimental references (#11290)

Other Changes

• feat(feedback): Make "required" text for input elements configurable (#11152) (#11153)
• feat(feedback): Update user feedback screenshot and cropping to align with designs (#11227)
• feat(nextjs): Remove runtime and vercel tags (#11291)
• feat(node): Add scope to ANR events (#11256)
• feat(node): Do not include prismaIntegration by default (#11265)
• feat(node): Ensure tracePropagationTargets are respected (#11285)
• feat(node): Simplify SentrySpanProcessor (#11273)
• feat(profiling): Use OTEL powered node package (#11239)
• feat(utils): Allow text encoder/decoder polyfill from global SENTRY (#11283)
• fix(nextjs): Show misconfiguration warning (no instrumentation.ts) (#11266)
• fix(node): Add logs when node-fetch cannot be instrumented (#11289)
• fix(node): Skip capturing Hapi Boom error responses. (#11151)
• fix(node): Use suppressTracing to avoid capturing otel spans (#11288)
• fix(opentelemetry): Do not stomp span status when startSpan callback throws (#11170)

8.0.0-alpha.5

This is the fifth alpha release of Sentry JavaScript SDK v8, which includes a variety of breaking changes.

Read the in-depth migration guide to find out how to address any breaking changes in your code.

Important Changes

• feat(nextjs): Remove client.(server|client).config.ts functionality in favor of instrumentation.ts (#11059)
  • feat(nextjs): Bump minimum required Next.js version to 13.2.0 (#11097)

With version 8 of the SDK we will no longer support the use of sentry.server.config.ts and sentry.edge.config.ts files. Instead, please initialize the Sentry Next.js SDK for the serverside in a Next.js instrumentation hook. sentry.client.config.ts|js is still supported and encouraged for initializing the clientside SDK. Please see the Migration Guide for more details.

In addition, the Next.js SDK now requires a minimum Next.js version of 13.2.0.

• feat(v8/angular): Merge angular and angular-ivy packages and start Angular support at v14 (#11091)

The @sentry/angular-ivy package has been removed. The @sentry/angular package now supports Ivy by default and requires at least Angular 14. See the Migration Guide for more details.

Removal/Refactoring of deprecated functionality

• feat(aws-serverless): Remove deprecated rethrowAfterCapture option (#11126)
• feat(node): Remove deprecated/duplicate/unused definitions (#11120)
• feat(v8): Remove deprecated integration methods on client (#11134)
• feat(v8/browser): Remove class export for linked errors (#11129)
• feat(v8/browser): Remove deprecated wrap export (#11127)
• feat(v8/core): Remove deprecated client.setupIntegrations method (#11179)
• feat(v8/core): Remove deprecated integration classes (#11132)
• feat(v8/ember): Remove InitSentryForEmber export (#11202)
• feat(v8/nextjs): Remove usage of class integrations (#11182)
• feat(v8/replay): Delete deprecated types (#11177)
• feat(v8/utils): Remove deprecated util functions (#11143)
• ref(node): Remove class based export for local variable integration (#11128)

Other Changes

• feat(browser): Make fetch the default transport for offline (#11209)
• feat(core): Filter out noisy GoogleTag error by default (#11208)
• feat(deps): Bump @sentry/cli from 2.30.0 to 2.30.2 (#11168)
• feat(nextjs): Prefix webpack plugin log messages with runtime (#11173)
• feat(node-profiling): Output ESM and remove Sentry deps from output (#11135)
• feat(node): Allow Anr worker to be stopped and restarted (#11214)
• feat(node): Support tunnel option for ANR (#11163)
• feat(opentelemetry): Do not capture exceptions for timed events (#11221)
• feat(serverless): Add Node.js 20 to compatible runtimes (#11103)
• feat(sveltekit): Switch to Otel-based @sentry/node package (#11075)
• fix(attachments): Add missing view_hierarchy attachment type (#11197)
• fix(build): Ensure tree shaking works properly for ESM output (#11122)
• fix(feedback): Only allow screenshots in secure contexts (#11188)
• fix(feedback): Reduce force layout in screenshots (#11181)
• fix(feedback): Smoother cropping experience and better UI (#11165)
• fix(feedback): Fix screenshot black bars in Safari (#11233)
• fix(metrics): use correct statsd data category (#11184)
• fix(metrics): use web-vitals ttfb calculation (#11185)
• fix(node): Export initOpenTelemetry (#11158)
• fix(node): Clear ANR timer on stop (#11229)
• fix(node): Time zone handling for cron (#11225)
• fix(node): Use unique variable for ANR context transfer (#11161)
• fix(opentelemetry): Do not stomp span error status (#11169)
• fix(types): Fix incorrect sampled type on Transaction (#11115)