react-error-boundary VS Sentry

I use the use-error-boundary module for this just to never have to write a class component myself!

Requires a dependency but you can absolutely use error boundaries with functional components via react-error-boundary: https://github.com/bvaughn/react-error-boundary

as for checking errors: https://github.com/bvaughn/react-error-boundary

For those of you, who hate re-inventing the wheel or just prefer libraries for already solved problems, there is a nice one that implements a flexible ErrorBoundary component and has a few useful utils similar to those described above: GitHub - bvaughn/react-error-boundary

Use https://github.com/bvaughn/react-error-boundary for error boundaries and you won't have to write one yourself.

There's no reason to manually write an error boundary as a class component yourself, either, given that https://github.com/bvaughn/react-error-boundary exists.

Yeah, and even in that case, you should probably be using https://github.com/bvaughn/react-error-boundary rather than writing your own from scratch.

they can https://github.com/bvaughn/react-error-boundary (this is from the react team) doesn't matter how it works internally, im not going to write a class just for error handling.

i would not bother with classes tbh, use this: https://github.com/bvaughn/react-error-boundary it's made by a react core team member and they even recommend it.

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry