@sentry-internal/replay-canvas - npm Package Versions

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)

8.0.0-alpha.4

This is the fourth Alpha release of the v8 cycle, 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: Set required node version to >=14.18.0 for all packages (#10968)

The minimum Node version required for the SDK is now 14.18.0.

• Serverless SDK Changes
  • feat(google-cloud): Add @sentry/google-cloud package (#10993)
  • feat(v8): Add @sentry/aws-serverless package (#11052)
  • feat(v8): Rename gcp package to @sentry/google-cloud-serverless (#11065)

@sentry/serverless is no longer published, and is replaced by two new packages: @sentry/google-cloud-serverless and @sentry/aws-serverless. These packages are now the recommended way to instrument serverless functions. See the migration guide for more details.

• build(bundles): Use ES2017 for bundles (drop ES5 support) (#10911)

The Browser SDK and CDN bundles now emits ES2017 compatible code and drops support for IE11. This also means that the Browser SDKs (@sentry/browser, @sentry/react, @sentry/vue, etc.) requires the fetch API to be available in the environment. If you need to support older browsers, please transpile your code to ES5 using babel or similar and add required polyfills.

New minimum supported browsers:

• Chrome 58
• Edge 15
• Safari/iOS Safari 11
• Firefox 54
• Opera 45
• Samsung Internet 7.2

Removal/Refactoring of deprecated functionality

• feat(browser): Remove IE parser from the default stack parsers (#11035)
• feat(bun/v8): Remove all deprecations from Bun SDK (#10971)
• feat(core): Remove startTransaction export (#11015)
• feat(v8/core): Move addTracingHeadersToFetchRequest and instrumentFetchRequest to core (#10918)
• feat(v8/deno): Remove deprecations from deno SDK (#10972)
• feat(v8/remix): Remove remixRouterInstrumentation (#10933)
• feat(v8/replay): Opt-in options for unmask and unblock (#11049)
• feat(v8/tracing): Delete BrowserTracing class (#10919)
• feat(v8/vercel-edge): Remove vercel-edge sdk deprecations (#10974)
• feat(replay/v8): Delete deprecated replaySession and errorSampleRates (#11045)
• feat(v8): Remove deprecated Replay, Feedback, ReplayCanvas exports (#10814)
• ref: Remove spanRecorder and all related code (#10977)
• ref: Remove deprecated origin field on span start options (#11058)
• ref: Remove deprecated properties from startSpan options (#11054)
• ref(core): Remove startTransaction & finishTransaction hooks (#11008)
• ref(nextjs): Remove sentry field in Next.js config as a means of configuration (#10839)
• ref(nextjs): Remove last internal deprecations (#11019)
• ref(react): Streamline browser tracing integrations & remove old code (#11012)
• ref(svelte): Remove startChild deprecations (#10956)
• ref(sveltekit): Update trace propagation & span options (#10838)
• ref(v8/angular): Remove instrumentAngularRouting and fix tests (#11021)

Other Changes

• feat: Ensure getRootSpan() does not rely on transaction (#10979)
• feat: Export getSpanDescendants() everywhere (#10924)
• feat: Make ESM output valid Node ESM (#10928)
• feat: Remove tags from spans & transactions (#10809)
• feat(angular): Update scope transactionName when route is resolved (#11043)
• feat(angular/v8): Change decorator naming and add name parameter (#11057)
• feat(astro): Update @sentry/astro to use OpenTelemetry (#10960)
• feat(browser): Remove HttpContext integration class (#10987)
• feat(browser): Use idle span for browser tracing (#10957)
• feat(build): Allow passing Sucrase options for rollup (#10747)
• feat(build): Core packages into single output files (#11030)
• feat(core): Allow custom tracing implementations (#11003)
• feat(core): Allow metrics aggregator per client (#10949)
• feat(core): Decouple scope.transactionName from root spans (#10991)
• feat(core): Ensure trace APIs always return a span (#10942)
• feat(core): Implement startIdleSpan (#10934)
• feat(core): Move globals to __SENTRY__ singleton (#11034)
• feat(core): Move more scope globals to __SENTRY__ (#11074)
• feat(core): Undeprecate setTransactionName (#10966)
• feat(core): Update continueTrace to be callback-only (#11044)
• feat(core): Update spanToJSON to handle OTEL spans (#10922)
• feat(deps): bump @sentry/cli from 2.29.1 to 2.30.0 (#11024)
• feat(feedback): New feedback integration with screenshots (#10590)
• feat(nextjs): Bump Webpack Plugin to version 2 and rework config options (#10978)
• feat(nextjs): Support Hybrid Cloud DSNs with tunnelRoute option (#10959)
• feat(node): Add setupFastifyErrorHandler utility (#11061)
• feat(node): Rephrase wording in http integration JSDoc (#10947)
• feat(opentelemetry): Do not use SentrySpan & Transaction classes (#10982)
• feat(opentelemetry): Remove hub from context (#10983)
• feat(opentelemetry): Use core getRootSpan functionality (#11004)
• feat(profiling-node): Refactor deprecated methods & non-hook variant (#10984)
• feat(react): Update scope's transactionName in React Router instrumentations (#11048)
• feat(remix): Refactor to use new performance APIs (#10980)
• feat(remix): Update remix SDK to be OTEL-powered (#11031)
• feat(sveltekit): Export unstable_sentryVitePluginOptions for full Vite plugin customization (#10930)
• feat(v8/bun): Update @sentry/bun to use OTEL node (#10997)
• fix(ember): Ensure browser tracing is correctly lazy loaded (#11026)
• fix(nextjs): Use passthrough createReduxEnhancer on server (#11005)
• fix(node): Add missing core re-exports (#10931)
• fix(node): Correct SDK name (#10961)
• fix(node): Do not assert in vendored proxy code (#11011)
• fix(node): Export spotlightIntegration from OTEL node (#10973)
• fix(node): support undici headers as strings or arrays (#10938)
• fix(opentelemetry): Fix span & sampling propagation (#11092)
• fix(react): Passes the fallback function through React's createElement function (#10623)
• fix(react): Set handled value in ErrorBoundary depending on fallback (#10989)
• fix(types): Add addScopeListener to Scope interface (#10952)
• fix(types): Add AttachmentType and use for envelope attachment_type property (#10946)
• fix(types): Remove usage of allowSyntheticDefaultImports (#11073)
• fix(v8/utils): Stack parser skip frames (not lines of stack string) (#10560)
• ref(angular): Refactor usage of startChild (#11056)
• ref(browser): Store browser metrics as attributes instead of tags (#10823)
• ref(browser): Update scope.transactionName on pageload and navigation span creation (#10992)
• ref(browser): Update browser metrics to avoid deprecations (#10943)
• ref(browser): Update browser profiling to avoid deprecated APIs (#11007)
• ref(feedback): Move UserFeedback type into feedback.ts (#11032)
• ref(nextjs): Clean up browser tracing integration (#11022)
• ref(node-experimental): Refactor usage of startChild() (#11047)
• ref(node): Use new performance APIs in legacy http & undici (#11055)
• ref(opentelemetry): Remove parent span map (#11014)
• ref(opentelemetry): Remove span metadata handling (#11020)

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

8.0.0-alpha.3

This alpha was released in an incomplete state. We recommend skipping this release and using the 8.0.0-alpha.4 release instead.