@sentry/node

Important Changes

• core: Make matcher parameter optional in makeMultiplexedTransport

The matcher parameter in makeMultiplexedTransport is now optional with a sensible default. This makes it much easier to use the multiplexed transport for sending events to multiple DSNs based on runtime configuration.

Before:

import { makeFetchTransport, makeMultiplexedTransport } from '@sentry/browser';

const EXTRA_KEY = 'ROUTE_TO';

const transport = makeMultiplexedTransport(makeFetchTransport, args => {
  const event = args.getEvent();
  if (event?.extra?.[EXTRA_KEY] && Array.isArray(event.extra[EXTRA_KEY])) {
    return event.extra[EXTRA_KEY];
  }
  return [];
});

Sentry.init({
  transport,
  // ... other options
});

// Capture events with routing info
Sentry.captureException(error, {
  extra: {
    [EXTRA_KEY]: [
      { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' },
      { dsn: 'https://key2@sentry.io/project2' },
    ],
  },
});

After:

import { makeFetchTransport, makeMultiplexedTransport, MULTIPLEXED_TRANSPORT_EXTRA_KEY } from '@sentry/browser';

// Just pass the transport generator - the default matcher handles the rest!
Sentry.init({
  transport: makeMultiplexedTransport(makeFetchTransport),
  // ... other options
});

// Capture events with routing info using the exported constant
Sentry.captureException(error, {
  extra: {
    [MULTIPLEXED_TRANSPORT_EXTRA_KEY]: [
      { dsn: 'https://key1@sentry.io/project1', release: 'v1.0.0' },
      { dsn: 'https://key2@sentry.io/project2' },
    ],
  },
});

The default matcher looks for routing information in event.extra[MULTIPLEXED_TRANSPORT_EXTRA_KEY]. You can still provide a custom matcher function for advanced use cases.

• nextjs: Support cacheComponents on turbopack

This release adds support for cacheComponents on turbopack builds. We are working on adding support for this feature in webpack builds as well.

Other Changes

• Publish AWS Lambda Layer for Node 24

• browser: Expose langchain instrumentation

• browser: Expose langgraph instrumentation

• cloudflare: Allow specifying a custom fetch in Cloudflare transport options

• core: Add isolateTrace option to Sentry.withMonitor()

• nextjs: Add cloudflare waitUntil detection

• node: Add LangChain v1 support

• remix: Add parameterized transaction naming for routes

• cloudflare: Keep http root span alive until streaming responses are consumed

• cloudflare: Wait for async events to finish

• core: continueTrace doesn't propagate given trace ID if active span exists

• node-core: Handle custom scope in log messages without parameters

• opentelemetry: Ensure Sentry spans don't leak when tracing is disabled

• react-router: Use underscores in trace origin values

• breaking

  tanstackstart-react: Remove empty placeholder implementations

Internal Changes