Update dependency react-error-boundary to v4 - autoclosed

renovate[bot] commented 1 year ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-error-boundary	`^3.0.0` -> `^4.0.0`

Release Notes

bvaughn/react-error-boundary (react-error-boundary)

### [`v4.0.10`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.10) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.9...4.0.10) - Target Safari 12+ compatibility (by removing optional chaining operator and default parameters) ### [`v4.0.9`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.9) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.8...4.0.9) - [145](https://togithub.com/bvaughn/react-error-boundary/issues/145): Removed explicit `ErrorBoundary.render` return type to avoid TypeScript error: > 'ErrorBoundary' cannot be used as a JSX component. ### [`v4.0.8`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.8) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.7...4.0.8) - [144](https://togithub.com/bvaughn/react-error-boundary/pull/144): Build release bundle with Preconstruct ### [`v4.0.7`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.7) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.6...4.0.7) \*Replaced post-processing `"use client"` insertion step with a custom Parcel plug-in. This should hopefully produce better source maps. ### [`v4.0.6`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.6) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.5...4.0.6) - Removed arrow function syntax to support older versions of Safari ### [`v4.0.5`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.5) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.4...4.0.5) Move `"use client"` directive to top of the bundled file. ### [`v4.0.4`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.4) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.3...4.0.4) README changes only ### [`v4.0.3`](https://togithub.com/bvaughn/react-error-boundary/releases/tag/4.0.3) [Compare Source](https://togithub.com/bvaughn/react-error-boundary/compare/4.0.2...4.0.3) - `withErrorBoundary` forwards refs - Add `"use client"` directive ### [`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 - "before 3am on Monday" (UTC), 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.

[ ] If you want to rebase/retry this PR, check this box

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
mdx	❌ Failed (Inspect)			Mar 27, 2023 at 1:04AM (UTC)

codecov-commenter commented 1 year ago

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (d8a62d2) 100.00% compared to head (53b9b0b) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #2278 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 22 22 Lines 2177 2177 ========================================= Hits 2177 2177 ``` | [Impacted Files](https://codecov.io/gh/mdx-js/mdx/pull/2278?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None) | Coverage Δ | | |---|---|---| | [packages/mdx/lib/run.js](https://codecov.io/gh/mdx-js/mdx/pull/2278?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None#diff-cGFja2FnZXMvbWR4L2xpYi9ydW4uanM=) | `100.00% <100.00%> (ø)` | | Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

mdx-js / mdx