react-error-boundary VS react-sweet-state

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.

For none server related state have a look at https://github.com/pmndrs/zustand or https://atlassian.github.io/react-sweet-state

Have a look at https://atlassian.github.io/react-sweet-state and we used it in a pretty large financial & trading App. I can say it's much simpler than Redux and does the job!

https://github.com/atlassian/react-sweet-state Developed and maintained by Atlassian. I am using it in ZudVPN and tbh I never looked back to other state management libraries. It is simple, intuitive and does not require a top component Provider like the Context API.