-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDK
Description
Package + Version
@sentry/nextjs@^6.10.0
Description
I am finding that the Next.js plugin does not report server side errors and some client side errors.
Using create-next-app
and @sentry/wizard
I have set up the most basic project which is deployed to Vercel. You can find my source code here: https://github.com/jsakas/sentry-next-test
I have three routes:
- https://sentry-next-test.vercel.app/throw-client -- calls an undefined function in
useEffect
generating a client error - https://sentry-next-test.vercel.app/throw-server -- calls an undefined function in
getServerSideProps
generating a server error - https://sentry-next-test.vercel.app/throw-button -- throws an unhandled exception from clicking a button (same example as from the docs)
Only the third example, throwing on button click, works as expected. However this is the most unlikely use case for us. We recently had a unhandled server side exception (in getServerSideProps
) which caused our site to crash. This error was not reported by Sentry and our customers ended up notifying our support team of the issue.
Here is the test project: https://sentry.io/organizations/guesthouse/issues/?project=5893235
Metadata
Metadata
Assignees
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDK