fix(deps): update sentry-javascript monorepo to v9 (major) #172

renovate · 2024-05-13T16:32:08Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/browser (source)	`7.120.3` -> `9.19.0`
@sentry/react (source)	`7.120.3` -> `9.19.0`

Release Notes

getsentry/sentry-javascript (@sentry/browser)

`v9.19.0`

Compare Source

feat(react-router): Add otel instrumentation for server requests (#16147)
feat(remix): Vendor in opentelemetry-instrumentation-remix (#16145)
fix(browser): Ensure spans auto-ended for navigations have cancelled reason (#16277)
fix(node): Pin @fastify/otel fork to direct url to allow installing without git (#16287)
fix(react): Handle nested parameterized routes in reactrouterv3 transaction normalization (#16274)

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

Bundle size 📦

Path	Size
@sentry/browser	23.4 KB
@sentry/browser - with treeshaking flags	23.06 KB
@sentry/browser (incl. Tracing)	37.31 KB
@sentry/browser (incl. Tracing, Replay)	74.53 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.72 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	79.19 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	91 KB
@sentry/browser (incl. Feedback)	39.8 KB
@sentry/browser (incl. sendFeedback)	28.03 KB
@sentry/browser (incl. FeedbackAsync)	32.79 KB
@sentry/react	25.17 KB
@sentry/react (incl. Tracing)	39.27 KB
@sentry/vue	27.67 KB
@sentry/vue (incl. Tracing)	39.07 KB
@sentry/svelte	23.43 KB
CDN Bundle	24.58 KB
CDN Bundle (incl. Tracing)	37.33 KB
CDN Bundle (incl. Tracing, Replay)	72.37 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.68 KB
CDN Bundle - uncompressed	71.72 KB
CDN Bundle (incl. Tracing) - uncompressed	110.5 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	221.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	234.31 KB
@sentry/nextjs (client)	40.88 KB
@sentry/sveltekit (client)	37.77 KB
@sentry/node	154.29 KB
@sentry/node - without tracing	95.6 KB
@sentry/aws-serverless	120.36 KB

`v9.18.0`

Compare Source

Important changes

feat: Support Node 24 (#16236)

We now also publish profiling binaries for Node 24.

Other changes

deps(node): Bump import-in-the-middle to 1.13.1 (#16260)
feat: Export consoleLoggingIntegration from vercel edge sdk (#16228)
feat(cloudflare): Add support for email, queue, and tail handler (#16233)
feat(cloudflare): Improve http span data (#16232)
feat(nextjs): Add more attributes for generation functions (#16214)
feat(opentelemetry): Widen peer dependencies to support Otel v2 (#16246)
fix(core): Gracefully handle invalid baggage entries (#16257)
fix(node): Ensure traces are propagated without spans in Node 22+ (#16221)
fix(node): Use sentry forked @fastify/otel dependency with pinned Otel v1 deps (#16256)
fix(remix): Remove vendored types (#16218)

Bundle size 📦

Path	Size
@sentry/browser	23.4 KB
@sentry/browser - with treeshaking flags	23.22 KB
@sentry/browser (incl. Tracing)	37.3 KB
@sentry/browser (incl. Tracing, Replay)	74.53 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	68.37 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	79.18 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.99 KB
@sentry/browser (incl. Feedback)	39.8 KB
@sentry/browser (incl. sendFeedback)	28.03 KB
@sentry/browser (incl. FeedbackAsync)	32.79 KB
@sentry/react	25.17 KB
@sentry/react (incl. Tracing)	39.26 KB
@sentry/vue	27.67 KB
@sentry/vue (incl. Tracing)	39.06 KB
@sentry/svelte	23.43 KB
CDN Bundle	24.58 KB
CDN Bundle (incl. Tracing)	37.33 KB
CDN Bundle (incl. Tracing, Replay)	72.37 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.67 KB
CDN Bundle - uncompressed	71.72 KB
CDN Bundle (incl. Tracing) - uncompressed	110.46 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	221.75 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	234.27 KB
@sentry/nextjs (client)	40.88 KB
@sentry/sveltekit (client)	37.76 KB
@sentry/node	155.42 KB
@sentry/node - without tracing	96 KB
@sentry/aws-serverless	121.5 KB

`v9.17.0`

Compare Source

feat(node): Migrate to @fastify/otel (#15542)

Bundle size 📦

Path	Size
@sentry/browser	23.35 KB
@sentry/browser - with treeshaking flags	23.19 KB
@sentry/browser (incl. Tracing)	37.25 KB
@sentry/browser (incl. Tracing, Replay)	74.47 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	68.34 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	79.12 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.93 KB
@sentry/browser (incl. Feedback)	39.75 KB
@sentry/browser (incl. sendFeedback)	27.98 KB
@sentry/browser (incl. FeedbackAsync)	32.74 KB
@sentry/react	25.16 KB
@sentry/react (incl. Tracing)	39.24 KB
@sentry/vue	27.63 KB
@sentry/vue (incl. Tracing)	39.01 KB
@sentry/svelte	23.38 KB
CDN Bundle	24.55 KB
CDN Bundle (incl. Tracing)	37.29 KB
CDN Bundle (incl. Tracing, Replay)	72.33 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.64 KB
CDN Bundle - uncompressed	71.62 KB
CDN Bundle (incl. Tracing) - uncompressed	110.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	221.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	234.15 KB
@sentry/nextjs (client)	40.84 KB
@sentry/sveltekit (client)	37.73 KB
@sentry/node	151.37 KB
@sentry/node - without tracing	95.77 KB
@sentry/aws-serverless	120.16 KB

`v9.16.1`

Compare Source

fix(core): Make sure logs get flushed in server-runtime-client (#16222)
ref(node): Remove vercel flushing code that does nothing (#16217)

`v9.16.0`

Compare Source

Important changes

feat: Create a Vite plugin that injects sentryConfig into the global config (#16197)

Add a new plugin makeConfigInjectorPlugin within our existing vite plugin that updates the global vite config with sentry options

feat(browser): Add option to sample linked traces consistently (#16037)

This PR implements consistent sampling across traces as outlined in (#15754)

feat(cloudflare): Add support for durable objects (#16180)

This PR introduces a new instrumentDurableObjectWithSentry method to the SDK, which instruments durable objects. We capture both traces and errors automatically.

feat(node): Add Prisma integration by default (#16073)

Prisma integration is enabled by default, it should work for both ESM and CJS.

feat(react-router): Add client-side router instrumentation (#16185)

Adds client-side instrumentation for react router's HydratedRouter. To enable it, simply replace browserTracingIntegration() with reactRouterTracingIntegration() in your client-side init call.

fix(node): Avoid double-wrapping http module (#16177)

When running your application in ESM mode, there have been scenarios that resulted in the http/https emitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.

In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now.
While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:

The ignoreOutgoingRequests option of httpIntegration receives the RequestOptions as second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:

ignoreOutgoingRequests(url: string, {
  method: string;
  protocol: string;
  host: string;
  hostname: string; // same as host
  path: string;
  headers: OutgoingHttpHeaders;
})

Other changes

feat(cloudflare): Add logs exports (#16165)
feat(vercel-edge): Add logs export (#16166)
feat(cloudflare): Read SENTRY_RELEASE from env (#16201)
feat(node): Drop http.server spans with 404 status by default (#16205)
fix(browser): Respect manually set sentry tracing headers in XHR requests (#16184)
fix(core): Respect manually set sentry tracing headers in fetch calls (#16183)
fix(feedback): Prevent removeFromDom() from throwing (#16030)
fix(node): Use class constructor in docstring for winston transport (#16167)
fix(node): Fix vercel flushing logic & add test for it (#16208)
fix(node): Fix 404 route handling in express 5 (#16211)
fix(logs): Ensure logs can be flushed correctly (#16216)
ref(core): Switch to standardized log envelope (#16133)

Bundle size 📦

Path	Size
@sentry/browser	23.35 KB
@sentry/browser - with treeshaking flags	23.19 KB
@sentry/browser (incl. Tracing)	37.25 KB
@sentry/browser (incl. Tracing, Replay)	74.47 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	68.34 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	79.12 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.93 KB
@sentry/browser (incl. Feedback)	39.75 KB
@sentry/browser (incl. sendFeedback)	27.98 KB
@sentry/browser (incl. FeedbackAsync)	32.74 KB
@sentry/react	25.16 KB
@sentry/react (incl. Tracing)	39.24 KB
@sentry/vue	27.63 KB
@sentry/vue (incl. Tracing)	39.01 KB
@sentry/svelte	23.38 KB
CDN Bundle	24.55 KB
CDN Bundle (incl. Tracing)	37.29 KB
CDN Bundle (incl. Tracing, Replay)	72.33 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.64 KB
CDN Bundle - uncompressed	71.62 KB
CDN Bundle (incl. Tracing) - uncompressed	110.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	221.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	234.15 KB
@sentry/nextjs (client)	40.84 KB
@sentry/sveltekit (client)	37.73 KB
@sentry/node	144.43 KB
@sentry/node - without tracing	96.3 KB
@sentry/aws-serverless	120.66 KB

`v9.15.0`

Compare Source

Important Changes

feat: Export wrapMcpServerWithSentry from server packages (#16127)

Exports the wrapMcpServerWithSentry which is our MCP server instrumentation from all the server packages.

feat(core): Associate resource/tool/prompt invocations with request span instead of response span (#16126)

Adds a best effort mechanism to associate handler spans for resource, tool and prompt with the incoming message requests instead of the outgoing SSE response.

Other Changes

fix: Vercel ai ESM patching (#16152)
fix(node): Update version range for module.register (#16125)
fix(react-router): Spread unstable_sentryVitePluginOptions correctly (#16156)
fix(react): Fix Redux integration failing with reducer injection (#16106)
fix(remix): Add ESM-compatible exports (#16124)
fix(remix): Avoid rewrapping root loader. (#16136)

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

Bundle size 📦

Path	Size
@sentry/browser	23.28 KB
@sentry/browser - with treeshaking flags	23.1 KB
@sentry/browser (incl. Tracing)	36.93 KB
@sentry/browser (incl. Tracing, Replay)	74.1 KB
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	67.47 KB
@sentry/browser (incl. Tracing, Replay with Canvas)	78.76 KB
@sentry/browser (incl. Tracing, Replay, Feedback)	90.58 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.93 KB
@sentry/vue	27.5 KB
@sentry/vue (incl. Tracing)	38.69 KB
@sentry/svelte	23.31 KB
CDN Bundle	24.49 KB
CDN Bundle (incl. Tracing)	36.96 KB
CDN Bundle (incl. Tracing, Replay)	72 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	77.3 KB
CDN Bundle - uncompressed	71.5 KB
CDN Bundle (incl. Tracing) - uncompressed	109.33 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	220.62 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	233.15 KB
@sentry/nextjs (client)	40.51 KB
@sentry/sveltekit (client)	37.41 KB
@sentry/node	143.4 KB
@sentry/node - without tracing	96.49 KB
@sentry/aws-serverless	120.81 KB

`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 a 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 Sent

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 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.

renovate bot added dependencies help wanted Extra attention is needed labels May 13, 2024

renovate bot had a problem deploying to production May 13, 2024 16:32 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from fa524ad to 7573344 Compare May 16, 2024 21:12

renovate bot had a problem deploying to production May 16, 2024 21:12 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 7573344 to 37345f9 Compare May 17, 2024 04:54

renovate bot had a problem deploying to production May 17, 2024 04:54 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 37345f9 to 63a9ca8 Compare May 17, 2024 21:52

renovate bot had a problem deploying to production May 17, 2024 21:52 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 63a9ca8 to b211bd5 Compare May 22, 2024 18:27

renovate bot had a problem deploying to production May 22, 2024 18:28 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from b211bd5 to 5863b04 Compare May 23, 2024 19:44

renovate bot had a problem deploying to production May 23, 2024 19:44 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 5863b04 to 419c238 Compare May 26, 2024 01:36

renovate bot had a problem deploying to production May 26, 2024 01:36 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 419c238 to d7dbc2f Compare May 27, 2024 19:54

renovate bot had a problem deploying to production May 27, 2024 19:54 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d7dbc2f to 60e3235 Compare May 29, 2024 16:37

renovate bot had a problem deploying to production May 29, 2024 16:37 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 60e3235 to ddf0ab1 Compare June 4, 2024 00:42

renovate bot had a problem deploying to production June 4, 2024 00:42 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from ddf0ab1 to 4eba19f Compare June 4, 2024 22:23

renovate bot had a problem deploying to production June 4, 2024 22:23 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 4eba19f to 1c20bfb Compare June 7, 2024 09:21

renovate bot had a problem deploying to production June 7, 2024 09:21 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 1c20bfb to 8856d85 Compare June 10, 2024 18:59

renovate bot had a problem deploying to production June 10, 2024 18:59 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 8856d85 to d4e141b Compare June 11, 2024 16:22

renovate bot had a problem deploying to production June 11, 2024 16:22 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from d4e141b to fb1b77c Compare June 12, 2024 10:54

renovate bot had a problem deploying to production March 19, 2025 11:06 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 8dd491e to 710ac4a Compare March 20, 2025 16:15

renovate bot had a problem deploying to production March 20, 2025 16:15 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 710ac4a to 59c244e Compare March 21, 2025 12:42

renovate bot had a problem deploying to production March 21, 2025 12:42 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 59c244e to f4223d8 Compare March 24, 2025 19:48

renovate bot had a problem deploying to production March 24, 2025 19:48 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f4223d8 to 2a08312 Compare March 27, 2025 20:23

renovate bot had a problem deploying to production March 27, 2025 20:23 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 2a08312 to 5a542f0 Compare March 28, 2025 16:10

renovate bot had a problem deploying to production March 28, 2025 16:10 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 5a542f0 to 06f93b7 Compare April 3, 2025 16:06

renovate bot had a problem deploying to production April 3, 2025 16:06 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 06f93b7 to e69127a Compare April 8, 2025 17:19

renovate bot had a problem deploying to production April 8, 2025 17:19 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from e69127a to 5659a82 Compare April 16, 2025 18:57

renovate bot had a problem deploying to production April 16, 2025 18:57 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 5659a82 to 9032863 Compare April 23, 2025 19:11

renovate bot had a problem deploying to production April 23, 2025 19:11 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 9032863 to f6beba2 Compare April 29, 2025 16:25

renovate bot had a problem deploying to production April 29, 2025 16:25 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from f6beba2 to 636ff88 Compare May 7, 2025 19:59

renovate bot had a problem deploying to production May 7, 2025 19:59 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 636ff88 to 748f6fa Compare May 8, 2025 16:06

renovate bot had a problem deploying to production May 8, 2025 16:06 Failure

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 748f6fa to 3bcc32e Compare May 13, 2025 12:11

renovate bot had a problem deploying to production May 13, 2025 12:11 Failure

fix(deps): update sentry-javascript monorepo to v9

4d41ea8

renovate bot force-pushed the renovate/major-sentry-javascript-monorepo branch from 3bcc32e to 4d41ea8 Compare May 14, 2025 15:32

renovate bot had a problem deploying to production May 14, 2025 15:32 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update sentry-javascript monorepo to v9 (major) #172

fix(deps): update sentry-javascript monorepo to v9 (major) #172

Uh oh!

renovate bot commented May 13, 2024 •

edited

Loading

Uh oh!

Uh oh!

fix(deps): update sentry-javascript monorepo to v9 (major) #172

Are you sure you want to change the base?

fix(deps): update sentry-javascript monorepo to v9 (major) #172

Uh oh!

Conversation

renovate bot commented May 13, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Bundle size 📦

Important changes

Other changes

Bundle size 📦

Bundle size 📦

Important changes

Other changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Bundle size 📦

Important Changes

Other Changes

Important Changes

Other Changes

Configuration

Uh oh!

Uh oh!

renovate bot commented May 13, 2024 •

edited

Loading