@sentry/react - npm Package Versions

published 8.31.0-beta.0 • 2 months ago

8.31.0

published 8.31.0 • 2 months ago

Changelog

8.31.0

Important Changes

feat(node): Add dataloader integration (#13664)

This release adds a new integration for the dataloader package. The Node SDK (and all SDKs that depend on it) will now automatically instrument dataloader instances. You can also add it manually:

Sentry.init({
  integrations: [Sentry.dataloaderIntegration()],
});

Other Changes

feat(browser): Add navigation activationStart timestamp to pageload span (#13658)
feat(gatsby): Add optional deleteSourcemapsAfterUpload (#13610)
feat(nextjs): Give app router prefetch requests a http.server.prefetch op (#13600)
feat(nextjs): Improve Next.js serverside span data quality (#13652)
feat(node): Add disableInstrumentationWarnings option (#13693)
feat(nuxt): Adding experimental_basicServerTracing option to Nuxt module (#13643)
feat(nuxt): Improve logs about adding Node option 'import' (#13726)
feat(replay): Add onError callback + other small improvements to debugging (#13721)
feat(replay): Add experimental option to allow for a checkout every 6 minutes (#13069)
feat(wasm): Unconditionally parse instruction addresses (#13655)
fix: Ensure all logs are wrapped with consoleSandbox (#13690)
fix(browser): Try multiple options for lazyLoadIntegration script parent element lookup (#13717)
fix(feedback): Actor color applies to feedback icon (#13702)
fix(feedback): Fix form width on mobile devices (#13068)
fix(nestjs): Preserve original function name on SentryTraced functions (#13684)
fix(node): Don't overwrite local variables for re-thrown errors (#13644)
fix(normalize): Treat Infinity as NaN both are non-serializable numbers (#13406)
fix(nuxt): Use correct server output file path (#13725)
fix(opentelemetry): Always use active span in Propagator.inject (#13381)
fix(replay): Fixes potential out-of-order segments (#13609)

Work in this release was contributed by @KyGuy2002, @artzhookov, and @julianCast. Thank you for your contributions!

8.30.0

published 8.30.0 • 3 months ago

Changelog

8.30.0

Important Changes

feat(node): Add kafkajs integration (#13528)

This release adds a new integration that instruments kafkajs library with spans and traces. This integration is automatically enabled by default, but can be included with the Sentry.kafkaIntegration() import.

Sentry.init({
  integrations: [Sentry.kafkaIntegration()],
});

Other Changes

feat(core): Allow adding measurements without global client (#13612)
feat(deps): Bump @opentelemetry/instrumentation-undici from 0.5.0 to 0.6.0 (#13622)
feat(deps): Bump @sentry/cli from 2.33.0 to 2.35.0 (#13624)
feat(node): Use @opentelemetry/instrumentation-undici for fetch tracing (#13485)
feat(nuxt): Add server config to root folder (#13583)
feat(otel): Upgrade @opentelemetry/semantic-conventions to 1.26.0 (#13631)
fix(browser): check supportedEntryTypes before caling the function (#13541)
fix(browser): Ensure Standalone CLS span timestamps are correct (#13649)
fix(nextjs): Widen removal of 404 transactions (#13628)
fix(node): Remove ambiguity and race conditions when matching local variables to exceptions (#13501)
fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#13640)
fix(node): Update OpenTelemetry instrumentation package for solidstart and opentelemetry (#13642)
fix(vue): Ensure Vue trackComponents list matches components with or without <> (#13543)
ref(profiling): Conditionally shim cjs globals (#13267)

Work in this release was contributed by @Zen-cronic and @odanado. Thank you for your contributions!

8.29.0

published 8.29.0 • 3 months ago

Changelog

8.29.0

Important Changes

Beta releases of official Solid and SolidStart Sentry SDKs

This release marks the beta releases of the @sentry/solid and @sentry/solidstart Sentry SDKs. For details on how to use them, check out the Sentry Solid SDK README and the Sentry SolidStart SDK README respectively. Please reach out on GitHub if you have any feedback or concerns.

feat(node): Option to only wrap instrumented modules (#13139)

Adds the SDK option to only wrap ES modules with import-in-the-middle that specifically need to be instrumented.

import * as Sentry from '@sentry/node';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  registerEsmLoaderHooks: { onlyIncludeInstrumentedModules: true },
});

feat(node): Update OpenTelemetry packages to instrumentation v0.53.0 (#13587)

All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8 and fixes various bugs related to ESM mode.

Other Changes

feat(nextjs): Emit warning when using turbopack (#13566)
feat(nextjs): Future-proof Next.js config options overriding (#13586)
feat(node): Add generic-pool integration (#13465)
feat(nuxt): Upload sourcemaps generated by Nitro (#13382)
feat(solidstart): Add browserTracingIntegration by default (#13561)
feat(solidstart): Add sentrySolidStartVite plugin to simplify source maps upload (#13493)
feat(vue): Only start UI spans if parent is available (#13568)
fix(cloudflare): Guard context.waitUntil call in request handler (#13549)
fix(gatsby): Fix assets path for sourcemaps upload (#13592)
fix(nextjs): Use posix paths for sourcemap uploads (#13603)
fix(node-fetch): Use stringified origin url (#13581)
fix(node): Replace dashes in generic-pool span origins with underscores (#13579)
fix(replay): Fix types in WebVitalData (#13573)
fix(replay): Improve replay web vital types (#13602)
fix(utils): Keep logger on carrier (#13570)

Work in this release was contributed by @Zen-cronic. Thank you for your contribution!

8.28.0

published 8.28.0 • 3 months ago

Changelog

8.28.0

Important Changes

Beta release of official NestJS SDK

This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)

This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK previously incorrectly processed the original values as they were reported from the browser. When updating your SDK to this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were smaller than the actually measured values. We apologize for the inconvenience!

Other Changes

feat(nestjs): Add SentryGlobalGraphQLFilter (#13545)
feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#13264)
feat(nextjs): Add bundleSizeOptimizations to build options (#13323)
feat(nextjs): Stabilize captureRequestError (#13550)
feat(nuxt): Wrap config in nuxt context (#13457)
feat(profiling): Expose profiler as top level primitive (#13512)
feat(replay): Add layout shift to CLS replay data (#13386)
feat(replay): Upgrade rrweb packages to 2.26.0 (#13483)
fix(cdn): Do not mangle _metadata (#13426)
fix(cdn): Fix SDK source for CDN bundles (#13475)
fix(nestjs): Check arguments before instrumenting with @Injectable (#13544)
fix(nestjs): Ensure exception and host are correctly passed on when using @WithSentry (#13564)
fix(node): Suppress tracing for transport request execution rather than transport creation (#13491)
fix(replay): Consider more things as DOM mutations for dead clicks (#13518)
fix(vue): Correctly obtain component name (#13484)

Work in this release was contributed by @leopoldkristjansson, @mhuggins and @filips123. Thank you for your contributions!

8.27.0

published 8.27.0 • 3 months ago

Changelog

8.27.0

Important Changes

fix(nestjs): Exception filters in main app module are not being executed (#13278)

With this release nestjs error monitoring is no longer automatically set up after adding the SentryModule to your application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to your main module providers or decorate the catch() method in your existing global exception filters with the newly released @WithSentry() decorator. See the docs for more details.

Other Changes

feat: Add options for passing nonces to feedback integration (#13347)
feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
feat(deps): bump @prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
feat(feedback): Improve error message for 403 errors (#13441)
fix(deno): Don't rely on Deno.permissions.querySync (#13378)
fix(replay): Ensure we publish replay CDN bundles (#13437)

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

7.119.0

published 7.119.0 • 3 months ago

8.26.0

published 8.26.0 • 3 months ago

Changelog

8.26.0

Important Changes

feat(node): Add fsInstrumentation (#13291)

This release adds fsIntegration, an integration that instruments the fs API to the Sentry Node SDK. The integration creates spans with naming patterns of fs.readFile, fs.unlink, and so on.

This integration is not enabled by default and needs to be registered in your Sentry.init call. You can configure via options whether to include path arguments or error messages as span attributes when an fs call fails:
```
Sentry.init({
  integrations: [
    Sentry.fsIntegration({
      recordFilePaths: true,
      recordErrorMessagesAsSpanAttributes: true,
    }),
  ],
});
```
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of file I/O, like for example when running a framework dev server, including this integration can massively slow down your application.

Other Changes

feat(browser): Add spotlightBrowser integration (#13263)
feat(browser): Allow sentry in safari extension background page (#13209)
feat(browser): Send CLS as standalone span (experimental) (#13056)
feat(core): Add OpenTelemetry-specific getTraceData implementation (#13281)
feat(nextjs): Always add browserTracingIntegration (#13324)
feat(nextjs): Always transmit trace data to the client (#13337)
feat(nextjs): export SentryBuildOptions (#13296)
feat(nextjs): Update experimental_captureRequestError to reflect RequestInfo.path change in Next.js canary (#13344)
feat(nuxt): Always add tracing meta tags (#13273)
feat(nuxt): Set transaction name for server error (#13292)
feat(replay): Add a replay-specific logger (#13256)
feat(sveltekit): Add bundle size optimizations to plugin options (#13318)
feat(sveltekit): Always add browserTracingIntegration (#13322)
feat(tracing): Make long animation frames opt-out (#13255)
fix(astro): Correctly extract request data (#13315)
fix(astro): Only track access request headers in dynamic page requests (#13306)
fix(nuxt): Add import line for disabled autoImport (#13342)
fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)
fix(remix): Ensure origin is correctly set for remix server spans (#13305)

Work in this release was contributed by @MonstraG, @undead-voron and @Zen-cronic. Thank you for your contributions!

8.25.0

published 8.25.0 • 4 months ago

Changelog