fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@reduxjs/toolkit (source)	^1.8.4 -> ^1.8.5
@types/inquirer	^8.2.2 -> ^8.2.3
@types/jest	^28.1.6 -> ^28.1.7
@types/node	^16.11.48 -> ^16.11.51
@typescript-eslint/eslint-plugin	^5.33.0 -> ^5.33.1
@typescript-eslint/parser	^5.33.0 -> ^5.33.1
eslint-plugin-jest	^26.8.3 -> ^26.8.4
eslint-plugin-jsonc	^2.3.1 -> ^2.4.0
lerna (source)	^5.4.2 -> ^5.4.3
postcss-preset-env	^7.7.2 -> ^7.8.0
terser-webpack-plugin	^5.3.4 -> ^5.3.5
undici (source)	^5.8.2 -> ^5.9.1
webpack-bundle-analyzer	^4.5.0 -> ^4.6.0

---

Release Notes

reduxjs/redux-toolkit

v1.8.5

Compare Source

This bugfix releas fixes an issue with large keepUnusedDataFor values overflowing JS timers, exports the types for the Redux DevTools Extension option, and and improves behavior of URL string generation.

Changelog

keepUnusedDataFor Timer Fix

keepUnusedDataFor accepts a value in seconds. When there are no more active subscriptions for a piece of data, RTKQ will set a timer using setTimeout, and keepUnusedDataFor * 1000 as the timer value.

We've been advising users that if they want to keep data in the cache forever that they should use a very large value for keepUnusedDataFor, such as 10 years in seconds.

However, it turns out that JS engines use a 32-bit signed int for timers, and 32-bits in milliseconds is only 24.8 days. If a timer is given a value larger than that, it triggers immediately.

We've updated the internal logic to clamp the keepUnusedDataFor value to be between 0 and THIRTY_TWO_BIT_MAX_TIMER_SECONDS - 1.

Note that in RTK 1.9 (coming soon), RTKQ will also accept Infinity as a special keepUnusedDataFor value to indicate cached data should never be expired.

Other Changes

RTK inlines the TS types for the Redux DevTools Extension options to avoid an extra dependency, but the TS type for the options object wasn't exported publicly. We now export the DevToolsEnhancerOptions type.

The logic for generating a final URL has been updated to avoid adding an extra trailing /.

What's Changed

• Prevent keepUnusedDataFor values from overflowing setTimeout counter by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2595
• remove typeof undefined checks where not necessary 🐃🪒 by @​phryneas in https://github.com/reduxjs/redux-toolkit/pull/1726
• Update RDT options types, and export those + AnyListenerPredicate by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/2596
• Ensures there is no unexpected slash in url before query params by @​ygrishajev in https://github.com/reduxjs/redux-toolkit/pull/2470

Full Changelog: reduxjs/redux-toolkit@v1.8.4...v1.8.5

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.33.1

Compare Source

Bug Fixes

• missing placeholders in violation messages for no-unnecessary-type-constraint and no-unsafe-argument (and enable eslint-plugin/recommended rules internally) (#​5453) (d023910)

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.33.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

jest-community/eslint-plugin-jest

v26.8.4

Compare Source

Bug Fixes

• prefer-mock-promise-shorthand: ignore mockImplementation functions that have parameters (#​1199) (78ccbef)

ota-meshi/eslint-plugin-jsonc

v2.4.0

Compare Source

🐛 Bug Fixes

• Properly exclude "off" rules in jsonc/auto rule by @​clemyan in https://github.com/ota-meshi/eslint-plugin-jsonc/pull/188

New Contributors

• @​clemyan made their first contribution in https://github.com/ota-meshi/eslint-plugin-jsonc/pull/188

Full Changelog: ota-meshi/eslint-plugin-jsonc@v2.3.1...v2.4.0

lerna/lerna

v5.4.3

Compare Source

Note: Version bump only for package lerna

csstools/postcss-plugins

v7.8.0

Compare Source

• Added @csstools/postcss-nested-calc
  Check the plugin README for usage details.
• Added @csstools/postcss-text-decoration-shorthand
  Check the plugin README for usage details.
• Update @csstools/postcss-cascade-layers to 1.0.5 (patch)
• Update @csstools/postcss-color-function to 1.1.1 (patch)
• Update @csstools/postcss-font-format-keywords to 1.0.1 (patch)
• Update @csstools/postcss-hwb-function to 1.0.2 (patch)
• Update @csstools/postcss-ic-unit to 1.0.1 (patch)
• Update @csstools/postcss-is-pseudo-class to 2.0.7 (patch)
• Update @csstools/postcss-normalize-display-values to 1.0.1 (patch)
• Update @csstools/postcss-oklab-function to 1.1.1 (patch)
• Update @csstools/postcss-stepped-value-functions to 1.0.1 (patch)
• Update @csstools/postcss-trigonometric-functions to 1.0.2 (patch)
• Update @csstools/postcss-unset-value to 1.0.2 (patch)
• Update autoprefixer to 10.4.8 (patch)
• Update browserslist to 4.21.3 (patch)
• Update cssdb to 7.0.0 (major)
• Update postcss-attribute-case-insensitive to 5.0.2 (patch)
• Update postcss-color-functional-notation to 4.2.4 (patch)
• Update postcss-color-rebeccapurple to 7.1.1 (patch)
• Update postcss-dir-pseudo-class to 6.0.5 (patch)
• Update postcss-double-position-gradients to 3.1.2 (patch)
• Update postcss-gap-properties to 3.0.5 (patch)
• Update postcss-image-set-function to 4.0.7 (patch)
• Update postcss-lab-function to 4.2.1 (patch)
• Update postcss-nesting to 10.1.10 (patch)
• Update postcss-overflow-shorthand to 3.0.4 (patch)
• Update postcss-place to 7.0.5 (patch)
• Update postcss-pseudo-class-any-link to 7.1.6 (patch)
• Update postcss-selector-not to 6.0.1 (patch)

webpack-contrib/terser-webpack-plugin

v5.3.5

Compare Source

nodejs/undici

v5.9.1

What's Changed

• fix: don't timeout while waiting for client to send request (#​1604)
• Fix array headers by @​mateonunez in https://github.com/nodejs/undici/pull/1598
• fix(fetch): implement fully read body algorithm by @​KhafraDev in https://github.com/nodejs/undici/pull/1597
• fix: add support for integrity option to Fetch by @​jelmervdl in https://github.com/nodejs/undici/pull/1596
• fix(File): respect typed array byteOffset and byteLength by @​mrbbot in https://github.com/nodejs/undici/pull/1601

New Contributors

• @​mateonunez made their first contribution in https://github.com/nodejs/undici/pull/1598
• @​jelmervdl made their first contribution in https://github.com/nodejs/undici/pull/1596
• @​mrbbot made their first contribution in https://github.com/nodejs/undici/pull/1601

Full Changelog: nodejs/undici@v5.8.2...v5.9.1

webpack-contrib/webpack-bundle-analyzer

v4.6.0

Compare Source

• New Feature
  • Support outputting different URL in server mode (#​520 by @​southorange1228)
  • Use deterministic chunk colors (#501 by @​CreativeTechGuy)

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #798 (8ada739) into main (59e0064) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #798   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines           57        57           
  Branches         2         2           
=========================================
  Hits            57        57           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[pull-request-quantifier-deprecated]

This PR has 34 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +17 -17
Percentile : 13.6%

Total files changed: 8

Change summary by file extension:
.json : +17 -17
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.