Next.js 16 Turbopack duplicates @opentelemetry/api across chunks, causing infinite .with() recursion and fatal RangeError: Maximum call stack size exceeded

[InterstellarStella]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.38.0 (works correctly on 10.8.0)

Framework Version

Next.js 16.1.6 (Turbopack, production build), Node.js v24.12.0, Prisma 7.x (@prisma/instrumentation ^7.4.0), pnpm workspaces, deployed on AWS ECS Fargate (Debian 12.13)

Link to Sentry event

No response

Reproduction Example/SDK Setup

// sentry.server.config.ts
import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  environment,
  tracesSampleRate: 1, // also reproduces with 0
  integrations: [
    Sentry.prismaIntegration(),
  ],
});

@opentelemetry/api resolves to a single version (1.9.0) across the dependency tree:

dependencies:
@sentry/nextjs 10.38.0
├── @opentelemetry/api 1.9.0
└─┬ @sentry/node 10.38.0
   ├── @opentelemetry/api 1.9.0
   ├─┬ @opentelemetry/context-async-hooks 2.5.0
   │  └── @opentelemetry/api 1.9.0 peer
   ├─┬ @opentelemetry/core 2.5.0
   │  └── @opentelemetry/api 1.9.0 peer
   └─┬ @opentelemetry/instrumentation 0.211.0
      └── @opentelemetry/api 1.9.0 peer

Steps to Reproduce

1. Create a Next.js 16 app using Turbopack (the default) with @sentry/nextjs 10.38.0
2. Deploy to a Node.js 24 environment (we use AWS ECS Fargate)
3. The server crashes with RangeError: Maximum call stack size exceeded sometimes within minutes, sometimes after several hours
4. Setting tracesSampleRate: 0 does not prevent the crash
5. Setting skipOpenTelemetrySetup: true does not prevent the crash (and introduces MaxListenersExceededWarning from all auto-loaded instrumentations stacking listeners on every request)
6. Downgrading to @sentry/nextjs 10.8.0 with the same Next.js 16.1.6 and Turbopack resolves the issue completely

Expected Result

The application runs stably without stack overflow errors, as it does on SDK version 10.8.0.

Actual Result

The server fatally crashes with an unhandled RangeError: Maximum call stack size exceeded. The stack trace shows two separate bundled copies of @opentelemetry/api in different Turbopack chunks, whose .with() methods recursively call each other.

Additionally, with skipOpenTelemetrySetup: true, the server experiences rapid MaxListenersExceededWarning floods:

MaxListenersExceededWarning: Possible EventEmitter memory leak detected.
11 close listeners added to [ServerResponse]. MaxListeners is 10.

Additional Context

Errors in Sentry are provided in the internal Linear ticket.

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1735

[chargome]

Can you please also share the next.config.ts|js file?

[wyantb]

const nextIntlPlugin = require("next-intl/plugin");
const { withSentryConfig } = require("@sentry/nextjs");
const withNextIntl = nextIntlPlugin("./i18n.ts");

const sentryConfig = {
  // For all available options, see:
  // https://github.com/getsentry/sentry-webpack-plugin#options

  org: "...",
  project: "...",

  // Only print logs for uploading source maps in CI
  silent: !process.env.CI,

  // For all available options, see:
  // https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/

  // Upload a larger set of source maps for prettier stack traces (increases build time)
  widenClientFileUpload: true,

  // Uncomment to route browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers.
  // This can increase your server load as well as your hosting bill.
  // Note: Check that the configured route will not match with your Next.js middleware, otherwise reporting of client-
  // side errors will fail.
  tunnelRoute: "/api/monitoring",

  // Hides source maps from generated client bundles
  hideSourceMaps: true,

  // Automatically tree-shake Sentry logger statements to reduce bundle size
  disableLogger: true,

  // Enables automatic instrumentation of Vercel Cron Monitors. (Does not yet work with App Router route handlers.)
  // See the following for more information:
  // https://docs.sentry.io/product/crons/
  // https://vercel.com/docs/cron-jobs
  automaticVercelMonitors: true,
};

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: false,
  transpilePackages: ["api", "auth", "tailwind-config", "mail"],
  output: "standalone",
  images: {
    remotePatterns: [
      {
        // google profile images
        protocol: "https",
        hostname: "lh3.googleusercontent.com",
      },
    ],
  },
  async redirects() {
    return [...];
  },
  webpack: (config) => {
    config.externals = config.externals || [];
    if (Array.isArray(config.externals)) {
      config.externals.push("@node-rs/argon2", "@node-rs/bcrypt", "hnswlib-node");
    }
    return config;
  },
};

module.exports = withSentryConfig(withNextIntl(nextConfig), sentryConfig);

Stella may have been able to reproduce with a more minimal example, but we're the team that's running fine on 10.8 and not 10.38, so I figured I could provide ours since there's nothing terribly secret in here. (I truncated the redirects list since I assume that's not a possible source of any problem, so this isn't quite valid JS but it's 99%)

[chargome]

Thanks for sharing, we're investigating