Is _error.js still necessary?

[mpereira]

I've been using the Sentry JS SDK for a while now, always upgrading to the newer versions.

I started seeing this error recently: _error.js called with falsy error (null) with Sentry version 7.69.0.

Here's my _error.js, which was probably generated by the Sentry JS CLI wizard months ago:

// This page is loaded by Nextjs:
//  - 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 throws or rejects, and it's
//    caught by the built-in Nextjs error boundary

// See:
//  - https://nextjs.org/docs/basic-features/data-fetching/overview
//  - https://nextjs.org/docs/api-reference/data-fetching/get-initial-props
//  - https://reactjs.org/docs/error-boundaries.html

import * as Sentry from '@sentry/nextjs';
import NextErrorComponent from 'next/error';

const CustomErrorComponent = (props) => {
  return <NextErrorComponent statusCode={props.statusCode} />;
};

CustomErrorComponent.getInitialProps = async (contextData) => {
  // In case this is running in a serverless function, await this in order to
  // give Sentry time to send the error before the lambda exits.
  await Sentry.captureUnderscoreErrorException(contextData);

  // This will contain the status code of the response.
  return NextErrorComponent.getInitialProps(contextData);
};

export default CustomErrorComponent;

[BoraVivek-Furrl]

Hi,

I am using Nextjs 14 and using App router, so still does this _error.js file required inside pages folder?

[lforst]

For pages router it is still necessary. If you are only using the app router you can remove it.

[cpatti97100]

Hi @mpereira did you find a solution for this? thanks!

[lforst]

For pages router it is still necessary.