Next.js SSR unhandled errors are not logged

[curiousercreative]

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

7.73.0

Framework Version

Next.js 13.5.3

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

1. Install NextJS example, enter project dir and init git repo (seems to be required for sentry wizard)

   npx create-next-app@latest nextjs-blog --use-npm --example "https://github.com/vercel/next-learn/tree/main/basics/learn-starter"
   cd nextjs-blog/
   git init

2. Install sentry

   npx @sentry/wizard@latest -i nextjs

3. Modify the home page to make it SSR rather than SSG and throw an error server-side during page component render.

   export function getServerSideProps () {
     return {
       props: {
         a: 'b',
       }
     }
   }
   
   export default function Home() {
     if (typeof window === 'undefined') throw new Error('server-side error')
     else throw new Error('client-side error')
   
     return <div></div>
   }
   

4. Build, start, and load page at http://localhost:3000

   npm run build && npm start

Expected Result

I expected at least the server-side error to be logged in Sentry. I wouldn't be surprised if both a server-side and client-side error were logged per page load.

Actual Result

No errors are logged in sentry

[curiousercreative]

captureException does work, so that may be a viable workaround for some

[Lms24]

Hi @curiousercreative thanks for reporting! Backlogging to investigate this further (currently too busy with other tasks). If you want to help speed this up, we'd greatly appreciate a minimal reproduction as a GH repo. Only asking because your repro steps make it seem like you already set up a minimal repro project.

[curiousercreative]

@Lms24 I've added a reproduction repo here: https://github.com/CommonEnergy/sentry-next-ssr

To repro:

1. Clone repo

   git clone https://github.com/CommonEnergy/sentry-next-ssr.git
   cd sentry-next-ssr
   

2. Add a .env or .env.local file to repo root with a NEXT_PUBLIC_SENTRY_DSN defined
3. Build and start the app

   npm run build
   npm start
   

4. Open in browser http://localhost:3000

[lforst]

Hey thanks for opening this issue. This is mind-blowing to me. We are instrumenting getServerSideProps but never considered instrumenting the actual page if it is run on the server. This is something we need to fix.

[curiousercreative]

@lforst we should also investigate whether the app router (where server components are the default) is affected and make sure those pages are similarly instrumented.

[lforst]

@curiousercreative In the app-router we have this for sure!