Next.js Turbopack Support

[ryanolson-aumni]

⚠️ This original post has been edited by @lforst to reflect the current status of Turbopack Support ⚠️

Important

This issue is tracking progress on Turbopack Support. If you find bugs or problems with the Sentry SDK in combination with Turbopack please open a separate issue. Thank you!

Problem Statement

Sentry should work in combination with Turbopack with all of its features.

Current Status (Last Update May 5, 2025)

Feature	Support	Notes
Next.js app compiles and runs without issues	✅
Server-side instrumentation	✅
Client-side instrumentation	✅	- Upgrade to SDK version 9.9.0 or greater - Upgrade to Next.js canary 15.3.0-canary.8 or greater - Add instrumentation-client.ts file with Sentry.init() call. (sentry.client.config.ts can be replaced with instrumentation-client.ts. It serves the same purpose.)
Release Injection	✅	- Upgrade SDK to version 9.11.0
Source Maps	❌	- Needs runAfterProductionCompile hook implemented in Next.js (done in Next.js 15.4.0-canary.19) - Needs way to inject debug IDs into bundles implemented in Next.js
React Component Name Annotations	❌	- Needs way to transform code in Next.js - Will likely not be possible for the forseeable future

[leerob]

It's also worth noting that the initial Turbopack support is for next dev, which is only for your local environment. next build support will come later 🙏

[coderrshyam]

@lforst Why depended on further next.js releases work now and make it compatitable turbopack with sentry at least in dev mode next dev --turbopack

[lforst]

@coderrshyam I don't fully understand what you are saying but the SDK is already compatible with next dev --turbopack. The only thing that is missing is sourcemaps for next build --tubropack.

[l0g1x]

Is there an ETA on source maps support?

[chargome]

@l0g1x you can follow the progress for this here (also linked in the description).