Bump react-error-boundary from 3.1.4 to 4.0.4

[dependabot]

Bumps react-error-boundary from 3.1.4 to 4.0.4.

Release notes

Sourced from react-error-boundary's releases.

4.0.4

README changes only

4.0.3

• withErrorBoundary forwards refs
• Add "use client" directive

4.0.2

Fix broken TypeScript definitions file (#133, parcel-bundler/parcel#8908)

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:

import { useErrorBoundary } from "react-error-boundary";
function ErrorFallback({ error }) {
const { resetBoundary } = useErrorBoundary();
return (
<div role="alert">
<p>Something went wrong:</p>
<pre style={{ color: "red" }}>{error.message}</pre>
<button onClick={resetBoundary}>Try again</button>
</div>
);
}

See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf

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.

// Before
function Greeting() {
  const [name, setName] = React.useState('')
  const {greeting, error} = useGreeting(name)
</tr></table> 

... (truncated)

Commits

• b323179 4.0.3 -> 4.0.4
• 7db7c9d Update README
• 7213c54 4.0.2 -> 4.0.3
• ce3668d withErrorBoundary forwards refs
• e7966d5 Merge pull request #130 from eps1lon/rsc-directive
• 050aecb Add "use client" directive
• 3893cab 4.0.1 -> 4.0.2
• bbeeb9a Merge pull request #134 from bvaughn/issues/133
• 63339c3 Workaround for bad TypeScript defs file (#133)
• cbbf3b0 De-emphasized outdated blog post
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #73.