Sentry Simple Example 🚨

This example demonstrates how to record unhandled exceptions in your code with Sentry. There are several test pages below that result in various kinds of unhandled exceptions.

Important: exceptions in development mode take a different path than in production. These tests should be run on a production build (i.e. 'next build'). Read more

• Server exceptions
• getServerSideProps throws an Error. This should cause _error.js to render and record Error('Server Test 1') in Sentry. Open in a new tab
• getServerSideProps returns a Promise that rejects. This should cause _error.js to render and record Error('Server Test 2') in Sentry. Open in a new tab
• getServerSideProps calls a Promise that rejects, but does not handle the rejection or await its result (returning synchronously). Sentry should record Error('Server Test 3'). Open in a new tab
• Client exceptions
• There is a top-of-module Promise that rejects, but its result is not awaited. Sentry should record Error('Client Test 1'). Perform client side navigation or Open in a new tab
• There is a top-of-module exception. _error.js should render and record ReferenceError('process is not defined') in Sentry. Perform client side navigation or Open in a new tab
• There is an exception during React lifecycle that is caught by Next.js's React Error Boundary. In this case, when the component mounts. This should cause _error.js to render and record Error('Client Test 3') in Sentry. Perform client side navigation or Open in a new tab
• There is an unhandled Promise rejection during React lifecycle. In this case, when the component mounts. Sentry should record Error('Client Test 4'). Perform client side navigation or Open in a new tab
• An Error is thrown from an event handler. Sentry should record Error('Client Test 5'). Perform client side navigation or Open in a new tab