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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	^7.20.12 -> ^7.21.0
@reduxjs/toolkit (source)	^1.9.2 -> ^1.9.3
@types/node (source)	^18.14.0 -> ^18.14.1
@typescript-eslint/eslint-plugin	^5.52.0 -> ^5.53.0
@typescript-eslint/parser	^5.52.0 -> ^5.53.0
stylelint (source)	^15.1.0 -> ^15.2.0

---

Release Notes

babel/babel

v7.21.0

Compare Source

🚀 New Feature

• babel-core, babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-proposal-private-methods, babel-plugin-proposal-private-property-in-object
  • #​15435 feat: Implement privateFieldsAsSymbols assumption for classes (@​fwienber)
• babel-helper-create-regexp-features-plugin, babel-plugin-proposal-regexp-modifiers, babel-standalone
  • #​15226 feat: Support regexp modifiers proposal (@​liuxingbaoyu)
• babel-cli, babel-core, babel-generator, babel-plugin-transform-destructuring, babel-plugin-transform-modules-commonjs, babel-plugin-transform-react-jsx, babel-traverse
  • #​15022 feat: Generate sourcemaps of friendly call frames (@​liuxingbaoyu)
• babel-parser, babel-types
  • #​15384 [ts] Support const modifier in type parameters (@​nicolo-ribaudo)
• babel-generator, babel-helpers, babel-parser, babel-plugin-proposal-decorators, babel-plugin-syntax-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​15405 Implement decorators as presented at 2023-01 TC39 meeting (@​nicolo-ribaudo)
• babel-parser
  • #​15114 Parser option to allow new.target outside functions (@​overlookmotel)
  • #​15320 Add annexb: false parser option to disable Annex B (@​nicolo-ribaudo)
• babel-core
  • #​15283 feat: Support .cts as configuration file (@​liuxingbaoyu)
• babel-generator, babel-parser, babel-plugin-transform-typescript
  • #​15381 [ts] Support export type * from (@​nicolo-ribaudo)

🐛 Bug Fix

• babel-plugin-transform-typescript
  • #​15379 [ts5.0] Better inlining of constants in enums (@​liuxingbaoyu)
• babel-core
  • #​15366 handling circular/shared structures in deep-clone (@​azizghuloum)
• babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-proposal-class-static-block, babel-plugin-proposal-private-methods, babel-plugin-transform-classes, babel-plugin-transform-new-target
  • #​15406 Preserve class elements comments in class transform (@​JLHwung)
• babel-parser, babel-plugin-transform-flow-comments, babel-plugin-transform-flow-strip-types, babel-types
  • #​15414 [ts] Fix restrictions for optional parameters (@​nicolo-ribaudo)

💅 Polish

• babel-parser
  • #​15400 polish: improve "await as identifier" error in modules (@​JLHwung)

🏠 Internal

• babel-core
  • #​15137 Improve CJS compat with ESM-based @babel/core (@​nicolo-ribaudo)

🔬 Output optimization

• babel-plugin-transform-typescript
  • #​15418 [ts] Handle exponentiation operator in constant folding (@​ehoogeveen-medweb)

reduxjs/redux-toolkit

v1.9.3

Compare Source

This release fixes a couple issues with the skip/skipToken options for query hooks, and makes a small perf tweak to serializing query args.

Changelog

Skip Behavior

We made a change in v1.9.0 that tried to make some skip behavior more consistent, including clearing out the cached data. However, we had overlooked that our own docs actually said "skipping a query will keep the cached data", and several users pointed this out as they'd been relying on that behavior.

We've reverted that change. Now, setting {skip: true} or skipToken for a query with existing results will keep the data value (reflecting the last successful query), but currentData will be undefined (reflecting the current settings).

We also identified and fixed an issue that could cause subscription entries to leak under a specific combination of timing and settings changes.

Query Arg Serialization Perf

RTKQ relies on serializing query arguments to serve as the cache keys, with the default using JSON.stringify() + some logic for sorting keys. There was a report that in some apps, large query arg objects could take a while to stringify and this was being done repeatedly. We've added a WeakMap-based cache for query args to avoid re-serializing existing arg values.

What's Changed

• Revert "clear data on skip" back to its original behavior by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/3188
• Use a WeakMap cache for query arg serialization for perf by @​markerikson in https://github.com/reduxjs/redux-toolkit/pull/3193

Full Changelog: reduxjs/redux-toolkit@v1.9.2...v1.9.3

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

v5.53.0

Compare Source

Features

• eslint-plugin: [consistent-generic-constructors] handle default parameters (#​6484) (e8cebce)
• eslint-plugin: [no-mixed-enums] add rule (#​6102) (16144d1)

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

v5.53.0

Compare Source

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

stylelint/stylelint

v15.2.0

Compare Source

• Added: messageArgs to 76 rules (#​6589) (@​kizu).
• Fixed: TypeScript error to export Plugin and RuleContext (#​6664) (@​henryruhs).
• Fixed: overrides.extends order when including same rules (#​6660) (@​kuoruan).
• Fixed: annotation-no-unknown false positives for CSS-in-JS template literals (#​6666) (@​hudochenkov).
• Fixed: declaration-property-value-no-unknown false positives for at-rule descriptors (#​6669) (@​FloEdelmann).
• Fixed: declaration-property-value-no-unknown parse error for alpha(opacity=n) to report as violation (#​6650) (@​romainmenke).
• Fixed: function-name-case false positives for CSS-in-JS template literals (#​6666) (@​hudochenkov).
• Fixed: function-no-unknown false positives for CSS-in-JS template literals (#​6666) (@​hudochenkov).
• Fixed: unit-no-unknown false positives for CSS-in-JS template literals (#​6666) (@​hudochenkov).
• Fixed: value-keyword-case false positives for CSS-in-JS template literals (#​6666) (@​hudochenkov).

---

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, check this box

---

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

[pull-request-quantifier-deprecated]

This PR has 26 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       : +13 -13
Percentile : 10.4%

Total files changed: 8

Change summary by file extension:
.json : +13 -13
.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.

[codecov]

Codecov Report

Merging #911 (fc36256) into main (0e97957) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #911   +/-   ##
=========================================
  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.