Packages

@sentry/node-core

10.75.2 · 22 Sep 2026MIT23.4M / weekRepositoryHomepagenpmAtom feed

Your version

102 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 10.77.1

    27 Oct 2026

    Reading the note…

  2. 10.76.2

    8 Oct 2026

    Reading the note…

  3. 10.76.1

    6 Oct 2026

    Reading the note…

  4. 10.76.0

    2 Oct 2026

    Reading the note…

  5. 10.75.3

    23 Sep 2026

    Reading the note…

  6. 10.75.2

    22 Sep 2026

    • v10/cloudflare: Enforce flush timeout across Workflow lifecycle

    • v10/core: Apply dataCollection.urlQueryParams to collected URLs and query strings

    • v10/nextjs: Align tunnel request matching in middleware with tunnel rewrite

  7. 10.75.1

    21 Sep 2026

    • v10/cloudflare: Capture telemetry from untraced Durable Object RPC calls

    • v10/cloudflare: Instrument namespaces returned by jurisdiction()

    • v10/hono: Allow @cloudflare/workers-types v5 as peer dependency

  8. 10.75.0

    16 Sep 2026

    • v10/effect: Capture errors through the Effect v4 ErrorReporter API

      On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.

    • v10/core: Accept a CollectBehavior shorthand for dataCollection.httpHeaders

    • v10/browser: Release the XHR virtualError once the request completed

  9. 10.74.0

    9 Sep 2026

    • v10: Streamline isolation scope handling & reset in isolation scopes

    • server-utils: Include Gemini reasoning tokens in Vercel AI token usage

    • v10/browser: Set user_agent.original on all spans for consistent filtering

  10. 10.73.0

    31 Aug 2026
    • deprecated

      v10/node: Deprecate shouldHandleError on setupExpressErrorHandler and setupFasitfyErrorHandler

    • v10/nextjs: Add @sentry/nextjs/config entry point

      withSentryConfig is now available from @sentry/nextjs/config, the path it moves to in v11. Importing it from @sentry/nextjs still works on v10 but logs a warning once, so you can change your next.config file today and upgrade to v11 without touching it again.

      // next.config.mjs
