Bump use-debounce from 9.0.4 to 10.0.0

[dependabot]

Bumps use-debounce from 9.0.4 to 10.0.0.

Release notes

Sourced from use-debounce's releases.

v10.0.0

• ❗️ [Major breaking change] replaced index.modern.js with index.mjs. Might require a little change in your build pipeline
• ❗️ [Major breaking change] New option debounceOnServer: if you put the option to true, it will run debouncing on server (via setTimeout). 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.
• ❕[Minor breaking change]: Replaced useState for useDebounce with useReducer. 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-equal
• ❕[Minor breaking change]: useDebouncedCallback 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.
• ℹ Lib size:
  • 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
• ℹ [Internal] Replaced Enzyme with testing-library
• ℹ [Internal] yarn classic => npm
• ℹ [Internal] Updated devDependencies

Changelog

Sourced from use-debounce's changelog.

10.0.0

• Major breaking change: replaced index.modern.js with index.mjs. Might require a little change in your build pipeline
• Major breaking change: New option debounceOnServer: if you put the option to true, it will run debouncing on server (via setTimeout). 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.
• Minor breaking change: Replaced useState for useDebounce with useReducer. 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-equal
• Minor breaking change: useDebouncedCallback 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.
• Lib size: 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
• [Internal] Replaced Enzyme with @​testing-library
• [Internal] yarn classic => npm
• [Internal] Updated devDependencies

Commits

• 24fc538 Merge pull request #168 from xnimorz/yarn_to_npm
• 1228b30 upd readme
• b928077 Merge pull request #167 from xnimorz/yarn_to_npm
• 3dfaf50 introduce debounceOnServer param for UseDebouncedCallback
• e69efea cache the newest function for useDebouncedCallback
• 7d15997 Replace useState with useReducer
• b1b0eb6 Add unit test to verify that function is possible to be debounced
• af3ff29 Update build pipeline
• de12bcc update github actions
• 6b568e8 update prettier
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Thank you for your interest in contributing to WooCommerce!

WooCommerce Blocks has been merged into the WooCommerce Monorepo.

From now on, please open any issues or pull requests in the woocommerce/woocommerce repository.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.