Global-error.js only catches errors thrown in the RootLayout, throw an error in there and you’ll see it

For some reason it just displays the error in the console of the browser, but does not show the error.js or global-error.js page

Need to be prod mode. You can use either a dynamic layout (export const revalidate = 0) or use react devtool to trigger an error

I thought that running npm run build and npm run start puts the app in prod mode

where would I need to add export const revalidate = 0?

Hey @joulev sorry to bother you, your tip with revalidate did help and I was able to see the error pages locally, but I was wondering about why this works?

In the docs it says that revalidate is used to purge the Data Cache, how does export const revalidate = 0 put you into Prod mode??

https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#revalidating-data

It doesn’t put you into prod mode. It ensures that the code is not run during build so the error is caught during runtime by the boundary file rather than caught during build causing a build error.