Intro

I am using Sentry for the first time in my Nextjs application with the new App router v14.2.5. I have followed the nextjs wizard and read the manual setup guide to understand how to use Sentry with nextjs.

As of my understanding sentry will automatically report errors in server components, but for server actions I have to wrap with a special function from sentry. I have tested that errors thrown in actions are reported to sentry. This is all fine and good. Errors in server components on the other hand....

My Issue

I am having a hard time catching errors in server components. First I thought sentry would automatically "just work", but this was not the case. The page I was trying to test errors on had a page.tsx that is a server component and nested server components inside it (maybe this is something sentry doesn't support?).

// app/page.tsx
export default async function Page(){
 const user = await getUserFromDb()
 return <NestedServerComponent />
}

// app/_shared/NestedServerComponent.server.tsx
export default async function NestedServerComponent(){
 // Do some async stuff and maybe throw an error
 return <ClientComponents />
}

• Errors thrown in Page where reported.
• Errors thrown in NestedServerComponent was ignored

wrapServerComponentWithSentry function

I also found that sentry exports a function called wrapServerComponentWithSentry that is not documented.

• When wrapping all components with wrapServerComponentWithSentry errors in Nested server components where catched
• I would also see different behaviour in dev mode and production npm run dev and npm run build && npm run start.

Is it something wrong with my setup or can someone confirm that Sentry should be able to catch errors in nested server components? Me personally don't like this magic, I would like to read how the magic works? How does sentry know if its a server component and auto wraps it? Does it only wrap server components in page.tsx files?

Another issue (maybe relevant)

When building nextjs and when running in development i get theses wierd warnings from sentry.

Attempted import error: '_optionalChain' is not exported from '@sentry/utils' (imported as '_optionalChain').
Attempted import error: '_nullishCoalesce' is not exported from '@sentry/utils' (imported as '_nullishCoalesce').

If this is why sentry doesn't report the errors it would be nice if it said so aswell. hehe...