-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Conversation
|
9698d43
to
34939ee
Compare
0683289
to
1aec662
Compare
8b5e72e
to
8ad78b2
Compare
287ceea
to
ec2b614
Compare
52f72bb
to
ca8ec8b
Compare
ca8ec8b
to
574301a
Compare
574301a
to
3da35cd
Compare
size-limit report 📦
|
d39ba22
to
54cb012
Compare
54cb012
to
ec9dfdb
Compare
483043d
to
6fb8e4b
Compare
ec35c43
to
599f7b4
Compare
599f7b4
to
8cb308e
Compare
8cb308e
to
131c1de
Compare
fec4e21
to
a982b56
Compare
This PR contains the following updates:
3.1.8
->4.0.0
7.0.2
->8.0.0
3.1.4
->4.0.11
Release Notes
lquixada/cross-fetch (cross-fetch)
v4.0.0
Compare Source
ds300/patch-package (patch-package)
v8.0.0
Compare Source
Breaking Changes
bvaughn/react-error-boundary (react-error-boundary)
v4.0.11
Compare Source
9b7b15b
)v4.0.10
Compare Source
v4.0.9
Compare Source
v4.0.8
Compare Source
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
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"use client"
directivev4.0.2
Compare Source
Fix broken TypeScript definitions file (#133, https://github.com/parcel-bundler/parcel/issues/8908)
v4.0.1
Compare Source
ErrorBoundaryContext
around fallback UI as well, so theuseErrorBoundary
hook could be used within the fallback component to reset the boundary.For example:
See this demo: https://codesandbox.io/s/nostalgic-browser-e9lpmf
v4.0.0
Compare Source
useErrorHandler
hook withuseErrorBoundary
; can be used to trigger an error boundary or dismiss oneonReset
andonResetKeys
props; pass "details" object explaining the cause of the resetWhy did the
useErrorHandler
hook change?The old hook had two design flaws, both related to the
givenError
parameter:throw
this value. This seemed unnecessary, because if a component already has a reference to an error during render, it can justthrow
the value itself.null
orundefined
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.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:
Dismiss the nearest error boundary
A fallback component can use this hook to request the nearest error boundary retry the render that original failed.
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.
This PR has been generated by Mend Renovate. View repository job log here.