@sentry/nextjs: Ability to opt-out of "specific message is omitted in production builds to avoid leaking sensitive details"

[stephenhmarsh]

Problem Statement

This has been extremely frustrating for me because it omits the entire stack trace:

Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.

Solution Brainstorm

There should be a config option to allow the full errors to get reported like normal.

[mydea]

Hello, this is a restriction from Next.js, and not from the Sentry SDK. In 8.4.0, we shipped an update to handle this ( #12157), but this depends on a change in Next.js that we contributed that is only available in Next.js 14.3.0-canary.64 or above. This means this should fully work once 14.3.0 is released - until then there is nothing we can do about this (except you can use the canary version, but that obviously has it's own set of problems). You can read more details in the PR I linked!

I'm going to close this issue because there is sadly nothing more we can do about this than wait for Vercel to release the change to a stable channel.

[stephenhmarsh]

thanks for the quick reply @mydea - appreciate the info about future steps forward 👍