fix(deps): update dependency use-debounce to v10 #78
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:
9.0.2
->10.0.4
Release Notes
xnimorz/use-debounce (use-debounce)
v10.0.4
Compare Source
v10.0.3
Compare Source
peerDependency
part frompackage.json
as NPM cannot correctly resolvepeerDependency
for beta and rc versions: see https://stackoverflow.com/questions/67934358/npm-including-all-range-of-pre-release-when-defining-peer-dependency for contextv10.0.2
Compare Source
isPending
does not reset the state if the tracked value hasn't changed.. See https://github.com/xnimorz/use-debounce/issues/178v10.0.1
Compare Source
v10.0.0
Compare Source
index.modern.js
withindex.mjs
. Might require a little change in your build pipelinedebounceOnServer
: if you put the option to true, it will run debouncing on server (viasetTimeout
). The new option can break your current server behaviour, as v9.x, it runs all the time and might cause unnessesary server CPU utilisation. Now, by default, debounced callbacks do not happen on server.useState
foruseDebounce
withuseReducer
. It might lead to reduced amount of re-renders, as useState is known to have excess re-renders in some corner: https://stackoverflow.com/questions/57652176/react-hooks-usestate-setvalue-still-rerender-one-more-time-when-value-is-equaluseDebouncedCallback
now updates function to call asap. Meaning, if you re-called the hook and it should trigger immediately, it will trigger the newest function all the time.914 B: index.js.gz
851 B: index.js.br
883 B: index.mjs.gz
826 B: index.mjs.br
938 B: index.module.js.gz
873 B: index.module.js.br
989 B: index.umd.js.gz
919 B: index.umd.js.br
v9.0.4
Compare Source
v9.0.3
Compare Source
Configuration
📅 Schedule: Branch creation - "every 2 weeks on Monday before 7am" in timezone Europe/Berlin, 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.
This PR was generated by Mend Renovate. View the repository job log.