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

chore(deps): update all devdependencies (major) #11148

Merged
merged 1 commit into from
Nov 27, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 12, 2023

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cross-fetch 3.1.8 -> 4.0.0 age adoption passing confidence
patch-package 7.0.2 -> 8.0.0 age adoption passing confidence
react-error-boundary 3.1.4 -> 4.0.11 age adoption passing confidence

Release Notes

lquixada/cross-fetch (cross-fetch)

v4.0.0

Compare Source

ds300/patch-package (patch-package)

v8.0.0

Compare Source

  • Add support for multiple patch files for a single package. #​474
Breaking Changes
  • Removed support for some very old legacy filename format stuff (pre-2019).
bvaughn/react-error-boundary (react-error-boundary)

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

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, 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 - "every weekend" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.

@changeset-bot
Copy link

changeset-bot bot commented Aug 12, 2023

⚠️ No Changeset found

Latest commit: a982b56

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from 9698d43 to 34939ee Compare August 19, 2023 07:15
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from 0683289 to 1aec662 Compare September 2, 2023 07:58
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from 8b5e72e to 8ad78b2 Compare September 15, 2023 14:05
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 287ceea to ec2b614 Compare September 24, 2023 22:10
@renovate renovate bot force-pushed the renovate/major-all-dev branch 3 times, most recently from 52f72bb to ca8ec8b Compare October 7, 2023 07:29
@renovate renovate bot force-pushed the renovate/major-all-dev branch from ca8ec8b to 574301a Compare October 14, 2023 10:04
@renovate renovate bot force-pushed the renovate/major-all-dev branch from 574301a to 3da35cd Compare October 16, 2023 17:47
@github-actions
Copy link
Contributor

github-actions bot commented Oct 16, 2023

size-limit report 📦

Path Size
dist/apollo-client.min.cjs 37.08 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/main.cjs" 43.51 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/main.cjs" (production) 42.01 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/index.js" 32.61 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "dist/index.js" (production) 31.27 KB (0%)
import { ApolloProvider } from "dist/react/index.js" 1.22 KB (0%)
import { ApolloProvider } from "dist/react/index.js" (production) 1.2 KB (0%)
import { useQuery } from "dist/react/index.js" 4.28 KB (0%)
import { useQuery } from "dist/react/index.js" (production) 4.1 KB (0%)
import { useLazyQuery } from "dist/react/index.js" 4.59 KB (0%)
import { useLazyQuery } from "dist/react/index.js" (production) 4.41 KB (0%)
import { useMutation } from "dist/react/index.js" 2.55 KB (0%)
import { useMutation } from "dist/react/index.js" (production) 2.53 KB (0%)
import { useSubscription } from "dist/react/index.js" 2.24 KB (0%)
import { useSubscription } from "dist/react/index.js" (production) 2.2 KB (0%)
import { useSuspenseQuery } from "dist/react/index.js" 4.62 KB (0%)
import { useSuspenseQuery } from "dist/react/index.js" (production) 4.05 KB (0%)
import { useBackgroundQuery } from "dist/react/index.js" 4.14 KB (0%)
import { useBackgroundQuery } from "dist/react/index.js" (production) 3.56 KB (0%)
import { useReadQuery } from "dist/react/index.js" 2.99 KB (0%)
import { useReadQuery } from "dist/react/index.js" (production) 2.94 KB (0%)
import { useFragment } from "dist/react/index.js" 2.09 KB (0%)
import { useFragment } from "dist/react/index.js" (production) 2.04 KB (0%)

@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from d39ba22 to 54cb012 Compare October 28, 2023 07:06
@renovate renovate bot force-pushed the renovate/major-all-dev branch from 54cb012 to ec9dfdb Compare November 4, 2023 07:41
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from 483043d to 6fb8e4b Compare November 13, 2023 01:58
@renovate renovate bot force-pushed the renovate/major-all-dev branch 2 times, most recently from ec35c43 to 599f7b4 Compare November 25, 2023 10:45
@renovate renovate bot force-pushed the renovate/major-all-dev branch from 599f7b4 to 8cb308e Compare November 27, 2023 14:35
@phryneas phryneas mentioned this pull request Nov 27, 2023
3 tasks
@renovate renovate bot force-pushed the renovate/major-all-dev branch from 8cb308e to 131c1de Compare November 27, 2023 14:48
@renovate renovate bot force-pushed the renovate/major-all-dev branch from fec4e21 to a982b56 Compare November 27, 2023 14:55
@phryneas phryneas merged commit f373f01 into main Nov 27, 2023
25 checks passed
@phryneas phryneas deleted the renovate/major-all-dev branch November 27, 2023 15:07
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants