Build(deps): Bump react-error-boundary from 3.1.4 to 4.1.0 in /catalog/ui

[dependabot]

Bumps react-error-boundary from 3.1.4 to 4.1.0.

Release notes

Sourced from react-error-boundary's releases.

4.0.13

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

4.0.12

• Support null fallback prop (#169)

4.0.11

• 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, 9b7b15bc29829b2a145c047ef188fecb90c9894e)

4.0.10

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

4.0.9

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

'ErrorBoundary' cannot be used as a JSX component.

4.0.8

• 144: Build release bundle with Preconstruct

4.0.7

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

4.0.6

• Removed arrow function syntax to support older versions of Safari

4.0.5

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

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();
</tr></table>

... (truncated)

Commits

• 96bb333 4.0.12 -> 4.1.0
• 206bdba Upgrade pnpm v8 -> v9 (#198)
• 23167c5 Relax fallback prop to support broader ReactNode type
• 4aaf9b0 chore: update CI workflows version to v4 and node version to 20 (#194)
• f75bc7f fix: change the script from npm to pnpm (#186)
• 15f1ba2 Update README.md (#180)
• ed6d112 ci(eslint): use eslint+prettier with ci strictly (#165)
• 54a2838 Support null fallback prop
• 23a4d77 Fix assertion helper function
• 8c40f40 Merge branch 'master' of github.com:bvaughn/react-error-boundary
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.