Package Exports
- use-error-boundary
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (use-error-boundary) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
use-error-boundary
A react hook for using error boundaries in your functional components.
It lets you keep track of the error state of child components, by wrapping them in a provided ErrorBoundary component.
Installation
npm i use-error-boundaryExamples and usage
Import the hook:
// Named
import { useErrorBoundary } from 'use-error-boundary'
// Default
import useErrorBoundary from 'use-error-boundary'Use the hook in your react component, it provides you with this object:
const MyComponent = () => {
const {
ErrorBoundary, // class - The react component to wrap your children in. This WILL NOT CHANGE
didCatch, // boolean - Whether the ErrorBoundary catched something
error, // null or the error
errorInfo // null or the error info as described in the react docs
} = useErrorBoundary()
...
}Wrap your components in the ErrorBoundary:
const JustRenderMe = () => {
throw new Error('💥')
}
const MyComponent = () => {
...
/**
* The ErrorBoundary renders its children directly,
* when a component throws, the ErrorBoundary will return null from its render method.
*
* See TODO section :)
*/
return (
<ErrorBoundary>
<JustRenderMe />
</ErrorBoundary>
)
}TODO
- Extend default ErrorBoundary component to render a provided component when there is an error
- Passing own component as ErrorBoundary and wrap it
- Change
createErrorBoundaryClassto passonDidCatchas prop (HOC) - Cleanup tests
Contributing
Contributions are welcome, as this is my first properly published npm package.
Feel free to open issues or pull requests! I will review them as fast as possible.