fix(deps): update dependency use-debounce to v10 #49
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:
7.0.1->10.0.6Release Notes
xnimorz/use-debounce (use-debounce)
v10.0.6Compare Source
What's Changed
Full Changelog: xnimorz/use-debounce@10.0.5...10.0.6
v10.0.5Compare Source
v10.0.4Compare Source
v10.0.3Compare Source
peerDependencypart frompackage.jsonas NPM cannot correctly resolvepeerDependencyfor beta and rc versions: see https://stackoverflow.com/questions/67934358/npm-including-all-range-of-pre-release-when-defining-peer-dependency for contextv10.0.2Compare Source
isPendingdoes not reset the state if the tracked value hasn't changed.. See #178v10.0.1Compare Source
v10.0.0Compare Source
index.modern.jswithindex.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.useStateforuseDebouncewithuseReducer. 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-equaluseDebouncedCallbacknow 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.4Compare Source
v9.0.3Compare Source
v9.0.2Compare Source
v9.0.1Compare Source
Fix the bug with the incorrect import path. Now it's index.cjs, instead of index.js
v9.0.0Compare Source
dist/index.jsis changed. Now it'sdist/index.cjs.v8.0.4Compare Source
useDebouncedCallbackargs: #140 Thanks to @sarunastv8.0.3Compare Source
typesto package json to mitigate microsoft/TypeScript#49160. #138 Thanks to @wuzzebv8.0.2Compare Source
v8.0.1Compare Source
v8.0.0Compare Source
useDebouncechanged its build system to microbundle. For now we have several entries:index.jsis for commonJS approachindex.modern.jsfor esnext module systemindex.umd.jsfor UMD.All the files are in
distfolder.If you have any paths which have
esmorlib, please, replace them todist:Before:
After:
useDebouncebehaviour with react-devtools tab when devtools have a component withuseDebounceoruseDebounceCallbackopened. #129 Thanks to @alexniarchos for reportingleading: true#124 Thanks to @mntnoe for reportingConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.