Update sentry-javascript monorepo to v9 (major) #20451

renovate · 2024-06-24T12:41:19Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/ember (source)	`7.120.3` -> `9.14.0`
@sentry/node (source)	`7.120.3` -> `9.14.0`
@sentry/react (source)	`7.120.3` -> `9.14.0`

Release Notes

getsentry/sentry-javascript (@sentry/ember)

`v9.14.0`

Compare Source

Important Changes

feat: Add Supabase Integration (#15719)

This PR adds Supabase integration to @sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.

feat(nestjs): Gracefully handle RPC scenarios in SentryGlobalFilter (#16066)

This PR adds better RPC exception handling to @sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type in SentryGlobalFilter to improve reliability in hybrid applications.

feat(react-router): Trace propagation (#16070)

This PR adds trace propagation to @sentry/react-router by providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.

Other Changes

feat(deps): Bump @prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
feat(nextjs): Improve server component data (#15996)
feat(nuxt): Log when adding HTML trace meta tags (#16044)
fix(node): Make body capturing more robust (#16105)
ref(node): Log when incoming request bodies are being captured (#16104)

Bundle size 📦

Path	Size
@sentry/browser	23.28 KB
@sentry/browser - with treeshaking flags	23.12 KB
@sentry/browser (incl. Tracing)	36.99 KB
@sentry/browser (incl. Tracing, Replay)	74.17 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.55 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.83 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.65 KB
@sentry/browser (incl. Feedback)	39.68 KB
@sentry/browser (incl. sendFeedback)	27.9 KB
@sentry/browser (incl. FeedbackAsync)	32.67 KB
@sentry/react	25.09 KB
@sentry/react (incl. Tracing)	38.91 KB
@sentry/vue	27.51 KB
@sentry/vue (incl. Tracing)	38.71 KB
@sentry/svelte	23.32 KB
CDN Bundle	24.5 KB
CDN Bundle (incl. Tracing)	36.98 KB
CDN Bundle (incl. Tracing, Replay)	72 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.16 KB
CDN Bundle - uncompressed	71.49 KB
CDN Bundle (incl. Tracing) - uncompressed	109.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	220.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	233.16 KB
@sentry/nextjs (client)	40.54 KB
@sentry/sveltekit (client)	37.44 KB
@sentry/node	143.37 KB
@sentry/node - without tracing	96.51 KB
@sentry/aws-serverless	120.83 KB

`v9.13.0`

Compare Source

Important Changes

feat(node): Add support for winston logger (#15983)

Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like @sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.
```
const winston = require('winston');
const Transport = require('winston-transport');

const transport = Sentry.createSentryWinstonTransport(Transport);

const logger = winston.createLogger({
  transports: [transport],
});
```

feat(core): Add wrapMcpServerWithSentry to instrument MCP servers from @modelcontextprotocol/sdk (#16032)

The Sentry SDK now supports instrumenting MCP servers from the @modelcontextprotocol/sdk package. Compatible with versions ^1.9.0 of the @modelcontextprotocol/sdk package.

import { McpServer } from '@&#8203;modelcontextprotocol/sdk/server/mcp.js';

// Create an MCP server
const server = new McpServer({
  name: 'Demo',
  version: '1.0.0',
});

// Use the instrumented server in your application
const instrumentedServer = Sentry.wrapMcpServerWithSentry(server);

feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)

Console instrumentation has been added to @sentry/cloudflare and @sentry/nextjs Edge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.
feat(bun): Support new Bun.serve APIs (#16035)

Bun 1.2.6 and above have a new Bun.serve API, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.

Thanks to @Jarred-Sumner for helping us get this supported!

Other Changes

feat(browser): Warn on duplicate browserTracingIntegration (#16042)
feat(core): Allow delayed sending with offline transport (#15937)
feat(deps): Bump @sentry/webpack-plugin from 3.2.4 to 3.3.1 (#16057)
feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#16034)
fix(core): Run beforeSendLog after we process log (#16019)
fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#16065)
fix(nextjs): Include patch version 0 for min supported 15.3.0 (#16026)
fix(node): Ensure late init works with all integrations (#16016)
fix(react-router): Pass unstable_sentryVitePluginOptions to cli instance (#16033)
fix(serverless-aws): Overwrite root span name with GraphQL if set (#16010)

`v9.12.0`

Compare Source

`v9.11.0`

Compare Source

feat(browser): Add http.redirect_count attribute to browser.redirect span (#15943)
feat(core): Add consoleLoggingIntegration for logs (#15955)
feat(core): Don't truncate error messages (#15818)
feat(nextjs): Add release injection in Turbopack (#15958)
feat(nextjs): Record turbopack as tag (#15928)
feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#15859)
feat(react-router): Add sentryHandleRequest (#15787)
fix(node): Use module instead of require for CJS check (#15927)
fix(remix): Remove mentions of deprecated ErrorBoundary wrapper (#15930)
ref(browser): Temporarily add sentry.previous_trace span attribute (#15957)
ref(browser/core): Move all log flushing logic into clients (#15831)
ref(core): Improve URL parsing utilities (#15882)

Bundle size 📦

Path	Size
@sentry/browser	23.2 KB
@sentry/browser - with treeshaking flags	23.02 KB
@sentry/browser (incl. Tracing)	36.83 KB
@sentry/browser (incl. Tracing, Replay)	73.99 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.39 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.66 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	91.22 KB
@sentry/browser (incl. Feedback)	40.33 KB
@sentry/browser (incl. sendFeedback)	27.83 KB
@sentry/browser (incl. FeedbackAsync)	32.63 KB
@sentry/react	25 KB
@sentry/react (incl. Tracing)	38.75 KB
@sentry/vue	27.41 KB
@sentry/vue (incl. Tracing)	38.55 KB
@sentry/svelte	23.23 KB
CDN Bundle	24.44 KB
CDN Bundle (incl. Tracing)	36.85 KB
CDN Bundle (incl. Tracing, Replay)	71.87 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.07 KB
CDN Bundle - uncompressed	71.24 KB
CDN Bundle (incl. Tracing) - uncompressed	108.94 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	220.23 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	232.8 KB
@sentry/nextjs (client)	40.06 KB
@sentry/sveltekit (client)	37.26 KB
@sentry/node	142.88 KB
@sentry/node - without tracing	96.08 KB
@sentry/aws-serverless	120.43 KB

`v9.10.1`

Compare Source

fix: Correct @sentry-internal/feedback docs to match the code (#15874)
deps: Bump bundler plugins to version 3.2.4 (#15909)

`v9.10.0`

Compare Source

Important Changes

feat: Add support for logs

feat(node): Add logging public APIs to Node SDKs (#15764)
feat(core): Add support for beforeSendLog (#15814)
feat(core): Add support for parameterizing logs (#15812)
fix: Remove critical log severity level (#15824)

All JavaScript SDKs other than @sentry/cloudflare and @sentry/deno now support sending logs via dedicated methods as part of Sentry's upcoming logging product.

Logging is gated by an experimental option, _experiments.enableLogs.

Sentry.init({
  dsn: 'PUBLIC_DSN',
  // `enableLogs` must be set to true to use the logging features
  _experiments: { enableLogs: true },
});

const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;

trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });

// Structured logging via the `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry.

info(fmt(`Updated profile for user ${userId}`));
warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));

With server-side SDKs like @sentry/node, @sentry/bun or server-side of @sentry/nextjs or @sentry/sveltekit, you can do structured logging without needing the fmt helper function.

const { info, warn } = Sentry.logger;

info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });

To filter logs, or update them before they are sent to Sentry, you can use the _experiments.beforeSendLog option.

feat(browser): Add diagnoseSdkConnectivity() function to programmatically detect possible connectivity issues (#15821)

The diagnoseSdkConnectivity() function can be used to programmatically detect possible connectivity issues with the Sentry SDK.
```
const result = await Sentry.diagnoseSdkConnectivity();
```
The result will be an object with the following properties:
- "no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet.
- "sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.
- undefined: The SDK is working as expected.
SDK Tracing Performance Improvements for Node SDKs
- feat: Stop using dropUndefinedKeys (#15796)
- feat(node): Only add span listeners for instrumentation when used (#15802)
- ref: Avoid dropUndefinedKeys for spanToJSON calls (#15792)
- ref: Avoid using SentryError for PromiseBuffer control flow (#15822)
- ref: Stop using dropUndefinedKeys in SpanExporter (#15794)
- ref(core): Avoid using SentryError for event processing control flow (#15823)
- ref(node): Avoid dropUndefinedKeys in Node SDK init (#15797)
- ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
We've been hard at work making performance improvements to the Sentry Node SDKs (@sentry/node, @sentry/aws-serverless, @sentry/nestjs, etc.). We've seen that upgrading from 9.7.0 to 9.10.0 leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.

Other Changes

chore(deps): Bump rrweb to 2.35.0 (#15825)
deps: Bump bundler plugins to 3.2.3 (#15829)
feat: Always truncate stored breadcrumb messages to 2kb (#15819)
feat(nextjs): Disable server webpack-handling for static builds (#15751)
fix(nuxt): Don't override Nuxt options if undefined (#15795)

`v9.9.0`

Compare Source

Important Changes

feat(nextjs): Support instrumentation-client.ts (#15705)

Next.js recently added a feature to support client-side (browser) instrumentation via the experimental.clientInstrumentationHook flag and the instrumentation-client.ts file.

To be forwards compatible, the Sentry Next.js SDK will now pick up instrumentation-client.ts files even on older Next.js versions and add them to your client bundles.
It is suggested that you either rename your sentry.client.config.ts file to instrumentation-client.ts, or if you already happen to have a instrumentation-client.ts file move the contents of sentry.client.config.ts to instrumentation-client.ts.

feat(browser): Add previous_trace span links (#15569)

The @sentry/browser SDK and SDKs based on @sentry/browser now emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option in browserTracingIntegration():

Sentry.init({
  dsn: 'your-dsn-here'
  integrations: [
    Sentry.browserTracingIntegration({
      // Available settings:
      // - 'in-memory' (default): Stores previous trace information in memory
      // - 'session-storage': Stores previous trace information in the browser's `sessionStorage`
      // - 'off': Disable storing and sending previous trace information
      linkPreviousTrace: 'in-memory',
    }),
  ],
});

feat(browser): Add logger.X methods to browser SDK (#15763)

For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.

Sentry.init({
  dsn: 'your-dsn-here',
  _experiments: {
    enableLogs: true, // This is required to use the logging features
  },
});

Sentry.logger.info('This is a trace message', { userId: 123 });
// See PR for better documentation

Please note that the logs product is still in early access. See the link above for more information.

Other Changes

feat(browser): Attach host as part of error message to "Failed to fetch" errors (#15729)
feat(core): Add parseStringToURL method (#15768)
feat(core): Optimize dropUndefinedKeys (#15760)
feat(node): Add fastify shouldHandleError (#15771)
fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
perf(nestjs): Remove usage of addNonEnumerableProperty (#15766)
ref: Avoid some usage of dropUndefinedKeys() (#15757)
ref: Remove some usages of dropUndefinedKeys() (#15781)
ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)

`v9.8.0`

Compare Source

feat(node): Implement new continuous profiling API spec (#15635)
feat(profiling): Add platform to chunk envelope (#15758)
feat(react): Export captureReactException method (#15746)
fix(node): Check for res.end before passing to Proxy (#15776)
perf(core): Add short-circuits to eventFilters integration (#15752)
perf(node): Short circuit flushing on Vercel only for Vercel (#15734)

`v9.7.0`

Compare Source

feat(core): Add captureLog method (#15717)
feat(remix/cloudflare): Export sentryHandleError (#15726)
fix(node): Always flush on Vercel before Lambda freeze (#15602)
fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
fix(node): Use fatal level for unhandled rejections in strict mode (#15720)
fix(nuxt): Delete Nuxt server template injection (#15749)

`v9.6.1`

Compare Source

feat(deps): bump @prisma/instrumentation from 6.4.1 to 6.5.0 (#15714)
feat(deps): bump @sentry/cli from 2.42.2 to 2.42.3 (#15711)
fix(nextjs): Re-patch router if it is overridden by Next.js (#15721)
fix(nuxt): Add Nitro Rollup plugin to inject Sentry server config (#15710)
chore(deps): Bump rollup to 4.35.0 (#15651)

`v9.6.0`

Compare Source

Important Changes

feat(tanstackstart): Add @sentry/tanstackstart-react package and make @sentry/tanstackstart package a utility package (#15629)

Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the @sentry/tanstackstart SDK package was renamed to @sentry/tanstackstart-react to reflect that the SDK is specifically intended to be used for React TanStack Start applications.
Note that the TanStack Start SDK is still in alpha status and may be subject to breaking changes in non-major package updates.

Other Changes

feat(astro): Accept all vite-plugin options (#15638)
feat(deps): bump @sentry/webpack-plugin from 3.2.1 to 3.2.2 (#15627)
feat(tanstackstart): Refine initial API (#15574)
fix(core): Ensure fill only patches functions (#15632)
fix(nextjs): Consider pageExtensions when looking for instrumentation file (#15701)
fix(remix): Null-check options (#15610)
fix(sveltekit): Correctly parse angle bracket type assertions for auto instrumentation (#15578)
fix(sveltekit): Guard process variable (#15605)

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

`v9.5.0`

Compare Source

Important Changes

We found some issues with the new feedback screenshot annotation where screenshots are not being generated properly. Due to this issue, we are reverting the feature.

Revert "feat(feedback) Allowing annotation via highlighting & masking (#15484)" (#15609)

Other Changes

Add cloudflare adapter detection and path generation (#15603)
deps(nextjs): Bump rollup to 4.34.9 (#15589)
feat(bun): Automatically add performance integrations (#15586)
feat(replay): Bump rrweb to 2.34.0 (#15580)
fix(browser): Call original function on early return from patched history API (#15576)
fix(nestjs): Copy metadata in custom decorators (#15598)
fix(react-router): Fix config type import (#15583)
fix(remix): Use correct types export for @sentry/remix/cloudflare (#15599)
fix(vue): Attach Pinia state only once per event (#15588)

Work in this release was contributed by @msurdi-a8c, @namoscato, and @rileyg98. Thank you for your contributions!

`v9.4.0`

Compare Source

feat(core): Add types for logs protocol and envelope (#15530)
feat(deps): Bump @sentry/cli from 2.41.1 to 2.42.2 (#15510)
feat(deps): Bump @sentry/webpack-plugin from 3.1.2 to 3.2.1 (#15512)
feat(feedback) Allowing annotation via highlighting & masking (#15484)
feat(nextjs): Add use client directive to client SDK entrypoints (#15575)
feat(nextjs): Allow silencing of instrumentation warning (#15555)
feat(sveltekit): Ensure AsyncLocalStorage async context strategy is used in Cloudflare Pages (#15557)
fix(cloudflare): Make @cloudflare/workers-types an optional peer dependency (#15554)
fix(core): Don't reverse values in event filters (#15584)
fix(core): Handle normalization of null prototypes correctly (#15556)
fix(nextjs): Only warn on missing onRequestError in version 15 (#15553)
fix(node): Allow for undefined transport to be passed in (#15560)
fix(wasm): Fix wasm integration stacktrace parsing for filename (#15572)
perf(node): Store normalized request for processing (#15570)

Bundle size 📦

Path	Size
@sentry/browser	23.13 KB
@sentry/browser - with treeshaking flags	22.92 KB
@sentry/browser (incl. Tracing)	36.2 KB
@sentry/browser (incl. Tracing, Replay)	73.38 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.79 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	77.99 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	89.91 KB
@sentry/browser (incl. Feedback)	39.66 KB
@sentry/browser (incl. sendFeedback)	27.76 KB
@sentry/browser (incl. FeedbackAsync)	32.54 KB
@sentry/react	24.95 KB
@sentry/react (incl. Tracing)	38.08 KB
@sentry/vue	27.38 KB
@sentry/vue (incl. Tracing)	37.89 KB
@sentry/svelte	23.17 KB
CDN Bundle	24.34 KB
CDN Bundle (incl. Tracing)	36.24 KB
CDN Bundle (incl. Tracing, Replay)	71.25 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	76.41 KB
CDN Bundle - uncompressed	71.12 KB
CDN Bundle (incl. Tracing) - uncompressed	107.51 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.31 KB
@sentry/nextjs (client)	39.25 KB
@sentry/sveltekit (client)	36.61 KB
@sentry/node	142.14 KB
@sentry/node - without tracing	95.57 KB
@sentry/aws-serverless	119.92 KB

`v9.3.0`

Compare Source

Important Changes

With this release we're publishing two new SDKs in experimental alpha stage:

feat(tanstackstart): Add TanStack Start SDK (#15523)

For details please refer to the README

feat(react-router): Add React Router SDK (#15524)

For details please refer to the README

feat(remix): Add support for Hydrogen (#15450)

This PR adds support for Shopify Hydrogen applications running on MiniOxygen runtime.

Other Changes

feat(core): Add forceTransaction to trpc middleware options (#15519)
feat(core): Default filter unactionable error (#15527)
feat(core): Rename inboundFiltersIntegration to eventFiltersIntegration (#15434)
feat(deps): bump @prisma/instrumentation from 6.2.1 to 6.4.1 (#15480)
feat(react-router): Add build-time config (#15406)
feat(replay): Bump rrweb to 2.33.0 (#15514)
fix(core): Fix allowUrls and denyUrls for linked and aggregate exceptions (#15521)
fix(nextjs): Don't capture devmode server-action redirect errors (#15485)
fix(nextjs): warn about missing onRequestError handler #15488)
fix(nextjs): Prevent wrong culprit from showing up for clientside error events #15475)
fix(nuxt): Ignore 300-400 status codes on app errors in Nuxt (#15473)
fix(react): Add support for cross-usage of React Router instrumentations (#15283)
fix(sveltekit): Guard process check when flushing events (#15516)

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

`v9.2.0`

Compare Source

Important Changes

feat(node): Support Express v5 (#15380)

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

feat(sveltekit): Add Support for Cloudflare (#14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages.
A docs update with updated instructions will follow shortly.
Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.

Thank you @SG60 for contributing this feature!

Other Changes

feat(core): Add addLink(s) to Sentry span (#15452)
feat(core): Add links to span options (#15453)
feat(deps): Bump @sentry/webpack-plugin from 2.22.7 to 3.1.2 (#15328)
feat(feedback): Disable Feedback submit & cancel buttons while submitting (#15408)
feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#15418)
feat(nuxt): Add enableNitroErrorHandler to server options (#15444)
feat(opentelemetry): Add addLink(s) to span (#15387)
feat(opentelemetry): Add links to span options (#15403)
feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#14916)
fix(browser): Ensure that performance.measure spans have a positive duration (#15415)
fix(bun): Includes correct sdk metadata (#15459)
fix(core): Add Google gmo error to Inbound Filters (#15432)
fix(core): Ensure http.client span descriptions don't contain query params or fragments (#15404)
fix(core): Filter out unactionable Facebook Mobile browser error (#15430)
fix(nestjs): Pin dependency on @opentelemetry/instrumentation (#15419)
fix(nuxt): Only use filename with file extension from command (#15445)
fix(nuxt): Use SentryNuxtServerOptions type for server init (#15441)
fix(sveltekit): Avoid loading vite config to determine source maps setting (#15440)
ref(profiling-node): Bump chunk interval to 60s (#15361)

Work in this release was contributed by @6farer, @dgavranic and @SG60. Thank you for your contributions!

Bundle size 📦

Path	Size
@sentry/browser	23.05 KB
@sentry/browser - with treeshaking flags	22.84 KB
@sentry/browser (incl. Tracing)	36.13 KB
@sentry/browser (incl. Tracing, Replay)	73.14 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	66.6 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	77.39 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.34 KB
@sentry/browser (incl. Feedback)	40.2 KB
@sentry/browser (incl. sendFeedback)	27.68 KB
@sentry/browser (incl. FeedbackAsync)	32.48 KB
@sentry/react	24.87 KB
@sentry/react (incl. Tracing)	38.01 KB
@sentry/vue	27.29 KB
@sentry/vue (incl. Tracing)	37.81 KB
@sentry/svelte	23.09 KB
CDN Bundle	24.25 KB
CDN Bundle (incl. Tracing)	36.15 KB
CDN Bundle (incl. Tracing, Replay)	71 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	76.17 KB
CDN Bundle - uncompressed	70.91 KB
CDN Bundle (incl. Tracing) - uncompressed	107.29 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.57 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.13 KB
@sentry/nextjs (client)	39.16 KB
@sentry/sveltekit (client)	36.54 KB
@sentry/node	129.25 KB
@sentry/node - without tracing	98.03 KB
@sentry/aws-serverless	107.45 KB

`v9.1.0`

Compare Source

feat(browser): Add graphqlClientIntegration (#13783)
feat(core): Allow for nested trpc context (#15379)
feat(core): Create types and utilities for span links (#15375)
feat(deps): bump @opentelemetry/instrumentation-pg from 0.50.0 to 0.51.0 (#15273)
feat(node): Extract Sentry-specific node-fetch instrumentation (#15231)
feat(vue): Support Pinia v3 (#15383)
fix(sveltekit): Avoid request body double read errors (#15368)
fix(sveltekit): Avoid top-level vite import (#15371)

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

`v9.0.1`

Compare Source

ref(flags): rename unleash integration param (#15343)

`v9.0.0`

Compare Source

Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9.
Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/

A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes

doc(deno)!: Make Deno v2 the minimum supported version (#15085)
feat!: Bump typescript to ~5.0.0 (#14758)
feat!: Drop nitro-utils package (#14998)
feat!: Only collect ip addresses with sendDefaultPii: true (#15084)
feat!: Remove autoSessionTracking option (#14802)
feat!: Remove enableTracing (#15078)
feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#15122)
feat!: Remove spanId from propagation context (#14733)
feat!: Remove deprecated and unused code (#15077)
feat!: Remove metrics API from the JS SDK (#14745)
feat!: Require Node >=18 as minimum supported version (#14749)
feat(astro)!: Respect user-specified source map setting (#14941)
feat(browser)!: Remove captureUserFeedback method (#14820)
feat(build)!: Drop pre-ES2020 polyfills (#14882)
feat(core)!: Add normalizedRequest to samplingContext (#14902)
feat(core)!: Always use session from isolation scope (#14860)
feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#14831)
feat(core)!: Remove BAGGAGE_HEADER_NAME export (#14785)
feat(core)!: Remove TransactionNamingScheme type (#14865)
feat(core)!: Remove addOpenTelemetryInstrumentation method ([

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 05:00 PM and 11:59 PM, only on Friday ( * 17-23 * * 5 ), Only on Sunday and Saturday ( * * * * 0,6 ), Between 12:00 AM and 12:59 PM, only on Monday ( * 0-12 * * 1 ) (UTC).

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

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

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

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

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

coderabbitai · 2025-04-01T13:12:09Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

github-actions bot added affects:admin Anything relating to Ghost Admin affects:portal labels Jun 24, 2024

ErisDS added the browser-tests label Apr 1, 2025

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 933e64f to 12a5e82 Compare April 2, 2025 13:33

renovate bot changed the title ~~Update sentry-javascript monorepo to v8 (major)~~ Update sentry-javascript monorepo to v9 (major) Apr 2, 2025

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 12a5e82 to 01ad274 Compare April 21, 2025 07:01

Update sentry-javascript monorepo to v9

1170bec

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 01ad274 to 1170bec Compare April 25, 2025 20:40

ErisDS added the requires changes [triage] Dependency updates that require code changes label Apr 25, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update sentry-javascript monorepo to v9 (major) #20451

Update sentry-javascript monorepo to v9 (major) #20451

renovate bot commented Jun 24, 2024 •

edited

Loading

coderabbitai bot commented Apr 1, 2025 •

edited

Loading

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Update sentry-javascript monorepo to v9 (major) #20451

Are you sure you want to change the base?

Update sentry-javascript monorepo to v9 (major) #20451

Conversation

renovate bot commented Jun 24, 2024 • edited Loading

Release Notes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Bundle size 📦

How To Upgrade

Breaking Changes

Configuration

coderabbitai bot commented Apr 1, 2025 • edited Loading

Review skipped

Chat

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

renovate bot commented Jun 24, 2024 •

edited

Loading

coderabbitai bot commented Apr 1, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)