We need Error boundaries and need to handle exceptions

[dahal]

We need to render error pages for bunch of errors (404, 500 etc).

Also, let's implement sentry for exception notifications. We donot want to be vendor locked, so lets make sure that the code does not break if Sentry is not enabled.

[linear]

CAP-68 We need Error boundaries and need to handle exceptions

[Vinyl-Davyl]

Would like to work on this too

[dahal]

Would like to work on this too

Assigned 🚀

[dahal]

Due it inactivity, I am making it open for others to contribute. Please feel free to submit the PR.

[Pranavtej]

@dahal would like to work on this issue , please assign me

[Tarunkumartasets]

this is not_found page for 404

in next 14 we need to have each error.tsx as they have removed 500.tsx which was in page router

doubt's
@dahal should we make sentry integration optional
@dahal can I get some idea to standardised the way we show error in each pages
also do we need to add error boundary to each major component

progress
404 page is done
sentry integration is done

[dahal]

@Pranavtej looks like @Tarunkumartasets picked this up, we have other issues if any of it interests you 🙏🏼

@Tarunkumartasets for error pages, let's go with something simple, here is the mockup

[dahal]

@Tarunkumartasets

• please make it optional
• lets use the mockup above for all 404 pages
• lets go with this approach

[Pranavtej]

@dahal that's ok i will pick some other issues .
if this issue still not resolved , assign to me

[DIWAKARKASHYAP]

@dahal i raised this PR due it inactivity