Obsolete Turbopack warning shown?

[jrr]

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

9.12.0

Framework Version

Next 15.3.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

It's a pnpm monorepo with turbopack, with turbo installed at the root level and sentry living within the next project:

// package.json
{
  // ...
  "devDependencies": {
    "prettier": "^3.5.3",
    "turbo": "^2.5.0",
    "typescript": "~5.8.3"
  },
  "packageManager": "pnpm@10.7.1",
  "engines": {
    "node": ">=22"
  }
}

// apps/web/package.json
{
  "name": "@repo/web",
  "type": "module",
  // ...
  "dependencies": {
    // ...
    "@sentry/nextjs": "^9.12.0",
    "next": "15.3.0",
  },
}

Steps to Reproduce

Update turbo, next, and sentry to the latest versions!

If this is difficult to repro I will try to assemble an example.

Expected Result

The turbopack warning doesn't appear after its version requirements have been satisfied.

Actual Result

[@sentry/nextjs] WARNING: You are using the Sentry SDK with Turbopack (next dev --turbo). The Sentry SDK is compatible with Turbopack on Next.js version 15.3.0 or later. You are currently on 15.3.0. Please upgrade to a newer Next.js version to use the Sentry SDK with Turbopack. Note that the SDK will continue to work for non-Turbopack production builds. This warning is only about dev-mode.

[lforst]

I may be stupid but I cannot reproduce this 🤔 Would you mind providing a reproduction example?

[jrr]

@lforst here! https://github.com/jrr/sentry-issue-repro

[lforst]

Ah god I thought I was going crazy. A colleague already fixed this and I was looking at current code being like "how on earth are we entering that branch" 😂 #16026

Thanks for the repro. That cleared things up! It will be fixed with the next release.