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 Apr 10, 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 - 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

[smeubank]

Hi @ryanolson-aumni

We are also eager to add support here!

We have 2 plugin repos to add support for webpack, esbuild, rollup, and vite. The latter 3 we support via an opensource project where we'd love to see support so we could potentially adopt it via our usage of their adapters. Upvote the issue there as well. Although I do not think it is on their immediate radar either. unjs/unplugin#302

https://github.com/getsentry/sentry-webpack-plugin

https://github.com/getsentry/sentry-javascript-bundler-plugins

[mdugue]

any news on this?

[lforst]

@mdugue We'll tackle turbopack when it becomes somewhat stable.

[smeubank]

any news on this?

Fwiw I would also encourage you to upvote and comment on this issue which wr could also use to provide support similar to webpack, vite, esbuild and rollup

unjs/unplugin#302

[lforst]

Update

As of now, we cannot transfer the functionality we currently have in the SDK to Turbopack:

Turbopack loaders are not passed transpiled javascript, instead, they are passed the original user code. The SDK needs transpiled JS to properly be able to do transformations to modules. We could transpile the user code ourselves but that is fragile AF - so not an option.

As of now, the SDK will continue to work in production mode which is arguably more important, but we would like to support dev mode.

Branch with my experiments: #9295

[Stanzilla]

Update

As of now, we cannot transfer the functionality we currently have in the SDK to Turbopack:

Turbopack loaders are not passed transpiled javascript, instead, they are passed the original user code. The SDK needs transpiled JS to properly be able to do transformations to modules. We could transpile the user code ourselves but that is fragile AF - so not an option.

As of now, the SDK will continue to work in production mode which is arguably more important, but we would like to support dev mode.

Branch with my experiments: #9295

To clarify, does it work with Turbopack in production mode as-is or only with the changes in your branch?

[lforst]

@Stanzilla Turbopack will not work with the SDK (dev and prod). My branch does not contain any fixes or features, just experiments proving that things don't work.

[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 🙏

[jmarbutt]

Is this why my dev mode crashes after every change in NextJS now? Anytime I make a change I get an error.

[lforst]

@jmarbutt In general: No, Sentry should not crash your dev mode in any case.

If you think otherwise, please create a separate issue with reproduction!

[jmarbutt]

Yeah it seems to only be happening when I am using turbo and sentry, if I disable turbo it works fine. I will see if I can get it to a more reproducible error.

[kachkaev]

Next.js 10.3 got released today. This section in the blog post looks promising:

Ecosystem
We’re working with commonly used integrations like Sentry to make sure they’re compatible with next build --turbopack before the stable release. Please reach out to @leerob on X if you are a tool author who would like to work with us to ensure compatibility.

🤞

[coderrshyam]

hey @calvinf Next.js15.3.0 just released today.

[wroughtec]

Just played with it this morning, might need to make sure the comment doesn't display or at least change it if is 15.3.0 🤣

 WARNING: You are using the Sentry SDK with Turbopack (`next build --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 as Turbopack is still experimental for production builds, some of the Sentry SDK features like source maps will not work. Follow this issue for progress on Sentry + Turbopack: https://github.com/getsentry/sentry-javascript/issues/8105.```

[lforst]

@kachkaev @chargome Yup, we are on it as much as we can. Still dependent on a few Next.js changes. In general, if you upgrade the SDK you should have all the monitoring functionality - only sourcemaps will not work.

@wroughtec Good point. Will change that!