@sentry/react 11.7.0

on Node.js NPM

Important Changes

• feat(cloudflare): Add opt-in cron monitoring for Cron Triggers (#25014)

  The new cronTriggersIntegration sends check-ins for Cron Triggers. Each check-in includes the schedule from controller.cron, so Sentry creates the monitor on the first run. The integration is opt-in, because monitors are billed.

  Cron Triggers have no names, so map each cron expression of your wrangler config to a monitor slug. With the Sentry Cloudflare Vite plugin, add the integration to src/instrument.server.ts:

  // src/monitorSlugs.ts
  export const monitorSlugs: Record<string, string> = {
    '30 9 * * MON-FRI': 'daily-report',
  };
  
  // src/instrument.server.ts
  import * as Sentry from '@sentry/cloudflare';
  import { monitorSlugs } from './monitorSlugs';
  
  export default Sentry.defineCloudflareOptions(env => ({
    dsn: env.SENTRY_DSN,
    integrations: [Sentry.cronTriggersIntegration({ monitorSlug: cron => monitorSlugs[cron] })],
  }));
  
  // src/index.ts
  import { monitorSlugs } from './monitorSlugs';
  
  export default {
    async scheduled(controller, env) {
      switch (monitorSlugs[controller.cron]) {
        case 'daily-report':
          // Your daily report job
          break;
      }
    },
  };

  The monitorSlug function can also return monitor settings, for example { monitorSlug: 'daily-report', maxRuntime: 30 }, or undefined to send no check-ins for a trigger. Without monitorSlug, the SDK derives the slug from the cron expression. If you deploy with wrangler directly, pass the same integration to Sentry.withSentry.

• feat(node): Add neonIntegration for @neondatabase/serverless (#25164, #25176)

  The new neonIntegration creates db spans for queries of the @neondatabase/serverless driver: for the WebSocket Client and Pool, and for the HTTP neon() function. This includes the neon-http and neon-serverless adapters of Drizzle. The integration is on by default when tracing is enabled.

• feat(node): Stop sending the process session once request sessions are tracked (#24915)

  Node servers sent release health data two times: as request session aggregates, and as the process session of processSessionIntegration. An error in a request also marked the process session as errored, so the SDK counted the error two times. Now the SDK drops the process session when it tracks the first request session. Scripts, CLIs and workers that do not serve requests keep the process session, and so do servers with httpServerIntegration({ sessions: false }). This changes the release health numbers of Node servers, because they no longer send the errored or crashed update of the process session.

• feat(server-utils): Record decide calls as gen_ai.decide spans (#25270, #25272, #25274, #25281)

  Vercel AI experimental_decide calls, Mastra classifier evaluations, TypeSafe and LangChain Jev calls, and Workers AI calls to TypeSafe Jev and Cloudflare Clef models now create decide <model> spans with the op gen_ai.decide. Before, these spans had the op gen_ai.evaluate, which is now deprecated in the Sentry conventions. If you use gen_ai.evaluate in queries, alerts or dashboards, change it to gen_ai.decide.

• fix(browser): Apply urlQueryParams to more URLs (#25262, #25289)

  The dataCollection.urlQueryParams option now also filters the query parameters of these URLs:

  • the page URL in event.request.url
  • the browser.* and resource.* span names with traceLifecycle: 'static'
  • the LCP URL attributes lcp.url and browser.web_vital.lcp.url
  • the URLs in fetch, XHR and navigation breadcrumbs
  • the ui.element.url attribute of elementTimingIntegration

  Before this fix, these URLs could send sensitive query values, for example ?jwt=..., to Sentry.

• fix(nextjs): Apply top-level bundleSizeOptimizations to webpack and Turbopack builds (#24818)

  The top-level bundleSizeOptimizations option now removes unused SDK code in webpack and in Turbopack builds. Before, the tree-shaking options had no effect on Turbopack. The webpack.treeshake option is deprecated. It still works, but when you set both options, bundleSizeOptimizations takes precedence.

Other Changes

• feat(nuxt): Detect the server API with @nuxt/kit 4.6 (#25138)
• fix(bundler-plugins): Escape JSON in generated injection code (#25265)
• fix(core): Don't mark http client spans as errors when the caller aborts (#25260)
• fix(core): Record span client report outcomes when discarding transactions (#25006)
• fix(core): Record client outcomes when beforeSend callbacks return invalid values (#25049)
• fix(core): Record span outcomes for spans dropped when building a transaction (#25048)
• fix(core): Report actual item count in client reports of envelope send failures (#25185)
• fix(core): Strip internal custom span name from streamed spans (#25212)
• fix(nextjs): Filter query parameters in request error context (#25233)
• fix(node): Don't mark fetch spans as errors when the caller aborts (#25129)
• fix(nuxt): Delete public source maps before Nitro lists its public assets (#25267)
• fix(nuxt): Keep @sentry/server-runtime-injection external on Nitro v3 (#24901)
• fix(nuxt): Remove @opentelemetry/resources dev alias (#25216)
• fix(profiling-node): Stop the trace lifecycle profiler when spans are unsampled (#25210)
• fix(react-router): Respect custom default integrations (#25259)
• fix(remix): Respect custom default integrations (#25258)
• fix(server-utils): avoid quadratic SQL summary regex backtracking (#25255)
• fix(server-utils): End Express layer spans when the client aborts (#25209)
• fix(server-utils): Record amqplib consumer info before the first delivery and instrument the callback API (#25047)
• fix(server-utils): Stop treating previous_response_id as the OpenAI conversation id (#25269)
• fix(sveltekit): Read load event pathname untracked (#25235)
• fix(sveltekit): Stop adapter-node 6 output dir probe from deleting the build (#25193)

Work in this release was contributed by @Philip-Nwabuwa and @4ktLuffy. Thank you for your contributions!

Bundle size 📦