chore(deps): update dependency @sentry/nextjs to v10 #1564

renovate · 2025-02-10T13:01:20Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/nextjs (source)	`8.55.0` -> `10.20.0`

Release Notes

getsentry/sentry-javascript (@sentry/nextjs)

`v10.20.0`

Compare Source

Important Changes

feat(flags): Add Growthbook integration (#17440)

Adds a new Growthbook integration for feature flag support.
feat(solid): Add support for TanStack Router Solid (#17735)

Adds support for TanStack Router in the Solid SDK, enabling better routing instrumentation for Solid applications.
feat(nextjs): Support native debugIds in turbopack (#17853)

Adds support for native Debug IDs in Turbopack, improving source map resolution and error tracking for Next.js applications using Turbopack. Native Debug ID generation will be enabled automatically for compatible versions.

Other Changes

feat(nextjs): Prepare for next 16 bundler default (#17868)
feat(node): Capture pino logger name (#17930)
fix(browser): Ignore React 19.2+ component render measure entries (#17905)
fix(nextjs): Fix createRouteManifest with basePath (#17838)
fix(react): Add POP guard for long-running pageload spans (#17867)
fix(tracemetrics): Send boolean for internal replay attribute (#17908)
ref(core): Add weight tracking logic to browser logs/metrics (#17901)

Internal Changes

- chore(nextjs): Add Next.js 16 peer dependency ([#17925](https://redirect.github.com/getsentry/sentry-javascript/pull/17925)) - chore(ci): Update Next.js canary testing ([#17939](https://redirect.github.com/getsentry/sentry-javascript/pull/17939)) - chore: Bump size limit ([#17941](https://redirect.github.com/getsentry/sentry-javascript/pull/17941)) - test(nextjs): Add next@16 e2e test ([#17922](https://redirect.github.com/getsentry/sentry-javascript/pull/17922)) - test(nextjs): Update next 15 tests ([#17919](https://redirect.github.com/getsentry/sentry-javascript/pull/17919)) - chore: Add external contributor to CHANGELOG.md ([#17915](https://redirect.github.com/getsentry/sentry-javascript/pull/17915)) - chore: Add external contributor to CHANGELOG.md ([#17928](https://redirect.github.com/getsentry/sentry-javascript/pull/17928)) - chore: Add external contributor to CHANGELOG.md ([#17940](https://redirect.github.com/getsentry/sentry-javascript/pull/17940))

Work in this release was contributed by @seoyeon9888, @madhuchavva and @thedanchez . Thank you for your contributions!

Bundle size 📦

Path	Size
@sentry/browser	24.07 KB
@sentry/browser - with treeshaking flags	22.6 KB
@sentry/browser (incl. Tracing)	39.89 KB
@sentry/browser (incl. Tracing, Replay)	77.35 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.3 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.94 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.83 KB
@sentry/browser (incl. Feedback)	40.36 KB
@sentry/browser (incl. sendFeedback)	28.61 KB
@sentry/browser (incl. FeedbackAsync)	33.46 KB
@sentry/react	25.73 KB
@sentry/react (incl. Tracing)	41.84 KB
@sentry/vue	28.45 KB
@sentry/vue (incl. Tracing)	41.64 KB
@sentry/svelte	24.08 KB
CDN Bundle	26.31 KB
CDN Bundle (incl. Tracing)	40.55 KB
CDN Bundle (incl. Tracing, Replay)	75.98 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	81.33 KB
CDN Bundle - uncompressed	77.1 KB
CDN Bundle (incl. Tracing) - uncompressed	120.19 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	232.65 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	245.11 KB
@sentry/nextjs (client)	43.85 KB
@sentry/sveltekit (client)	40.3 KB
@sentry/node-core	49.59 KB
@sentry/node	150.78 KB
@sentry/node - without tracing	90.48 KB
@sentry/aws-serverless	103.85 KB

`v10.19.0`

Compare Source

feat(tracemetrics): Add trace metrics behind an experiments flag (#17883)

Internal Changes

chore: add info latest release for the cursor release command (#17876)

Bundle size 📦

Path	Size
@sentry/browser	23.83 KB
@sentry/browser - with treeshaking flags	22.36 KB
@sentry/browser (incl. Tracing)	39.66 KB
@sentry/browser (incl. Tracing, Replay)	77.13 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.01 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.71 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.57 KB
@sentry/browser (incl. Feedback)	40.14 KB
@sentry/browser (incl. sendFeedback)	28.38 KB
@sentry/browser (incl. FeedbackAsync)	33.18 KB
@sentry/react	25.5 KB
@sentry/react (incl. Tracing)	41.56 KB
@sentry/vue	28.24 KB
@sentry/vue (incl. Tracing)	41.39 KB
@sentry/svelte	23.87 KB
CDN Bundle	26.01 KB
CDN Bundle (incl. Tracing)	40.18 KB
CDN Bundle (incl. Tracing, Replay)	75.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	80.96 KB
CDN Bundle - uncompressed	76.34 KB
CDN Bundle (incl. Tracing) - uncompressed	119.32 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	231.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	244.24 KB
@sentry/nextjs (client)	43.54 KB
@sentry/sveltekit (client)	40.02 KB
@sentry/node-core	49.55 KB
@sentry/node	150.75 KB
@sentry/node - without tracing	90.42 KB
@sentry/aws-serverless	103.83 KB

`v10.18.0`

Compare Source

`v10.17.0`

Compare Source

Important Changes

feat(nuxt): Implement server middleware instrumentation (#17796)

This release introduces instrumentation for Nuxt middleware, ensuring that all middleware handlers are automatically wrapped with tracing and error reporting functionality.
fix(aws-serverless): Take http_proxy into account when choosing
useLayerExtension default (#17817)

The default setting for useLayerExtension now considers the http_proxy environment variable.
When http_proxy is set, useLayerExtension will be off by default.
If you use a http_proxy but would still like to make use of the Sentry Lambda extension, exempt localhost in a no_proxy environment variable.

Other Changes

feat(node): Split up http integration into composable parts (#17524)
fix(core): Remove check and always respect ai.telemetry.functionId for Vercel AI gen spans (#17811)
doc(core): Fix outdated JSDoc in beforeSendSpan (#17815)

Internal Changes

ci: Do not run dependabot on e2e test applications (#17813)
docs: Reword changelog for google gen ai integration (#17805)

`v10.16.0`

Compare Source

feat(logs): Add internal replay_is_buffering flag (#17752)
feat(react-router): Update loadContext type to be compatible with middleware (#17758)
feat(replay/logs): Only attach sampled replay Ids to logs (#17750)
fix(browser): Use current start timestamp for CLS span when CLS is 0 (#17800)
fix(core): Prevent instrumentAnthropicAiClient breaking MessageStream api (#17754)
fix(nextjs): Don't use chalk in turbopack config file (#17806)
fix(react): Do not send additional navigation span on pageload (#17799)

Internal Changes

build(aws): Ensure AWS build cache does not keep old files (#17776)
chore: Add publish_release command (#17797)
ref(aws-serverless): Add resolution for import-in-the-middle when building the Lambda layer (#17780)
ref(aws-serverless): Improve README with better examples (#17787)
ref(core): Improve promise buffer (#17788)
Revert "test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)" (#17784)
test(e2e): Pin [email protected] due to @vercel/nft incompatibility (#17777)
test(nextjs): Add route handler tests for turbopack (#17515)
test(react-router): Test v8 middleware (#17783)

`v10.15.0`

Compare Source

Important Changes

feat(cloudflare): Add honoIntegration with error-filtering function (#17743)

This release adds a honoIntegration to @sentry/cloudflare, which exposes a shouldHandleError function that lets you define which errors in onError should be captured.
By default, Sentry captures exceptions with error.status >= 500 || error.status <= 299.

The integration is added by default, and it's possible to modify this behavior like this:
```
 integrations: [
   honoIntegration({
    shouldHandleError: (err) => true; // always capture exceptions in onError
   })
 ]
```
feat(node): Add instrumentation for hono handler (#17428)

This PR enhances the Hono integration by adding comprehensive handler instrumentation, error handling capabilities.

feat(aws): Enable Lambda extension by default when using the Lamba layer (#17684)
feat(browser): Add setActiveSpanInBrowser to set an active span in the browser (#17714)

This PR adds a feature to the browser SDKs only: Making an inactive span active. We do this to enable use cases where having a span only being active in the callback is not practical.

Other Changes

fix(browser): Improve handling of 0 and undefined resource timing values (#17751)
ref(nextjs): Display build compatibility warning for webpack (#17746)

Internal Changes

docs: Reword changelog for google gen ai instrumentation (#17753)
build: Add @typescript-eslint/no-unnecessary-type-assertion rule (#17728)
build: Update TS target to es2020 everywhere (#17709)
chore: Add external contributor to CHANGELOG.md (#17745)

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

`v10.14.0`

Compare Source

Important Changes

feat(cloudflare,vercel-edge): Add support for Google Gen AI instrumentation (#17723)

The SDK now supports manually instrumenting Google's Generative AI operations in Cloudflare Workers and Vercel Edge Runtime environments, providing insights into your AI operations. You can use const wrappedClient = Sentry.instrumentGoogleGenAIClient(genAiClient) to get an instrumented client.

Other Changes

fix(nextjs): Display updated turbopack warnings (#17737)
ref(core): Wrap isolationscope in WeakRef when storing it on spans (#17712)

Internal Changes

test(node): Avoid using specific port for node-integration-tests (#17729)
test(nuxt): Update Nuxt version and add Nitro $fetch test (#17713)

`v10.13.0`

Compare Source

Important Changes

feat(browser): Add option to explicitly end pageload span via reportPageLoaded() (#17697)

With this release you can take manual control of ending the pageload span. Usually this span is ended automatically by the SDK, based on a period of inactivity after the initial page was loaded in the browser. If you want full control over the pageload duration, you can tell Sentry, when your page was fully loaded:
```
Sentry.init({
  //...
  integrations: [
    // 1. Enable manual pageload reporting
    Sentry.browserTracingIntegration({ enableReportPageLoaded: true }),
  ],
});

// 2. Whenever you decide the page is loaded, call:
Sentry.reportPageLoaded();
```
Note that if Sentry.reportPageLoaded() is not called within 30 seconds of the initial pageload (or whatever value the finalTimeout option is set to), the pageload span will be ended automatically.
feat(core,node): Add instrumentation for GoogleGenerativeAI (#17625)

The SDK now automatically instruments the @google/generative-ai package to provide insights into your AI operations.
feat(nextjs): Promote useRunAfterProductionCompileHook to non-experimental build option (#17721)

The useRunAfterProductionCompileHook option is no longer experimental and is now a stable build option for Next.js projects.
feat(nextjs): Use afterProductionCompile hook for webpack builds (#17655)

Next.js projects using webpack can opt-in to use the useRunAfterProductionCompileHook hook for source map uploads.
feat(nextjs): Flip default value for useRunAfterProductionCompileHook for Turbopack builds (#17722)

The useRunAfterProductionCompileHook option is now enabled by default for Turbopack builds, enabling automated source map uploads.
feat(node): Do not drop 300 and 304 status codes by default (#17686)

HTTP transactions with 300 and 304 status codes are now captured by default, providing better visibility into redirect and caching behavior.

Other Changes

feat(core): Add logger to core and allow scope to be passed log methods (#17698)
feat(core): Allow to pass onSuccess to handleCallbackErrors (#17679)
feat(core): Create template attributes in consoleLoggingIntegration (#17703)
feat(deps): bump @sentry/cli from 2.52.0 to 2.53.0 (#17652)
feat(node): Add extra platforms to os context (#17720)
fix(browser): Ensure idle span duration is adjusted when child spans are ignored (#17700)
fix(core): Ensure builtin stack frames don't affect thirdPartyErrorFilterIntegration (#17693)
fix(core): Fix client hook edge cases around multiple callbacks (#17706)
fix(nextjs): Enable fetch span when OTel setup is skipped (#17699)
fix(node): Fix this context for vercel AI instrumentation (#17681)

Internal Changes

chore: Add external contributor to CHANGELOG.md (#17725)
chore: Add link to build and test icon in readme (#17719)
chore(nuxt): Bump Vite and Rollup plugins (#17671)
chore(repo): Add changelog entry for reportPageLoaded (#17724)
ci: Fix lookup of changed E2E test apps (#17707)
ci(test-matrix): Add logs for getTestMatrix (#17673)
ref: Avoid some usage of SyncPromise where not needed (#17641)
ref(core): Add debug log when dropping a span via ignoreSpans (#17692)
ref(core): Avoid looking up anthropic-ai integration options (#17694)
ref(core): Streamline module_metadata assignment and cleanup functions (#17696)
ref(remix): Avoid unnecessary error wrapping HandleDocumentRequestFunction (#17680)
Revert "[Gitflow] Merge master into develop"

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

`v10.12.0`

Compare Source

Important Changes

ref: Add and Adjust error event mechanism values

This release includes a variety of changes aimed at setting the mechanism field on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.
Relevant PRs

Released in 10.12.0:
- ref(angular): Adjust ErrorHandler event mechanism (#17608)
- ref(astro): Adjust mechanism on error events captured by astro middleware (#17613)
- ref(aws-severless): Slightly adjust aws-serverless mechanism type (#17614)
- ref(bun): Adjust mechanism of errors captured in Bun.serve (#17616)
- ref(cloudflare): Adjust event mechanisms and durable object origin (#17618)
- ref(core): Adjust mechanism in captureConsoleIntegration (#17633)
- ref(core): Adjust MCP server error event mechanism (#17622)
- ref(core): Simplify linkedErrors mechanism logic (#17600)
- ref(deno): Adjust mechanism of errors caught by globalHandlersIntegration (#17635)
- ref(nextjs): Set more specific event mechanisms (#17543)
- ref(node): Adjust mechanism of express, hapi and fastify error handlers (#17623)
- ref(node-core): Add mechanism to cron instrumentations (#17544)
- ref(node-core): Add more specific mechanism.type to worker thread errors from childProcessIntegration (#17578)
- ref(node-core): Adjust mechanism of onUnhandledRejection and onUnhandledException integrations (#17636)
- ref(node): Add mechanism to errors captured via connect and koa integrations (#17579)
- ref(nuxt): Add and adjust mechanism.type in error events (#17599)
- ref(react): Add mechanism to reactErrorHandler and adjust mechanism in ErrorBoundary (#17602)
- ref(remix): Adjust event mechanism of captureRemixServerException (#17629)
- ref(replay-internal): Add mechanism to error caught by replayIntegration in debug mode (#17606)
- ref(solid): Add mechanism to error captured by withSentryErrorBoundary (#17607)
- ref(solidstart): Adjust event mechanism in withServerActionInstrumentation (#17637)
- ref(sveltekit): Adjust mechanism of error events (#17646)
- ref(vue): Adjust mechanism in Vue error handler (#17647)
Released in 10.11.0:
- ref(browser): Add more specific mechanism.type to errors captured by httpClientIntegration (#17254)
- ref(browser): Set more descriptive mechanism.type in browserApiErrorsIntergation (#17251)
- ref(core): Add mechanism.type to trpcMiddleware errors (#17287)
- ref(core): Add more specific event mechanisms and span origins to openAiIntegration (#17288)
- ref(nestjs): Add mechanism to captured errors (#17312)

feat(node) Ensure prismaIntegration works with Prisma 5 (#17595)

We used to require to pass in the v5 version of @prisma/instrumentation into prismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() }), if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because @prisma/instrumentation@5 requires OTEL v1.

With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on @prisma/instrumentation@5 if you had it in your application. You only need to configure the tracing preview feature according to our docs.

feat(deps): Update OpenTelemetry dependencies (#17558)
- @opentelemetry/core bumped to ^2.1.0
- @opentelemetry/context-async-hooks bumped to ^2.1.0
- @opentelemetry/resources bumped to ^2.1.0
- @opentelemetry/sdk-trace-base bumped to ^2.1.0
- @opentelemetry/semantic-conventions bumped to ^1.37.0
- @opentelemetry/instrumentation bumped to ^0.204.0
- @opentelemetry/instrumentation-http bumped to ^0.204.0
- @opentelemetry/instrumentation-amqplib bumped to ^0.51.0
- @opentelemetry/instrumentation-aws-sdk bumped to ^0.59.0
- @opentelemetry/instrumentation-connect bumped to ^0.48.0
- @opentelemetry/instrumentation-dataloader bumped to ^0.22.0
- @opentelemetry/instrumentation-express bumped to ^0.53.0
- @opentelemetry/instrumentation-fs bumped from to ^0.24.0
- @opentelemetry/instrumentation-generic-pool bumped to ^0.48.0
- @opentelemetry/instrumentation-graphql bumped to ^0.52.0
- @opentelemetry/instrumentation-hapi bumped to ^0.51.0
- @opentelemetry/instrumentation-ioredis bumped to ^0.52.0
- @opentelemetry/instrumentation-kafkajs bumped to ^0.14.0
- @opentelemetry/instrumentation-knex bumped to ^0.49.0
- @opentelemetry/instrumentation-koa bumped to ^0.52.0
- @opentelemetry/instrumentation-lru-memoizer bumped to ^0.49.0
- @opentelemetry/instrumentation-mongodb bumped from to ^0.57.0
- @opentelemetry/instrumentation-mongoose bumped from to ^0.51.0
- @opentelemetry/instrumentation-mysql bumped to ^0.50.0
- @opentelemetry/instrumentation-mysql2 bumped to ^0.51.0
- @opentelemetry/instrumentation-nestjs-core bumped to ^0.50.0
- @opentelemetry/instrumentation-pg bumped to ^0.57.0
- @opentelemetry/instrumentation-redis bumped to ^0.53.0
- @opentelemetry/instrumentation-undici bumped to ^0.15.0
- @prisma/instrumentation bumped to 6.15.0

Other Changes

feat(browser): Add timing and status atttributes to resource spans (#17562)
feat(cloudflare,vercel-edge): Add support for Anthropic AI instrumentation (#17571)
feat(core): Add Consola integration (#17435)
feat(deps): Update OpenTelemetry dependencies (#17569)
feat(core): Export TracesSamplerSamplingContext type (#17523)
feat(deno): Add OpenTelemetry support and vercelAI integration (#17445)
feat(node-core): Remove experimental note from winston api (#17626)
feat(node): Ensure prismaIntegration works with Prisma v5 (#17595)
feat(node): Tidy existing ESM loader hook (#17566)
feat(sveltekit): Align build time options with shared type (#17413)
fix(core): Fix error handling when sending envelopes (#17662)
fix(browser): Always start navigation as root span (#17648)
fix(browser): Ensure propagated parentSpanId stays consistent during trace in TwP mode (#17526)
fix(cloudflare): Initialize once per workflow run and preserve scope for step.do (#17582)
fix(nextjs): Add edge polyfills for nextjs-13 in dev mode (#17488)
fix(nitro): Support nested _platform properties in Nitro 2.11.7+ (#17596)
fix(node): Preserve synchronous return behavior for streamText and other methods for AI (#17580)
ref(node): Inline types imported from shimmer (#17597) - ref(nuxt): Add and adjust mechanism.type in error events (#17599)
ref(browser): Improve fetchTransport error handling (#17661)

Internal Changes

chore: Add changelog note about mechanism changes (#17632)
chore(aws): Update README.md (#17601)
chore(deps): bump hono from 4.7.10 to 4.9.7 in /dev-packages/e2e-tests/test-applications/cloudflare-hono (#17630)
chore(deps): bump next from 14.2.25 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-app-dir (#17627)
chore(deps): bump next from 14.2.25 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-pages-dir (#17620)
chore(deps): bump next from 14.2.29 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-orpc (#17494)
chore(deps): bump next from 14.2.30 to 14.2.32 in /dev-packages/e2e-tests/test-applications/nextjs-14 (#17628)
chore(repo): Rename .claude/settings.local.json to .claude/settings.json (#17591)
docs(issue-template): Add note about prioritization (#17590)
ref(core): Streamline event processor handling (#17634)
test(angular): Bump TS version to 5.9.0 in Angular 20 e2e test (#17605)
test(nextjs): Remove Next 13 and pin Next 14 canary and latest tests (#17577)
test(react-router): Unflake flushIfServerless test (#17610)

`v10.11.0`

Compare Source

Important Changes

feat(aws): Add experimental AWS Lambda extension for tunnelling events (#17525)

This release adds an experimental Sentry Lambda extension to the existing Sentry Lambda layer. Sentry events are now tunneled through the extension and then forwarded to Sentry. This has the benefit of reducing the request processing time.

To enable it, set _experiments.enableLambdaExtension in your Sentry config like this:
```
Sentry.init({
  dsn: '<YOUR_DSN>',
  _experiments: {
    enableLambdaExtension: true,
  },
});
```

Other Changes

feat(core): Add replay id to logs (#17563)
feat(core): Improve error handling for Anthropic AI instrumentation (#17535)
feat(deps): bump @opentelemetry/instrumentation-ioredis from 0.51.0 to 0.52.0 (#17557)
feat(node): Add incoming request headers as OTel span attributes (#17475)
fix(astro): Ensure traces are correctly propagated for static routes (#17536)
fix(react): Remove handleExistingNavigation (#17534)
ref(browser): Add more specific mechanism.type to errors captured by httpClientIntegration (#17254)
ref(browser): Set more descriptive mechanism.type in browserApiErrorsIntergation (#17251)
ref(core): Add mechanism.type to trpcMiddleware errors (#17287)
ref(core): Add more specific event mechanisms and span origins to openAiIntegration (#17288)
ref(nestjs): Add mechanism to captured errors (#17312)

Internal Changes

chore: Use proper test-utils dependency in workspace (#17538)
chore(test): Remove geist font (#17541)
ci: Check for stable lockfile (#17552)
ci: Fix running of only changed E2E tests (#17551)
ci: Remove project automation workflow (#17508)
test(node-integration-tests): pin ai@5.0.30 to fix test fails (#17542)

`v10.10.0`

Compare Source

Important Changes

feat(browser): Add support for propagateTraceparent SDK option (#17509)

Adds support for a new browser SDK init option, propagateTraceparent for attaching a W3C compliant traceparent header to outgoing fetch and XHR requests, in addition to sentry-trace and baggage headers. More details can be found here.

feat(core): Add tool calls attributes for Anthropic AI (#17478)

Adds missing tool call attributes, we add gen_ai.response.tool_calls attribute for Anthropic AI, supporting both streaming and non-streaming requests.

feat(nextjs): Use compiler hook for uploading turbopack sourcemaps (#17352)

Adds a new experimental flag _experimental.useRunAfterProductionCompileHook to withSentryConfig for automatic source maps uploads when building a Next.js app with next build --turbopack.
When set we:

Automatically enable source map generation for turbopack client files (if not explicitly disabled)
Upload generated source maps to Sentry at the end of the build by leveraging a Next.js compiler hook.

Other Changes

feat(feedback): Add more labels so people can configure Highlight and Hide labels (#17513)
fix(node): Add origin for OpenAI spans & test auto instrumentation (#17519)

Bundle size 📦

Path	Size
@sentry/browser	23.59 KB
@sentry/browser - with treeshaking flags	22.2 KB
@sentry/browser (incl. Tracing)	39.19 KB
@sentry/browser (incl. Tracing, Replay)	76.63 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.64 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	81.2 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	93.13 KB
@sentry/browser (incl. Feedback)	39.93 KB
@sentry/browser (incl. sendFeedback)	28.13 KB
@sentry/browser (incl. FeedbackAsync)	32.96 KB
@sentry/react	25.27 KB
@sentry/react (incl. Tracing)	41.11 KB
@sentry/vue	27.97 KB
@sentry/vue (incl. Tracing)	40.95 KB
@sentry/svelte	23.62 KB
CDN Bundle	25.14 KB
CDN Bundle (incl. Tracing)	39.05 KB
CDN Bundle (incl. Tracing, Replay)	74.48 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	79.82 KB
CDN Bundle - uncompressed	73.4 KB
CDN Bundle (incl. Tracing) - uncompressed	115.49 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	227.88 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	240.35 KB
@sentry/nextjs (client)	43.08 KB
@sentry/sveltekit (client)	39.62 KB
@sentry/node-core	48.49 KB
@sentry/node	147.1 KB
@sentry/node - without tracing	90.07 KB
@sentry/aws-serverless	103.06 KB

`v10.9.0`

Compare Source

Important Changes

feat(node): Update httpIntegration handling of incoming requests (#17371)

This version updates the handling of the Node SDK of incoming requests. Instead of relying on @opentelemetry/instrumentation-http, we now handle incoming request instrumentation internally, ensuring that we can optimize performance as much as possible and avoid interop problems.

This change should not affect you, unless you're relying on very in-depth implementation details. Importantly, this also drops the _experimentalConfig option of the integration - this will no longer do anything.
Finally, you can still pass instrumentation.{requestHook,responseHook,applyCustomAttributesOnSpan} options, but they are deprecated and will be removed in v11. Instead, you can use the new incomingRequestSpanHook configuration option if you want to adjust the incoming request span.

Other Changes

feat(browser): Add replay.feedback CDN bundle (#17496)
feat(browser): Export sendFeedback from CDN bundles (#17495)
fix(astro): Ensure span name from beforeStartSpan isn't overwritten (#17500)
fix(browser): Ensure source is set correctly when updating span name in-place in beforeStartSpan (#17501)
fix(core): Only set template attributes on logs if parameters exist (#17480)
fix(nextjs): Fix parameterization for root catchall routes (#17489)
fix(node-core): Shut down OTel TraceProvider when calling Sentry.close() (#17499)

Internal Changes

chore: Add changelog script back to package.json (#17517)
chore: Ensure prettier is run on all files (#17497)
chore: Ignore prettier commit for git blame (#17498)
chore: Remove experimental from Nuxt SDK package description (#17483)
ci: Capture overhead in node app (#17420)
ci: Ensure we fail on cancelled jobs (#17506)
ci(deps): bump actions/checkout from 4 to 5 (#17505)
ci(deps): bump actions/create-github-app-token from 2.0.6 to 2.1.1 (#17504)
test(aws): Improve reliability on CI (#17502)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot added the dependencies Pull requests that update a dependency file label Feb 10, 2025

renovate bot had a problem deploying to data-manager-ui/test February 10, 2025 13:01 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d62d176 to 68e958c Compare February 11, 2025 16:57

renovate bot had a problem deploying to data-manager-ui/test February 11, 2025 16:57 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 68e958c to 24a8f16 Compare February 13, 2025 12:07

renovate bot had a problem deploying to data-manager-ui/test February 13, 2025 12:07 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 24a8f16 to 18d524e Compare February 24, 2025 18:36

renovate bot had a problem deploying to data-manager-ui/test February 24, 2025 18:36 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 18d524e to e5d40d8 Compare February 28, 2025 15:25

renovate bot had a problem deploying to data-manager-ui/test February 28, 2025 15:25 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from e5d40d8 to 1510c7b Compare March 5, 2025 16:07

renovate bot had a problem deploying to data-manager-ui/test March 5, 2025 16:07 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 1510c7b to 1df7a7b Compare March 6, 2025 22:41

renovate bot had a problem deploying to data-manager-ui/test March 6, 2025 22:41 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 1df7a7b to 7ee0aa5 Compare March 15, 2025 21:04

renovate bot had a problem deploying to data-manager-ui/test March 15, 2025 21:06 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 7ee0aa5 to f6d64ae Compare March 15, 2025 21:16

renovate bot had a problem deploying to data-manager-ui/test March 15, 2025 21:25 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f6d64ae to 8d94c11 Compare March 17, 2025 16:31

renovate bot had a problem deploying to data-manager-ui/test March 17, 2025 16:31 Failure

renovate bot had a problem deploying to data-manager-ui/test September 9, 2025 14:45 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 2daecef to 10049fb Compare September 16, 2025 15:47

renovate bot had a problem deploying to data-manager-ui/test September 16, 2025 15:48 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 10049fb to c96f62d Compare September 22, 2025 13:56

renovate bot had a problem deploying to data-manager-ui/test September 22, 2025 13:56 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from c96f62d to 11bb7c0 Compare September 23, 2025 10:39

renovate bot had a problem deploying to data-manager-ui/test September 23, 2025 10:39 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 11bb7c0 to d76dfce Compare September 24, 2025 18:38

renovate bot had a problem deploying to data-manager-ui/test September 24, 2025 18:38 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d76dfce to d52114b Compare September 25, 2025 16:18

renovate bot had a problem deploying to data-manager-ui/test September 25, 2025 16:19 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d52114b to 2d01d07 Compare September 29, 2025 17:25

renovate bot had a problem deploying to data-manager-ui/test September 29, 2025 17:26 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 2d01d07 to fb4e481 Compare September 30, 2025 12:54

renovate bot had a problem deploying to data-manager-ui/test September 30, 2025 12:54 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from fb4e481 to f5e0c94 Compare October 7, 2025 14:59

renovate bot had a problem deploying to data-manager-ui/test October 7, 2025 14:59 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f5e0c94 to 60a33ae Compare October 9, 2025 15:29

chore(deps): update dependency @sentry/nextjs to v10

fb0e878

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 60a33ae to fb0e878 Compare October 15, 2025 17:05

renovate bot had a problem deploying to data-manager-ui/test October 15, 2025 17:06 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency @sentry/nextjs to v10 #1564

chore(deps): update dependency @sentry/nextjs to v10 #1564

Uh oh!

renovate bot commented Feb 10, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

chore(deps): update dependency @sentry/nextjs to v10 #1564

Are you sure you want to change the base?

chore(deps): update dependency @sentry/nextjs to v10 #1564

Uh oh!

Conversation

renovate bot commented Feb 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Important Changes

Other Changes

Bundle size 📦

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Feb 10, 2025 •

edited

Loading