Next.js App Router with Turbopack: route handler error not captured

Question

Next.js App Router with Turbopack: route handler error not captured

Closed this issue 2 months ago · 5 comments

KirillTregubov commented 2 months ago

Related: #8105

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.12.0

Framework Version

Next 15.5.3

Link to Sentry event

No response

Reproduction Example/SDK Setup

https://github.com/KirillTregubov/nextjs-sentry-demo

This repo was generated by following this quick start followed by this step in the Sentry Next.js docs

Steps to Reproduce

Clone repo
Install dependencies (I used bun i)
Create an .env file and provide SENTRY_AUTH_TOKEN= inside it.
Run the dev script and add the --turbo flag (I used bun dev --turbo)
Send a request to http://localhost:3000/api/sentry-example-api (I navigated using my browser)

Expected Result

Thrown SentryExampleAPIError("This error is raised on the backend called by the example page.") in the route handler is captured.

Actual Result

Error does not show up in the Sentry dashboard.

Additional Context

The error is properly captured when run without Turbopack. Repeat the following steps:
4. Run the dev script (I used bun dev)
5. Send a request to http://localhost:3000/api/sentry-example-api (I navigated using my browser)

You will notice that the error properly shows up in the dashboard.

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

Answer 1 · 2025-09-19T03:22:14.000Z

JS-958 Next.js App Router with Turbopack: route handler error not captured

Answer 2 · 2025-09-19T06:27:15.000Z

Hey @KirillTregubov thanks for reaching out.
The fix already merged from Vercel but so far only released in next@15.5.1-canary.25.

closing as duplicate of #17512

Answer 3 · 2025-09-20T16:42:49.000Z

@chargome can you please clarify as your comment is confusing and we're unsure if this support is actually coming or not. You're saying its backdated in an old canary of an old version and didn't make it into the release of 15.5.1, 15.5.2, or 15.5.3? Did you mean to type 15.6 canary?

Answer 4 · 2025-09-21T21:16:45.000Z

@swiecki Vercel released the fix already in next@15.5.1-canary.25 but not on any stable release.

Answer 5 · 2025-09-22T10:57:39.000Z

It will be included in next@15.5.4