Skip to content

Bump @sentry/nextjs from 7.110.1 to 8.17.0

DependabotCatalogueIndicateurs requested to merge dependabot-npm_and_yarn-sentry-nextjs-8.17.0 into develop

Bumps @sentry/nextjs from 7.110.1 to 8.17.0.

Release notes

Sourced from @​sentry/nextjs's releases.

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)

Bundle size 📦

Path Size
@​sentry/browser 22.31 KB
@​sentry/browser (incl. Tracing) 33.45 KB
@​sentry/browser (incl. Tracing, Replay) 69.2 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 62.53 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 73.27 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 85.9 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics) 87.76 KB
@​sentry/browser (incl. metrics) 26.59 KB
@​sentry/browser (incl. Feedback) 38.98 KB
@​sentry/browser (incl. sendFeedback) 26.92 KB
@​sentry/browser (incl. FeedbackAsync) 31.54 KB
@​sentry/react 25.05 KB
@​sentry/react (incl. Tracing) 36.49 KB
@​sentry/vue 26.41 KB
@​sentry/vue (incl. Tracing) 35.31 KB
@​sentry/svelte 22.44 KB
CDN Bundle 23.52 KB
CDN Bundle (incl. Tracing) 35.21 KB
CDN Bundle (incl. Tracing, Replay) 69.31 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 74.51 KB
CDN Bundle - uncompressed 69.02 KB
CDN Bundle (incl. Tracing) - uncompressed 104.04 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 214.43 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 227.15 KB
@​sentry/nextjs (client) 36.37 KB
@​sentry/sveltekit (client) 34.1 KB
@​sentry/node 130.79 KB
@​sentry/node - without tracing 91.88 KB
@​sentry/aws-serverless 117.05 KB

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

... (truncated)

Changelog

Sourced from @​sentry/nextjs's 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

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 {
</tr></table>

... (truncated)

Commits

Merge request reports