Releases · tatethurston/react-use-error-boundary

21 Jun 21:46

v3.0.0

525225a

v3.0.0 Latest

Latest

What's Changed

const [error] = useErrorBoundary();

The error wrapping that was introduced in v2 has been removed. error will now be the error that was caught without any wrapping for thrown primitives. The types have been updated to unknown to reflect that thrown JavaScript errors may be any type not just instances of Error.
withErrorBoundary now propagates the wrapped component display name for improved debugging with React dev tools. It will display as WithErrorBoundary(${Component.displayName}).

Full Changelog: v2.0.1...v3.0.0

Assets 2

27 May 21:46

tatethurston

v2.0.1

c41df06

v2.0.1

What's Changed

Publish CommonJS and ESM.

Full Changelog: v2.0.0...v2.0.1

Assets 2

19 May 01:11

tatethurston

v2.0.0

6bf903c

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.