- import { withSentryConfig } from '@sentry/nextjs';
+ import { withSentryConfig } from '@sentry/nextjs/config';

    • v10/cloudflare: Instrument Durable Object handlers installed as read-only properties

  11. 10.72.0

    28 Aug 2026

    • AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)

      Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.

    • v10/cloudflare: Add rpcTracePropagationBindings (#23737, #23738)

      The new rpcTracePropagationBindings option names the env bindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence over enableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.

    • v10/astro: Support astro v7 route patterns properly

  12. 10.71.0

    24 Aug 2026
    • breaking

      v10/core: Enable logs by default

    • deprecated

      v10/core: Deprecate scope.clear() method

    • v10/core: Bound child span tracking on long-lived spans

  13. 10.70.0

    10 Aug 2026

    • v10/core: Support stable MCP SDK v2

    • v10/solid,solidstart: Support @solidjs/router v1

    • v10/cloudflare: Fork the isolation scope for Durable Object methods

  14. 10.69.0

    29 Jul 2026

    • v10/cloudflare: Add instrumentAgentWithSentry for Cloudflare Agents

    • v10/cloudflare: Add Spotlight integration for local dev event forwarding

    • v10/cloudflare: Add wranglerConfigPath to Vite options

  15. 10.68.0

    24 Jul 2026

    • cloudflare: Add @sentry/cloudflare/vite orchestrion plugin

    • nestjs: Support WebSocket errors in SentryGlobalFilter

    • node,server-utils: Set cache.key on dataloader spans and capture redis delete operations as cache.remove

  16. 10.67.0

    20 Jul 2026

    • effect: Capture errors through the Effect v4 ErrorReporter API

      On Effect v4, Sentry.effectLayer now registers a Sentry ErrorReporter. Failures that pass through Effect.withErrorReporting, ErrorReporter.report or the built-in HTTP and RPC reporting boundaries are captured automatically, with ErrorReporter.ignore, ErrorReporter.severity and ErrorReporter.attributes annotations respected. Nothing changes on Effect v3.

      The server SDK now enables the contextLines and linkedErrors integrations by default, so captured errors carry source context and their cause chain. No other Node default integration is enabled.

    • sveltekit: Add support for SvelteKit 3

      The SvelteKit SDK now supports the pre-release of SvelteKit 3, including client-side pageload and navigation tracing and server-side native tracing, alongside continued SvelteKit 2 support. No Sentry-specific setup changes are required. The SDK detects your SvelteKit version and picks the right implementation automatically.

    • aws-serverless: Use orchestrion aws-sdk integration under diagnostics-channel opt-in

  17. 10.66.0

    16 Jul 2026
    • deprecated

      node-core: Deprecate @sentry/node-core package

    • deprecated

      tanstackstart: Deprecate @sentry/tanstackstart package

    • bun: Add initWithoutDefaultIntegrations and getDefaultIntegrationsWithoutPerformance

  18. 10.65.0

    10 Jul 2026

    • angular: Set url attributes on pageload and navigation spans

    • astro: Set url.template on pageload spans

    • aws-serverless: Replace OTel Lambda instrumentation with handler redirection

  19. 10.64.0

    7 Jul 2026

    • cloudflare: Add nodejs_compat entrypoint

      The Cloudflare SDK now ships a dedicated @sentry/cloudflare/nodejs_compat entrypoint for Workers running with the nodejs_compat flag. This entrypoint unlocks Node SDK features on Cloudflare, including the prismaIntegration (#21882) and AI v7 support for the vercelAiIntegration (#21917).

      This entrypoint is a drop-in replacement, so you can switch your imports from @sentry/cloudflare directly to @sentry/cloudflare/nodejs_compat. To use it, your Worker must set the nodejs_compat compatibility flag in wrangler.toml/wrangler.jsonc. This will become the default entrypoint in v11.

    • Use Sentry's minimal OpenTelemetry tracer provider by default (#21666, #21680, #21842)

      The Node SDK now registers Sentry's own minimal SentryTracerProvider by default, which creates native Sentry spans directly instead of routing them through the full OpenTelemetry SDK span pipeline. This reduces overhead for the common case where you don't need the full OpenTelemetry tracing stack.

      If you rely on OpenTelemetry SDK features that the minimal provider doesn't support, you can opt out and fall back to the full OpenTelemetry BasicTracerProvider by setting openTelemetryBasicTracerProvider: true in your Sentry.init() options. Providing custom openTelemetrySpanProcessors also forces the full provider automatically.

    • bun,deno,node: Pg orchestrion instrumentation

  20. 10.63.0

    1 Jul 2026

    • browser: Add url.full attribute to resource spans

    • core: Add extendIntegration method

    • core: Add isTracingSuppressed to the async context strategy

  21. 10.62.0

    26 Jun 2026

    • server-runtimes: Add v7 support for vercelAiIntegration

      The vercelAiIntegration now supports v7 of the ai package. Note that v7 is not yet supported on Cloudflare.

    • node: Avoid failing at runtime if tracingChannel is not available

    • sveltekit: Avoid capturing preloaded 400 errors on client

  22. 10.61.0

    25 Jun 2026

    • core: Enable streamGenAiSpans by default

      The SDK now extracts all gen_ai spans out of a transaction and sends them as v2 envelope items by default. This prevents gen_ai spans from being dropped when the transaction payload exceeds size limits. Because they are no longer constrained by transaction size limits, AI message data is also no longer truncated by default. Set enableTruncation: true on the respective AI integration to re-enable truncation. To keep the previous behavior, set streamGenAiSpans: false.

      Self-hosted Sentry users should opt out with streamGenAiSpans: false, since streamed gen_ai spans may not be ingested by their Sentry instance.

    • cloudflare: Add batch, exec, and withSession D1 instrumentation

    • cloudflare: Instrument SQL API in sqlite durable objects

  23. 10.60.0

    23 Jun 2026

    • cloudflare: Add R2 bucket auto-instrumentation

    • core: Add bindScopeToEmitter to bind a scope to an event emitter

    • browser: Ensure url.full and http.url attributes have the same values on http.client spans

  24. 10.59.0

    19 Jun 2026

    • react-router: Add support for React Router v8

      The SDK now supports React Router v8, in both the framework and SPA (@sentry/react) modes.

    • react: Add version-agnostic React Router SPA exports

      @sentry/react now exports version-agnostic wrappers for React Router v6+ SPA instrumentation. The new exports replace the version-specific V6/V7 variants, which are now deprecated:

      DeprecatedNew
      reactRouterV6BrowserTracingIntegration / V7reactRouterBrowserTracingIntegration
      withSentryReactRouterV6Routing / V7wrapReactRouterRouting
      wrapCreateBrowserRouterV6 / V7wrapCreateBrowserRouter
      wrapCreateMemoryRouterV6 / V7wrapCreateMemoryRouter
      wrapUseRoutesV6 / V7wrapUseRoutes

      The deprecated exports continue to work and will be removed in the next major version.

    • aws-serverless: Instrument aws-sdk clients >= 3.1046.0

  25. 10.58.0

    15 Jun 2026
    • deprecated

      react-router: Always build client instrumentation and deprecate useInstrumentationAPI

    • hono: Add support for the Deno runtime

      @sentry/hono now supports the Deno runtime via a new @sentry/hono/deno entry point. Install @sentry/deno as a peer dependency and initialize Sentry through the sentry() middleware:

      import { Hono } from 'hono';
import { sentry } from '@sentry/hono/deno';

const app = new Hono();

app.use(
  sentry(app, {
    dsn: '__DSN__', // or Deno.env.get('SENTRY_DSN')
    tracesSampleRate: 1.0,
  }),
);

Deno.serve(app.fetch);

    • core: Extract objects as structured logs in consoleLoggingIntegration

      The consoleLoggingIntegration now extracts structured log attributes when the first argument is a plain object.

      // Object keys become log attributes
console.log({ userId: 123, action: 'login' }, 'User logged in');
// → attributes: { userId: 123, action: "login" }

// Non-object first args use template + parameters (unchanged)
console.log('Hello', 'world', 123);
// → sentry.message.template: "Hello {} {}"

  26. 10.57.0

    9 Jun 2026
    • deprecated

      core: Deprecate sendDefaultPii in favor of dataCollection

      sendDefaultPii is deprecated and will be removed in v11. The new dataCollection option lets you control each category of collected data. sendDefaultPii: true still works and maps to enabling all dataCollection categories. dataCollection.userInfo defaults to true when dataCollection is provided, meaning auto-populated user.* fields (e.g. IP address from a request) are collected by default. Data you set explicitly (like via Sentry.setUser()) is always sent regardless. When dataCollection is not set at all, the legacy sendDefaultPii behavior applies (userInfo: false by default) to preserve backward compatibility.

      Note that an empty dataCollection: {} falls back to more permissive defaults than sendDefaultPii: false, so replicate the old behavior by opting out explicitly:

      Sentry.init({
  dataCollection: {
    userInfo: false,
    genAI: { inputs: false, outputs: false },
    httpBodies: [],
    httpHeaders: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
    cookies: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
    queryParams: { deny: ['forwarded', '-ip', 'remote-', 'via', '-user'] },
  },
});

    • angular: Add support for Angular 22

      @sentry/angular now officially supports Angular 22.

    • Use dataCollection.frameContextLines for ContextLines integration

  27. 10.56.0

    2 Jun 2026

    • deno: Redis diagnostics channel based integration for Deno

      Adds Redis integration support for Deno, covering both redis and ioredis clients.

    • cloudflare: Only capture workflow step error on final retry attempt

    • hono: Emit warning if @sentry/node was imported instead of @sentry/hono/node

  28. 10.55.0

    28 May 2026
    • deprecated

      hono: Promote @sentry/hono to stable and deprecate honoIntegration

      The @sentry/hono SDK is now stable. See the Sentry Hono SDK docs to get started.

    • hono: Add shouldHandleError option to sentry() middleware

      The sentry() middleware now accepts a shouldHandleError callback to control which errors are captured and sent to Sentry. By default, 3xx/4xx HTTP errors are ignored and 5xx errors and plain Error objects are captured. Return true from the callback to capture an error, false to suppress it.

      app.use(
  sentry(app, {
    dsn: '__DSN__',
    shouldHandleError(error) {
      const status = (error as { status?: number })?.status;
      // Capture 401/403 in addition to the default 5xx errors
      return status === 401 || status === 403 || typeof status !== 'number' || status >= 500;
    },
  }),
);

    • tanstackstart-react: Add distributed tracing

      Server and client traces are now automatically connected, allowing you to see the full request lifecycle from server-side rendering through client-side hydration in a single trace.

  29. 10.54.0

    26 May 2026

    • core: Support array attributes for spans, logs, and metrics

      Arrays of primitive values (string, number, boolean) are now accepted as attribute values. Arrays containing non-primitive elements will be dropped and won't show up in Sentry. Array attributes on logs and metrics were previously stringified and will now be sent as actual arrays instead. If you have custom rules that process attribute values in any beforeSend* callbacks (e.g., data scrubbing), you may need to update them to correctly handle array values.

      For instance, here's how you can update a beforeSendLog callback to handle arrays:

      beforeSendLog: log => {
  const attributes = log.attributes;
  Object.keys(attributes).forEach(key => {
    const value = attributes[key];
    if (typeof value === 'string') {
      attributes[key] = scrubData(value);
    }
    if (Array.isArray(value)) {
      attributes[key] = value.map(v => (typeof v === 'string' ? scrubData(v) : v));
    }
  });
  return log;
};

    • browser: Add fetchStreamPerformanceIntegration for streamed response tracking

      A new integration that tracks the performance of streamed fetch responses. Use this to measure time-to-first-byte and streaming duration for APIs that return chunked/streamed data. This replaces the now deprecated trackFetchStreamPerformance option.

    • core: Add dataCollection client option

      Adds a new dataCollection client option for controlling what data the SDK collects and sends to Sentry. This provides a centralized way to configure data collection behavior across different SDK features. In the future, this option will be used for fine-granular data filtering, while the simple sendDefaultPii boolean option will be deprecated and removed in a future release.

  30. 10.53.1

    12 May 2026

    Reading the note…

  31. 10.53.0

    12 May 2026

    • core: Add streamGenAiSpans options to stream gen_ai spans

      Adds a new streamGenAiSpans option that controls how gen_ai spans are sent to Sentry. When set, the SDK extracts all gen_ai spans out of a transaction and sends them as v2 envelope items.

      Enable this option if gen_ai spans are being dropped because the transaction payload exceeds size limits.

      Sentry.init({
  dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0',
  streamGenAiSpans: true,
});

    • browser: Migrate browser profiling thread data to span attributes

    • core: Add addConsoleInstrumentationFilter utility

  32. 10.52.0

    7 May 2026
    • security

      Bump fast-xml-parser to fix vulnerability

    • security

      Bump vite versions to fix vulnerability

    • Beta release of the official Hono Sentry SDK

      This release marks the beta release of the @sentry/hono Sentry SDK. For details on how to use it, check out the Sentry Hono SDK docs. Please reach out on GitHub if you have any feedback or concerns.

  33. 10.51.0

    29 Apr 2026
    • breaking

      hono: Change setup for @sentry/hono/node (init in external file)

      To improve Node.js instrumentation, the sentry() middleware exported from @sentry/hono/node no longer accepts configuration options. Instead, you must configure the SDK by calling Sentry.init() in a dedicated instrumentation file that runs before your application code (read more in the Hono SDK readme:

      // instrument.mjs (or instrument.ts)
import * as Sentry from '@sentry/hono/node';

Sentry.init({
  dsn: '__DSN__',
  tracesSampleRate: 1.0,
});

    • cloudflare: Add trace propagation for RPC method calls

      Trace context is now propagated across Cloudflare Workers RPC calls, connecting traces between Workers and Durable Objects. This feature is opt-in and requires setting enableRpcTracePropagation: true in your SDK configuration:

      // Worker
export default Sentry.withSentry(
  env => ({
    dsn: env.SENTRY_DSN,
    enableRpcTracePropagation: true,
  }),
  handler,
);

// Durable Object
export const MyDurableObject = Sentry.instrumentDurableObjectWithSentry(
  env => ({
    dsn: env.SENTRY_DSN,
    enableRpcTracePropagation: true,
  }),
  MyDurableObjectBase,
);

    • nitro: Add @sentry/nitro SDK

      A new @sentry/nitro package provides first-class Sentry support for Nitro applications, with HTTP handler and error instrumentation, middleware tracing, request isolation, and build-time source map uploading via withSentryConfig. Read more in the Nitro SDK docs and the Nitro SDK readme.

  34. 10.50.0

    23 Apr 2026
    • removed

      hono: Remove undefined from options type

    • effect: Support v4 beta

      The @sentry/effect integration now supports Effect v4 beta, enabling Sentry instrumentation for the latest Effect framework version. Read more in the Effect SDK readme.

    • hono: Add @sentry/hono/bun for Bun runtime

      A new @sentry/hono/bun entry point adds first-class support for running Hono applications instrumented with Sentry on the Bun runtime. Read more in the Hono SDK readme.

  35. 10.49.0

    16 Apr 2026

    Reading the note…

  36. 10.48.0

    9 Apr 2026

    Reading the note…

  37. 10.47.0

    31 Mar 2026

    Reading the note…

  38. 10.46.0

    25 Mar 2026

    Reading the note…

  39. 10.45.0

    19 Mar 2026

    Reading the note…

  40. 10.44.0

    17 Mar 2026

    Reading the note…

  41. 10.43.0

    10 Mar 2026

    Reading the note…

  42. 10.42.0

    3 Mar 2026

    Reading the note…

  43. 10.41.0

    2 Mar 2026

    Reading the note…

  44. 10.40.0

    24 Feb 2026

    Reading the note…

  45. 10.39.0

    16 Feb 2026

    Reading the note…

  46. 10.38.0

    29 Jan 2026

    Reading the note…

  47. 10.37.0

    27 Jan 2026

    Reading the note…

  48. 10.36.0

    21 Jan 2026

    Reading the note…

  49. 10.35.0

    19 Jan 2026

    Reading the note…

  50. 10.34.0

    14 Jan 2026

    Reading the note…