v2.0.0

What's Changed

const [error] = useErrorBoundary();

error is now the error that was caught or undefined if nothing errored. Previously error was a boolean value. Providing access to the error rather than a boolean makes it more ergonomic to render UI in response to the caught error. Special thanks to @davwheat for the contribution.

If something other than an instance of Error is thrown, it will be wrapped in an Error object by calling new Error() on the thrown value. A warning will log when this occurs: while you may throw any value in JavaScript, you should only throw instances of Error. This ensures a stack trace is collected and that all errors conform to a unified interface. This wrapping may be removed in a future v3 release of this library.

New Contributors

• @davwheat made their first contribution in #9

Full Changelog: v1.0.2...v2.0.0