Error boundries
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
In React 16 components introduce something new called [error boundries](https://facebook.github.io/react/blog/2017/07/26/error-handling-in-react-16.html). The main idea is that if an error is thrown from a component, it can be caught early, and prevents crashing the whole web page.
I find this interesting because:
1. it means apps can keep running even if a component crashes (resiliency! :D)
2. it'll play well with `component.use` (or similar); can send through the error to a local dev logger, or monitoring solution
3. it's especially good to add resiliency when encapsulating 3rd party code - ideally code would never crash, but alas code isn't bug free
Thoughts?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.