chore(deps): update all devdependencies (major) #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.61.0->6.3.05.61.0->6.3.03.1.8->4.0.05.11.1->6.0.08.1.0->10.3.37.0.2->8.0.03.1.4->4.0.11Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.3.0Compare Source
Bug Fixes
allowTypeImportsenabled (#7379) (cc9a46d)Features
ignorePrimitivesoption to betrue(#7331) (dfcafae)Reverts
You can read about our versioning strategy and releases on our website.
6.2.1 (2023-07-31)
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.2.1Compare Source
Bug Fixes
You can read about our versioning strategy and releases on our website.
v6.2.0Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.1.0Compare Source
Bug Fixes
Features
You can read about our versioning strategy and releases on our website.
v6.0.0Compare Source
Bug Fixes
exportsfield in package.json files (#6550) (53776c2)chore
Features
rule-tester(#6777) (2ce1c1d)RuleTesterin/utilsin favour of the new/rule-testerpackage (#6816) (c33f497)BREAKING CHANGES
You can read about our versioning strategy and releases on our website.
v5.62.0Compare Source
Bug Fixes
Features
ignorePrimitivesoption (#6487) (6edaa04)You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.3.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
6.2.1 (2023-07-31)
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.2.1Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.2.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
v6.1.0Compare Source
Features
You can read about our versioning strategy and releases on our website.
v6.0.0Compare Source
Bug Fixes
exportsfield in package.json files (#6550) (53776c2)chore
Features
rule-tester(#6777) (2ce1c1d)BREAKING CHANGES
You can read about our versioning strategy and releases on our website.
v5.62.0Compare Source
Note: Version bump only for package @typescript-eslint/parser
You can read about our versioning strategy and releases on our website.
lquixada/cross-fetch (cross-fetch)
v4.0.0Compare Source
testing-library/eslint-plugin-testing-library (eslint-plugin-testing-library)
v6.0.0Compare Source
You can follow the migration guide to v6.
BREAKING CHANGES
await-async-queryis now calledawait-async-queriesno-await-sync-eventsis now enabled by default in the DOM, Angular & React configsno-await-sync-queryis now calledno-await-sync-queriesno-debugging-utilsnow enables all debug methods in all configs by defaultno-node-accessis now enabled by default in the DOM configawait-fire-eventis now calledawait-async-eventno-global-regexp-flag-in-queryis now enabled by default in all configsno-manual-cleanupis now enabled by default in the React & Vue configsno-render-in-setupis now calledno-render-in-lifecycleprefer-wait-foris now removedBug Fixes
Features
await-async-queries(#665) (c1803df)await-async-event+ add support foruser-event(#652) (b4ce9bb)no-await-sync-queries(#666) (7ed3da8)no-render-in-lifecycle(#649) (9acba43)isaacs/node-glob (glob)
v10.3.3Compare Source
v10.3.2Compare Source
v10.3.1Compare Source
v10.3.0Compare Source
--default -pflag to provide a default patternv10.2.7Compare Source
v10.2.6Compare Source
v10.2.5Compare Source
v10.2.4Compare Source
v10.2.3Compare Source
v10.2.2Compare Source
v10.2.1Compare Source
v10.2.0Compare Source
v10.1.0Compare Source
'.'instead of the empty string''when the currentworking directory is returned as a match.
posix: trueoption to return/delimited paths, even onWindows.
v10.0.0Compare Source
v9.3.5Compare Source
v9.3.4Compare Source
v9.3.3Compare Source
nested extglob patterns.
v9.3.2Compare Source
v9.3.1Compare Source
v9.3.0Compare Source
v9.2.1Compare Source
v9.2.0Compare Source
v9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.2Compare Source
v9.0.1Compare Source
v9.0.0Compare Source
ds300/patch-package (patch-package)
v8.0.0Compare Source
Breaking Changes
bvaughn/react-error-boundary (react-error-boundary)
v4.0.11Compare Source
9b7b15b)v4.0.10Compare Source
v4.0.9Compare Source
ErrorBoundary.renderreturn type to avoid TypeScript error:v4.0.8Compare Source
v4.0.7Compare Source
*Replaced post-processing
"use client"insertion step with a custom Parcel plug-in. This should hopefully produce better source maps.v4.0.6Compare Source
v4.0.5Compare Source
Move
"use client"directive to top of the bundled file.v4.0.4Compare Source
README changes only
v4.0.3Compare Source
withErrorBoundaryforwards refs"use client"directivev4.0.2Compare Source
Fix broken TypeScript definitions file (#133, https://github.com/parcel-bundler/parcel/issues/8908)
v4.0.1Compare Source
ErrorBoundaryContextaround fallback UI as well, so theuseErrorBoundaryhook 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.0Compare Source
useErrorHandlerhook withuseErrorBoundary; can be used to trigger an error boundary or dismiss oneonResetandonResetKeysprops; pass "details" object explaining the cause of the resetWhy did the
useErrorHandlerhook change?The old hook had two design flaws, both related to the
givenErrorparameter:throwthis value. This seemed unnecessary, because if a component already has a reference to an error during render, it can justthrowthe value itself.nullorundefinedvalues. (Although an edge case, JavaScript enables throwing any values/types.)If you were using the
givenErrorfunctionality– you can now just throw the value directly instead.How can I use the new
useErrorHandlerhook?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.