@sentry/browser - npm Package Versions

published 8.21.0 • 4 months ago

Changelog

8.21.0

Important Changes

Alpha release of Official Cloudflare SDK
- feat(cloudflare): Add withSentry method (#13025)
- feat(cloudflare): Add cloudflare sdk scaffolding (#12953)
- feat(cloudflare): Add basic cloudflare package and tests (#12861)

This release contains the alpha version of @sentry/cloudflare, our SDK for the Cloudflare Workers JavaScript Runtime! For details on how to use it, please see the README. Any feedback/bug reports are greatly appreciated, please reach out on GitHub.

Please note that only Cloudflare Workers are tested and supported - official Cloudflare Pages support will come in an upcoming release.

Other Changes

feat(feedback): Make cropped screenshot area draggable (#13071)
feat(core): Adapt spans for client-side fetch to streaming responses (#12723)
feat(core): Capture # of dropped spans through beforeSendTransaction (#13022)
feat(deps): bump @opentelemetry/instrumentation-aws-sdk from 0.43.0 to 0.43.1 (#13089)
feat(deps): bump @opentelemetry/instrumentation-express from 0.41.0 to 0.41.1 (#13090)
feat(nestjs): Automatic instrumentation of nestjs middleware (#13065)
feat(node): Upgrade import-in-the-middle to 1.11.0 (#13107)
feat(nuxt): Add connected tracing meta tags (#13098)
feat(nuxt): Add vue-router instrumentation (#13054)
feat(solidstart): Add server action instrumentation helper (#13035)
fix(feedback): Ensure pluggable feedback CDN bundle is correctly built (#13081)
fix(nextjs): Only delete clientside bundle source maps with sourcemaps.deleteFilesAfterUpload (#13102)
fix(node): Improve OTEL validation logic (#13079)

8.20.0

published 8.20.0 • 4 months ago

Changelog

8.20.0

Important Changes

feat(node): Allow to pass registerEsmLoaderHooks to preload (#12998)

You can write your own custom preload script and configure this in the preload options. registerEsmLoaderHooks can be passed as an option to preloadOpenTelemetry, which allows to exclude/include packages in the preload.

fix(node): Do not emit fetch spans when tracing is disabled (#13003)

Sentry will not emit "fetch" spans if tracing is disabled. This is relevant for user who use their own sampler.

Other Changes

feat(feedback): Trigger button aria label configuration (#13008)
feat(nestjs): Change nest sdk setup (#12920)
feat(node): Extend ESM hooks options for iitm v1.10.0 (#13016)
feat(node): Send client reports (#12951)
feat(nuxt): Automatically add BrowserTracing (#13005)
feat(nuxt): Setup source maps with vite config (#13018)
feat(replay): Improve public Replay APIs (#13000)

8.19.0

published 8.19.0 • 4 months ago

Changelog

8.19.0

feat(core): Align Span interface with OTEL (#12898)
fix(angular): Remove afterSendEvent listener once root injector is destroyed (#12786)
fix(browser): Fix bug causing unintentional dropping of transactions (#12933)
fix(feedback): Add a missing call of Actor.appendToDom method when DOMContentLoaded event is triggered (#12973)
feat(vercel-edge): Add dedupe as default integration (#12957)
fix(node): Pass inferred name & attributes to tracesSampler (#12945)
feat(express): Allow to pass options to setupExpressErrorHandler (#12952)

Work in this release was contributed by @jaspreet57 and @arturovt. Thank you for your contribution!

8.18.0

published 8.18.0 • 4 months ago

Changelog

8.18.0

Important Changes

ref: Deprecate enableTracing (12897)

The enableTracing option has been deprecated and will be removed in the next major version. We recommend removing it in favor of the tracesSampleRate and tracesSampler options. If you want to enable performance monitoring, please set the tracesSampleRate to a sample rate of your choice, or provide a sampling function as tracesSampler option instead. If you want to disable performance monitoring, remove the tracesSampler and tracesSampleRate options.

Other Changes

feat(node): Expose exclude and include options for ESM loader (#12910)
feat(browser): Add user agent to INP standalone span attributes (#12896)
feat(nextjs): Add experimental_captureRequestError for onRequestError hook (#12885)
feat(replay): Bump rrweb to 2.25.0 (#12478)
feat(tracing): Add long animation frame tracing (#12646)
fix: Cleanup hooks when they are not used anymore (#12852)
fix(angular): Guard ErrorEvent check in ErrorHandler to avoid throwing in Node environments (#12892)
fix(inp): Ensure INP spans have correct transaction (#12871)
fix(nestjs): Do not make SentryTraced() decorated functions async (#12879)
fix(nextjs): Support automatic instrumentation for app directory with custom page extensions (#12858)
fix(node): Ensure correct URL is passed to ignoreIncomingRequests callback (#12929)
fix(otel): Do not add otel.kind: INTERNAL attribute (#12841)
fix(solidstart): Set proper sentry origin for solid router integration when used in solidstart sdk (#12919)
fix(sveltekit): Add Vite peer dep for proper type resolution (#12926)
fix(tracing): Ensure you can pass null as parentSpan in startSpan* (#12928)
ref(core): Small bundle size improvement (#12830)

Work in this release was contributed by @GitSquared, @ziyadkhalil and @mcous. Thank you for your contributions!

8.17.0

published 8.17.0 • 4 months ago

Changelog

8.17.0

feat: Upgrade OTEL deps (#12809)
fix(nuxt): Add module to build:transpile script (#12843)
fix(browser): Allow SDK initialization in NW.js apps (#12846)

8.16.0

published 8.16.0 • 4 months ago

Changelog

8.16.0

Important Changes

feat(nextjs): Use spans generated by Next.js for App Router (#12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have a root span, and more importantly, if you had data stream to the client, its duration was not captured because the server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with server component spans being descendants of that transaction. This means you will get more data that is also more accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge runtime), and you will instead receive transactions for your App Router SSR requests that look like GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

- feat(nestjs): Add nest cron monitoring support (#12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@nestjs/schedule';
import { SentryCron, MonitorConfig } from '@sentry/nestjs';
import type { MonitorConfig } from '@sentry/types';

const monitorConfig: MonitorConfig = {
  schedule: {
    type: 'crontab',
    value: '* * * * *',
  },
  checkinMargin: 2, // In minutes. Optional.
  maxRuntime: 10, // In minutes. Optional.
  timezone: 'America/Los_Angeles', // Optional.
};

export class MyCronService {
  @Cron('* * * * *')
  @SentryCron('my-monitor-slug', monitorConfig)
  handleCron() {
    // Your cron job logic here
  }
}

Other Changes

feat(node): Allow to pass instrumentation config to httpIntegration (#12761)
feat(nuxt): Add server error hook (#12796)
feat(nuxt): Inject sentry config with Nuxt addPluginTemplate (#12760)
fix: Apply stack frame metadata before event processors (#12799)
fix(feedback): Add missing h import in ScreenshotEditor (#12784)
fix(node): Ensure autoSessionTracking is enabled by default (#12790)
ref(feedback): Let CropCorner inherit the existing h prop (#12814)
ref(otel): Ensure we never swallow args for ContextManager (#12798)

8.15.0

published 8.15.0 • 4 months ago

Changelog

8.15.0

feat(core): allow unregistering callback through on (#11710)
feat(nestjs): Add function-level span decorator to nestjs (#12721)
feat(otel): Export & use spanTimeInputToSeconds for otel span exporter (#12699)
fix(core): Pass origin as referrer for lazyLoadIntegration (#12766)
fix(deno): Publish from build directory (#12773)
fix(hapi): Specify error channel to filter boom errors (#12725)
fix(react): Revert back to jsxRuntime: 'classic' to prevent breaking react 17 (#12775)
fix(tracing): Report dropped spans for transactions (#12751)
ref(scope): Delete unused public getStack() (#12737)

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

8.14.0

published 8.14.0 • 4 months ago

Changelog

8.14.0

Important Changes

feat(nestjs): Filter 4xx errors (#12695)

The @sentry/nestjs SDK no longer captures 4xx errors automatically.

Other Changes

chore(react): Remove private namespace JSX (#12691)
feat(deps): bump @opentelemetry/propagator-aws-xray from 1.25.0 to 1.25.1 (#12719)
feat(deps): bump @prisma/instrumentation from 5.16.0 to 5.16.1 (#12718)
feat(node): Add registerEsmLoaderHooks option (#12684)
feat(opentelemetry): Expose sampling helper (#12674)
fix(browser): Make sure measure spans have valid start timestamps (#12648)
fix(hapi): Widen type definitions (#12710)
fix(nextjs): Attempt to ignore critical dependency warnings (#12694)
fix(react): Fix React jsx runtime import for esm (#12740)
fix(replay): Start replay in afterAllSetup instead of next tick (#12709)

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

8.13.0

published 8.13.0 • 5 months ago

Changelog