Sentry now showing first line of stack traces from the Error cause

[Yuripetusko]

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

8.48.0

Framework Version

react 18.3.1, next 14.24.2

Link to Sentry event

https://taskwise-gmbh.sentry.io/issues/16694528/?project=4508482014806096&query=is:unresolved%20issue.priority:%5Bhigh,%20medium%5D&stream_index=0

Reproduction Example/SDK Setup

https://codesandbox.io/p/sandbox/nervous-brattain-kzpr8z

export class CustomError extends Error {
  userErrorMessage: string;
  name = "CustomError";

  constructor(
    message: string,
    userErrorMessage?: RelocationUserErrorMessage,
    cause?: unknown
  ) {
    super(message, { cause });

    this.userErrorMessage = userErrorMessage || "Something went wrong";
  }
}

Steps to Reproduce

1. Throw an error in 1 file
2. Catch an error in another file and create new error passing original error as cause
3. Capture new custom error with sentry

Expected Result

When console.logging the custom error, the stack trace of the cause includes a line where it was thrown, however when viewing the sentry, the stack trace of cause is missing 1 line, so it's hard to see where the error originated.

Example:

Here how it is displayed in Sentry

And here how it is displayed in console

As you see 1 line in the cause stack trace is missing in sentry, specifically this line:

at generateAreaInfoAction (generateAreaInfoAction.ts:21:11)

Actual Result

The whole stack trace to be included in Sentry for cause error

It appears that sentry displays the custom error's stack instead of stack of the cause, and only the first line (error name and message) of the cause is displayed, with the rest of the stack being displayed on sentry is taken from the actual error and not the cause error

[Yuripetusko]

It's almost like sentry only taking cause.message for the first line, but re-uses custom error's stack trace for the rest of it instead of inherited/caused error's stack trace

[s1gr1d]

Hello and thanks for reaching out! And hanks for the reproduction example, however it's not working and throwing an ReferenceError when trying to compile. Also, Sentry is not set up because the instrument.ts file isn't included anywhere and several function imports are missing. I am happy to look at this again, when the reproduction is working.

As for error.cause: You can include it with the ExtraErrorData integration, which automatically enables captureErrorCause.

[Yuripetusko]

Sorry about incorrect reproduction. I just did a working example, and also discovered that with @sentry/node it works correctly, but not with @sentry/nextjs

Here is a nextjs example:

Yuripetusko/sentry-14780-issue-reproduction@56213fc

You can start dev server with pnpm dev

Then navigate to http://localhost:3000/sentry-example-page, and press the button.

Here is a nextjs example and you can see that custom error stack trace is not including module1 file where it was thrown from
https://skybreach.sentry.io/issues/16764753/?project=4508558364573776&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=0

---

And here is an example with @sentry/node https://github.com/Yuripetusko/sentry-error-cause-stack-trace

You can test it by running pnpm testSentry and here it works correctly with stack trace of cause showing module1

https://skybreach.sentry.io/issues/16764267/?project=4508558364573776&query=is:unresolved%20issue.priority:%5Bhigh,%20medium%5D&stream_index=2

[Yuripetusko]

I also deployed The nextjs example to vercel if you don't want to run it locally

https://sentry-14780-issue-reproduction.vercel.app/sentry-example-page

[s1gr1d]

Thanks for the two GitHub repos, I will take a look! :)