Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
May 28, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 22, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

bvaughn/react-error-boundary

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, https://github.com/parcel-bundler/parcel/issues/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 - 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.


  • 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
Copy link

vercel bot commented Mar 22, 2023

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

Name Status Preview Comments Updated (UTC)
gqty ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 17, 2023 9:22pm

@renovate
Copy link
Contributor Author

renovate bot commented Apr 6, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
installing v2 tool node v18.16.0
linking tool node v18.16.0
node: v18.16.0 /usr/local/bin/node
npm: 9.5.1  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 7 seconds
installing v2 tool pnpm v8.5.1
linking tool pnpm v8.5.1
8.5.1
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 5 seconds
Scope: all 15 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 8, reused 0, downloaded 0, added 0
Progress: resolved 16, reused 0, downloaded 11, added 0
Progress: resolved 22, reused 0, downloaded 15, added 0
Progress: resolved 29, reused 0, downloaded 23, added 0
Progress: resolved 36, reused 0, downloaded 30, added 0
Progress: resolved 39, reused 0, downloaded 32, added 0
Progress: resolved 43, reused 0, downloaded 35, added 0
examples/vite-example                    |  WARN  deprecated @vitejs/[email protected]
Progress: resolved 46, reused 0, downloaded 39, added 0
Progress: resolved 50, reused 0, downloaded 44, added 0
Progress: resolved 54, reused 0, downloaded 45, added 0
Progress: resolved 59, reused 0, downloaded 50, added 0
Progress: resolved 63, reused 0, downloaded 52, added 0
Progress: resolved 66, reused 0, downloaded 57, added 0
Progress: resolved 70, reused 0, downloaded 63, added 0
Progress: resolved 74, reused 0, downloaded 66, added 0
Progress: resolved 76, reused 0, downloaded 71, added 0
Progress: resolved 81, reused 0, downloaded 76, added 0
Progress: resolved 90, reused 0, downloaded 81, added 0
Progress: resolved 100, reused 0, downloaded 93, added 0
Progress: resolved 105, reused 0, downloaded 99, added 0
Progress: resolved 109, reused 0, downloaded 104, added 0
Progress: resolved 116, reused 0, downloaded 112, added 0
Progress: resolved 122, reused 0, downloaded 117, added 0
Progress: resolved 130, reused 0, downloaded 122, added 0
Progress: resolved 131, reused 0, downloaded 125, added 0
Progress: resolved 132, reused 0, downloaded 127, added 0
Progress: resolved 133, reused 0, downloaded 127, added 0
Progress: resolved 135, reused 0, downloaded 128, added 0
Progress: resolved 135, reused 0, downloaded 129, added 0
Progress: resolved 135, reused 0, downloaded 131, added 0
Progress: resolved 135, reused 0, downloaded 132, added 0
Progress: resolved 135, reused 0, downloaded 133, added 0
Progress: resolved 136, reused 0, downloaded 133, added 0
Progress: resolved 136, reused 0, downloaded 134, added 0
Progress: resolved 137, reused 0, downloaded 134, added 0
Progress: resolved 138, reused 0, downloaded 134, added 0
Progress: resolved 159, reused 0, downloaded 135, added 0
Progress: resolved 178, reused 0, downloaded 152, added 0
Progress: resolved 194, reused 0, downloaded 169, added 0
Progress: resolved 202, reused 0, downloaded 181, added 0
Progress: resolved 211, reused 0, downloaded 186, added 0
Progress: resolved 220, reused 0, downloaded 199, added 0
Progress: resolved 233, reused 0, downloaded 214, added 0
Progress: resolved 248, reused 0, downloaded 226, added 0
Progress: resolved 261, reused 0, downloaded 239, added 0
Progress: resolved 275, reused 0, downloaded 251, added 0
Progress: resolved 284, reused 0, downloaded 260, added 0
Progress: resolved 302, reused 0, downloaded 272, added 0
Progress: resolved 314, reused 0, downloaded 288, added 0
Progress: resolved 328, reused 0, downloaded 301, added 0
Progress: resolved 367, reused 0, downloaded 346, added 0
Progress: resolved 393, reused 0, downloaded 369, added 0
Progress: resolved 405, reused 0, downloaded 380, added 0
Progress: resolved 421, reused 0, downloaded 398, added 0
Progress: resolved 428, reused 0, downloaded 405, added 0
Progress: resolved 433, reused 0, downloaded 409, added 0
Progress: resolved 439, reused 0, downloaded 416, added 0
Progress: resolved 448, reused 0, downloaded 422, added 0
Progress: resolved 460, reused 0, downloaded 434, added 0
Progress: resolved 474, reused 0, downloaded 450, added 0
Progress: resolved 485, reused 0, downloaded 458, added 0
Progress: resolved 494, reused 0, downloaded 468, added 0
Progress: resolved 505, reused 0, downloaded 479, added 0
Progress: resolved 521, reused 0, downloaded 493, added 0
Progress: resolved 545, reused 0, downloaded 516, added 0
Progress: resolved 558, reused 0, downloaded 531, added 0
Progress: resolved 578, reused 0, downloaded 549, added 0
Progress: resolved 603, reused 0, downloaded 576, added 0
Progress: resolved 626, reused 0, downloaded 596, added 0
Progress: resolved 651, reused 0, downloaded 624, added 0
Progress: resolved 675, reused 0, downloaded 650, added 0
Progress: resolved 691, reused 0, downloaded 668, added 0
Progress: resolved 716, reused 0, downloaded 691, added 0
Progress: resolved 751, reused 0, downloaded 728, added 0
Progress: resolved 777, reused 0, downloaded 749, added 0
Progress: resolved 806, reused 0, downloaded 775, added 0
Progress: resolved 824, reused 0, downloaded 798, added 0
Progress: resolved 863, reused 0, downloaded 831, added 0
Progress: resolved 896, reused 0, downloaded 864, added 0
Progress: resolved 916, reused 0, downloaded 891, added 0
Progress: resolved 951, reused 0, downloaded 922, added 0
Progress: resolved 967, reused 0, downloaded 925, added 0
Progress: resolved 970, reused 0, downloaded 926, added 0
Progress: resolved 987, reused 0, downloaded 940, added 0
Progress: resolved 1018, reused 0, downloaded 970, added 0
Progress: resolved 1051, reused 0, downloaded 999, added 0
Progress: resolved 1072, reused 0, downloaded 1020, added 0
examples/ez-react-next                   |  WARN  deprecated [email protected]
Progress: resolved 1092, reused 0, downloaded 1043, added 0
Progress: resolved 1106, reused 0, downloaded 1060, added 0
Progress: resolved 1126, reused 0, downloaded 1077, added 0
Progress: resolved 1162, reused 0, downloaded 1110, added 0
Progress: resolved 1185, reused 0, downloaded 1133, added 0
Progress: resolved 1211, reused 0, downloaded 1166, added 0
Progress: resolved 1224, reused 0, downloaded 1181, added 0
Progress: resolved 1247, reused 0, downloaded 1202, added 0
Progress: resolved 1265, reused 0, downloaded 1220, added 0
Progress: resolved 1274, reused 0, downloaded 1228, added 0
Progress: resolved 1306, reused 0, downloaded 1256, added 0
Progress: resolved 1327, reused 0, downloaded 1275, added 0
Progress: resolved 1345, reused 0, downloaded 1296, added 0
Progress: resolved 1369, reused 0, downloaded 1324, added 0
Progress: resolved 1389, reused 0, downloaded 1345, added 0
Progress: resolved 1426, reused 0, downloaded 1380, added 0
Progress: resolved 1456, reused 0, downloaded 1406, added 0
Progress: resolved 1470, reused 0, downloaded 1417, added 0
Progress: resolved 1493, reused 0, downloaded 1444, added 0
Progress: resolved 1519, reused 0, downloaded 1474, added 0
Progress: resolved 1536, reused 0, downloaded 1487, added 0
Progress: resolved 1555, reused 0, downloaded 1507, added 0
Progress: resolved 1588, reused 0, downloaded 1543, added 0
Progress: resolved 1604, reused 0, downloaded 1555, added 0
Progress: resolved 1624, reused 0, downloaded 1574, added 0
Progress: resolved 1647, reused 0, downloaded 1594, added 0
Progress: resolved 1663, reused 0, downloaded 1615, added 0
Progress: resolved 1700, reused 0, downloaded 1646, added 0
Progress: resolved 1707, reused 0, downloaded 1668, added 0
Progress: resolved 1707, reused 0, downloaded 1670, added 0
Progress: resolved 1708, reused 0, downloaded 1670, added 0
Progress: resolved 1741, reused 0, downloaded 1696, added 0
 ENOENT  ENOENT: no such file or directory, scandir '/mnt/renovate/gh/gqty-dev/gqty/packages/cli/dist'



Progress: resolved 1752, reused 0, downloaded 1714, added 0

@renovate renovate bot force-pushed the renovate/react-error-boundary-4.x branch from 5b448dd to 6180ef1 Compare April 6, 2023 10:30
@renovate renovate bot force-pushed the renovate/react-error-boundary-4.x branch from 6180ef1 to 7c187a7 Compare April 17, 2023 21:20
@renovate renovate bot force-pushed the renovate/react-error-boundary-4.x branch from 7c187a7 to a1aa084 Compare May 27, 2023 19:24
@renovate renovate bot force-pushed the renovate/react-error-boundary-4.x branch from a1aa084 to 3c67501 Compare May 27, 2023 22:24
@vicary vicary merged commit bb81e3f into main May 28, 2023
@vicary vicary deleted the renovate/react-error-boundary-4.x branch May 28, 2023 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant