@honeybadger-io/nextjs/templates/_error_app_router.js

Next.js integration for Honeybadger

'use client'; // Error components must be Client Components

// eslint-disable-next-line import/no-unresolved
import { useEffect } from 'react'
import { Honeybadger } from '@honeybadger-io/react'

/**
 * error.[js|tsx]: https://nextjs.org/docs/app/building-your-application/routing/error-handling
 * global-error.[js|tsx]: https://nextjs.org/docs/app/building-your-application/routing/error-handling#handling-errors-in-layouts
 *
 * This component is called when:
 *  - on the server, when data fetching methods throw or reject
 *  - on the client, when getInitialProps throws or rejects
 *  - on the client, when a React lifecycle method (render, componentDidMount, etc) throws or rejects
 *      and was caught by the built-in Next.js error boundary
 */
export default function Error({
  error,
  reset,
}) {
  useEffect(() => {
    Honeybadger.notify(error)
  }, [error])

  return (
    <div>
      <h2>Something went wrong!</h2>
      <button
        onClick={
          // Attempt to recover by trying to re-render the segment
          () => reset()
        }
      >
                Try again
      </button>
    </div>
  )
}