Bump use-debounce from 9.0.4 to 10.0.4

[dependabot]

Bumps use-debounce from 9.0.4 to 10.0.4.

Release notes

Sourced from use-debounce's releases.

v10.0.4

• Fix behaviour for strictMode react when leading is set to true and trailing is true

v10.0.2

• Fixed: isPending does not reset the state if the tracked value hasn't changed.. See xnimorz/use-debounce#178

v10.0.1

• Fixed flush method return args, thanks to @​h

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.4

• Fix behaviour for strictMode react when leading is set to true and trailing is true

10.0.3

• Removed peerDependency part from package.json as NPM cannot correctly resolve peerDependency for beta and rc versions: see https://stackoverflow.com/questions/67934358/npm-including-all-range-of-pre-release-when-defining-peer-dependency for context

10.0.2

• Fixed: isPending does not reset the state if the tracked value hasn't changed.. See xnimorz/use-debounce#178

10.0.1

• Fixed flush method return args, thanks to @​h

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

• 324885c Update version
• cd102d3 Fix React Strict mode behaviour
• 4c27377 Merge pull request #185 from xnimorz/dependabot/npm_and_yarn/rollup-2.79.2
• 7b99fa4 Bump rollup from 2.79.1 to 2.79.2
• 453490e 10.03
• 460b1df Merge pull request #180 from xnimorz/isPending
• da112e0 Fix isPending state
• d4f9cc9 Merge pull request #177 from xnimorz/dependabot/npm_and_yarn/braces-3.0.3
• a6a95cc Bump braces from 3.0.2 to 3.0.3
• 4386acc Merge pull request #176 from xnimorz/dependabot/npm_and_yarn/ws-8.17.1
• 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]

Localization Summary

language	unchanged	added	removed	untranslated
br	875	0	0	79
de	875	0	0	412
en	875	0	0	0
es	875	0	0	403
fr	875	0	0	420
ja	875	0	0	383
ru	875	0	0	393
zh	875	0	0	382

View full summary

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
audioverse-next	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 24, 2024 2:43pm

[github-actions]

📦 Next.js Bundle Analysis for audioverse-next

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page	Size (compressed)
global	242.29 KB (🟢 -26 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Two Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (225 KB)
/[language]/library/history	23.53 KB	265.82 KB	118.14% (+/- <0.01%)
/[language]/library/playlists	23.56 KB	265.85 KB	118.15% (+/- <0.01%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 5% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

[github-actions]

Lighthouse Results

• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/es
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en/discover
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en/teachings/all/page/1
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en/teachings/300
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en/bibles
• https://audioverse-next-4eclqnnqd-audioverse.vercel.app/en/presenters/1309/amanda-anguish

[github-actions]

Accessibility Issues

Code	New	Fixed	Retained	Ignored	Total
WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail	0	0	0	2207	2207
WCAG2AA.Principle2.Guideline2_4.2_4_1.H64.1	0	0	0	129	129

View full summary