I can make a class an error boundary in React by implementing componentDidCatch
.
Is there a clean approach to making a functional component into an error boundary without converting it into a class?
Or is this a code smell?
Only class components can be error boundaries. In practice, most of the time you'll want to declare an error boundary component once and use it throughout your application. Note that error boundaries only catch errors in the components below them in the tree. An error boundary can't catch an error within itself.
Error boundaries catch errors during rendering, in lifecycle methods, and in constructors of the whole tree below them. In order to use Error Boundary in Functional Component, I use react-error-boundary. When we run this application, we will get a nice error display form the content of ErrorHandler component.
So basically, error boundaries only handle errors in the parts of our code that involve React. To create an error boundary, we simply have to create a class component and define a state variable for determining whether the error boundary has caught an error.
Error handling with Error Boundaries — For class components. Error boundaries are the most straightforward and effective way to handle errors that occur within your React components. You can create an error boundary component by including the life cycle method componentDidCatch(error, info) if you use class component.
As of v16.2.0, there's no way to turn a functional component into an error boundary.
The React docs are clear about that, although you're free to reuse them as many times as you wish:
The
componentDidCatch()
method works like a JavaScriptcatch {}
block, but for components. Only class components can be error boundaries. In practice, most of the time you’ll want to declare an error boundary component once and use it throughout your application.
Also bear in mind that try/catch
blocks won't work on all cases.
If a component deep in the hierarchy tries to updates and fails, the try/catch
block in one of the parents won't work -- because it isn't necessarily updating together with the child.
There is an implementation that can handle with non-existent functionalities for a functional component such as componentDidCatch
and deriveStateFromError
.
According to the author, it is based on React.memo().
The proposed solution is greatly inspired by the new React.memo() API.
import Catch from "./functional-error-boundary" type Props = { children: React.ReactNode } const MyErrorBoundary = Catch(function MyErrorBoundary(props: Props, error?: Error) { if (error) { return ( <div className="error-screen"> <h2>An error has occured</h2> <h4>{error.message}</h4> </div> ) } else { return <React.Fragment>{props.children}</React.Fragment> } })
reference and API here
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With