@sentry/utils - npm Package Versions

published 8.13.0 • 5 months ago

Changelog

8.13.0

Important Changes

feat(nestjs): Add Nest SDK This release adds a dedicated SDK for NestJS (@sentry/nestjs) in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (@sentry/node) supporting the same set of features. See the docs for how to use the SDK.

Other Changes

deps: Bump bundler plugins to 2.20.1 (#12641)
deps(nextjs): Remove react peer dep and allow rc (#12670)
feat: Update OTEL deps (#12635)
feat(deps): bump @prisma/instrumentation from 5.15.0 to 5.15.1 (#12627)
feat(node): Add context info for missing instrumentation (#12639)
fix(feedback): Improve feedback error message (#12647)

8.12.0

published 8.12.0 • 5 months ago

Changelog

8.12.0

Important Changes

feat(solid): Remove need to pass router hooks to solid integration (breaking)

This release introduces breaking changes to the @sentry/solid package (which is currently out in alpha).

We've made it easier to get started with the solid router integration by removing the need to pass use* hooks explicitly to solidRouterBrowserTracingIntegration. Import solidRouterBrowserTracingIntegration from @sentry/solid/solidrouter and add it to Sentry.init

import * as Sentry from '@sentry/solid';
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@sentry/solid/solidrouter';
import { Router } from '@solidjs/router';

Sentry.init({
  dsn: '__PUBLIC_DSN__',
  integrations: [solidRouterBrowserTracingIntegration()],
  tracesSampleRate: 1.0, //  Capture 100% of the transactions
});

const SentryRouter = withSentryRouterRouting(Router);

feat(core): Return client from init method (#12585)

Sentry.init() now returns a client directly, so you don't need to explicitly call getClient() anymore:

const client = Sentry.init();

feat(nextjs): Add deleteSourcemapsAfterUpload option (#12457)

This adds an easy way to delete sourcemaps immediately after uploading them:

module.exports = withSentryConfig(nextConfig, {
  sourcemaps: {
    deleteSourcemapsAfterUpload: true,
  },
});

feat(node): Allow to configure maxSpanWaitDuration (#12610)

Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However, if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early. In this case, you can increase this duration to a value that fits your expected data.

Other Changes

feat(feedback): Extra check for iPad in screenshot support (#12593)
fix(bundle): Ensure CDN bundles do not overwrite window.Sentry (#12580)
fix(feedback): Inject preact from feedbackModal into feedbackScreenshot integration (#12535)
fix(node): Re-throw errors from koa middleware (#12609)
fix(remix): Mark isRemixV2 as optional in exposed types. (#12614)
ref(node): Add error message to NodeFetch log (#12612)

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

8.12.0-beta.0

published 8.12.0-beta.0 • 5 months ago

8.11.0

published 8.11.0 • 5 months ago

Changelog

8.11.0

Important Changes

feat(core): Add parentSpan option to startSpan* APIs (#12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });

  Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});

  Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});

Other Changes

feat(node): Detect release from more providers (#12529)
fix(profiling-node): Use correct getGlobalScope import (#12564)
fix(profiling-node) sample timestamps need to be in seconds (#12563)
ref: Align @sentry/node exports from framework SDKs. (#12589)

7.118.0

published 7.118.0 • 5 months ago

8.10.0

published 8.10.0 • 5 months ago

Changelog

8.10.0

Important Changes

feat(remix): Migrate to opentelemetry-instrumentation-remix. (#12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@sentry/remix');

Sentry.init({
  dsn: YOUR_DSN
  // opt-in to new auto instrumentation
  autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes

feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#12512)
feat(feedback): Allow passing tags field to any feedback config param (#12197)
feat(feedback): Improve screenshot quality for retina displays (#12487)
feat(feedback): Screenshots don't resize after cropping (#12481)
feat(node) add max lineno and colno limits (#12514)
feat(profiling) add global profile context while profiler is running (#12394)
feat(react): Add React version to events (#12390)
feat(replay): Add url to replay hydration error breadcrumb type (#12521)
fix(core): Ensure standalone spans respect sampled flag (#12533)
fix(core): Use maxValueLength in extra error data integration (#12174)
fix(feedback): Fix scrolling after feedback submission (#12499)
fix(feedback): Send feedback rejects invalid responses (#12518)
fix(nextjs): Update @rollup/plugin-commonjs (#12527)
fix(node): Ensure status is correct for http server span errors (#12477)
fix(node): UnifygetDynamicSamplingContextFromSpan (#12522)
fix(profiling): continuous profile chunks should be in seconds (#12532)
fix(remix): Add nativeFetch support for accessing request headers (#12479)
fix(remix): Export no-op as captureRemixServerException from client SDK (#12497)
ref(node) refactor contextlines to use readline (#12221)

Work in this release was contributed by @AndreyKovanov and @kiliman. Thank you for your contributions!

8.9.2

published 8.9.2 • 5 months ago

Changelog

8.9.2

fix(profiling): Update exports so types generate properly (#12469)

8.9.1

published 8.9.1 • 5 months ago

Changelog

8.9.1

Important changes

feat(solid): Add Solid SDK

This release adds a dedicated SDK for Solid JS in alpha state with instrumentation for Solid Router and a custom ErrorBoundary. See the package README for how to use the SDK.

Other changes

feat(deps): bump @opentelemetry/instrumentation-express from 0.40.0 to 0.40.1 (#12438)
feat(deps): bump @opentelemetry/instrumentation-mongodb from 0.44.0 to 0.45.0 (#12439)
feat(deps): bump @opentelemetry/propagator-aws-xray from 1.24.1 to 1.25.0 (#12437)
feat(nextjs): Allow for suppressing warning about missing global error handler file (#12369)
feat(redis): Add cache logic for redis-4 (#12429)
feat(replay): Replay Web Vital Breadcrumbs (#12296)
fix: Fix types export order (#12404)
fix(astro): Ensure server-side exports work correctly (#12453)
fix(aws-serverless): Add op to Otel-generated lambda function root span (#12430)
fix(aws-serverless): Only auto-patch handler in CJS when loading awslambda-auto (#12392)
fix(aws-serverless): Only start root span in Sentry wrapper if Otel didn't wrap handler (#12407)
fix(browser): Fix INP span creation & transaction tagging (#12372)
fix(nextjs): correct types conditional export ordering (#12355)
fix(replay): Fix guard for exception event (#12441)
fix(vue): Handle span name assignment for nested routes in VueRouter (#12398)

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

8.9.0

published 8.9.0 • 5 months ago

Changelog