chore(deps): update dependency react-error-boundary to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-error-boundary (source)	3.1.4 → 6.1.0

---

Release Notes

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

v6.1.0

Compare Source

v6.0.3

Compare Source

• Removed react-dom from peer dependencies list; it was accidentally added during a previous internal refactor

v6.0.2

Compare Source

Updated README and generated TS docs

v6.0.1

Compare Source

v6.0.0

Compare Source

Module is ESM-only in order to better work with modern tooling.

v5.0.0

Compare Source

Update withErrorBoundary types to be compatible with the latest forwardRef types

For more background see PR #​211

v4.1.2

Compare Source

• Remove engines field from Package JSON entirely

v4.1.1

Compare Source

• Remove node constraint from engines

v4.1.0

Compare Source

• Relax fallback prop to support broader ReactNode type

v4.0.13

Compare Source

Removed references to ESLint config kcd-scripts from package.json

v4.0.12

Compare Source

• Support null fallback prop (#​169)

v4.0.11

Compare Source

• Re-throw original error in the event that no fallback is specified (#​160)
• Improved exported prop types def (#​152)
• Bundle built with Preconstruct (#​144, #​149, 9b7b15b)

v4.0.10

Compare Source

• Target Safari 12+ compatibility (by removing optional chaining operator and default parameters)

v4.0.9

Compare Source

• 145: Removed explicit ErrorBoundary.render return type to avoid TypeScript error:

'ErrorBoundary' cannot be used as a JSX component.

v4.0.8

Compare Source

• 144: Build release bundle with Preconstruct

v4.0.7

Compare Source

*Replaced post-processing "use client" insertion step with a custom Parcel plug-in. This should hopefully produce better source maps.

v4.0.6

Compare Source

• Removed arrow function syntax to support older versions of Safari

v4.0.5

Compare Source

Move "use client" directive to top of the bundled file.

v4.0.4

Compare Source

README changes only

v4.0.3

Compare Source

• withErrorBoundary forwards refs
• Add "use client" directive

v4.0.2

Compare Source

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

v4.0.1

Compare Source

• 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

v4.0.0

Compare Source

• 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)
  useErrorHandler(error)

// 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:

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.

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>
  );
}

---

Configuration

📅 Schedule: Branch creation - "after 7pm every weekday,before 5am every weekday" in timezone Europe/Madrid, 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 was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
unleash-docs	Ignored	Preview	Jan 16, 2026 0:39am

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/react-error-boundary	6.1.0	🟢 4.1	Details Check Score Reason Maintained 🟢 10 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 Binary-Artifacts 🟢 10 no binaries found in the repo Code-Review ⚠️ 0 Found 0/30 approved changesets -- score normalized to 0 Packaging ⚠️ -1 packaging workflow not detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches Signed-Releases ⚠️ -1 no releases found Security-Policy ⚠️ 0 security policy file not detected Vulnerabilities 🟢 7 3 existing vulnerabilities detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• frontend/yarn.lock