Darkhorse-Fraternity / monad-stack

https://monad-stack-docs.vercel.app
MIT License
0 stars 0 forks source link

fix(deps): update dependency react-error-boundary to v4 #50

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
react-error-boundary ^3.1.4 -> ^4.0.0 age adoption passing confidence

Release Notes

bvaughn/react-error-boundary ### [`v4.0.2`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.2) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.1...4.0.2) Fix broken TypeScript definitions file ([#​133](https://togithub.com/bvaughn/react-error-boundary/issues/133), [https://github.com/parcel-bundler/parcel/issues/8908](https://togithub.com/parcel-bundler/parcel/issues/8908)) ### [`v4.0.1`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.1) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.0...4.0.1) - Render `ErrorBoundaryContext` around fallback UI as well, so the `useErrorBoundary` hook could be used within the fallback component to reset the boundary. For example: ```js import { useErrorBoundary } from "react-error-boundary"; function ErrorFallback({ error }) { const { resetBoundary } = useErrorBoundary(); return (

Something went wrong:

{error.message}
); } ``` See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf ### [`v4.0.0`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.0) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/v3.1.4...4.0.0) - Replace `useErrorHandler` hook with `useErrorBoundary`; can be used to trigger an error boundary or dismiss one - Merge `onReset` and `onResetKeys` props; pass "details" object explaining the cause of the reset *** ### Why did the `useErrorHandler` hook change? The old hook had two design flaws, both related to the `givenError` parameter: 1. All the hook did was `throw` this value. This seemed unnecessary, because if a component already has a reference to an error during render, it can just `throw` the value itself. - It would not properly re-throw `null` or `undefined` values. (Although an edge case, JavaScript enables throwing *any* values/types.) If you were using the `givenError` functionality– you can now just *throw the value* directly instead. ```js // Before function Greeting() { const [name, setName] = React.useState('') const {greeting, error} = useGreeting(name) useErrorHandler(error) ``` ```js // After function Greeting() { const [name, setName] = React.useState('') const {greeting, error} = useGreeting(name) if (error) { throw error; } ``` ### How can I use the new `useErrorHandler` hook? #### Show the nearest error boundary from an event handler React only handles errors thrown during render or during component lifecycle methods (e.g. effects and did-mount/did-update). Errors thrown in event handlers, or after async code has run, will not be caught. This hook can be used to pass those errors to the nearest error boundary: ```js import { useErrorBoundary } from "react-error-boundary"; function Example() { const { showBoundary } = useErrorBoundary(); useEffect(() => { fetchGreeting(name).then( response => { // Set data in state and re-render }, error => { // Show error boundary showBoundary(error); } ); }); // Render ... } ``` #### Dismiss the nearest error boundary A fallback component can use this hook to request the nearest error boundary retry the render that original failed. ```js import { useErrorBoundary } from "react-error-boundary"; function ErrorFallback({ error }) { const { resetBoundary } = useErrorBoundary(); return (

Something went wrong:

{error.message}
); } ```

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by Mend Renovate. View repository job log here.

vercel[bot] commented 1 year ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated
monad-stack-docs ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Mar 21, 2023 at 5:57PM (UTC)