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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@antfu/eslint-config	^2.11.6 -> ^2.12.1
@babel/core (source)	^7.24.3 -> ^7.24.4
@babel/preset-env (source)	^7.24.3 -> ^7.24.4
@docusaurus/core (source)	3.2.0 -> 3.2.1
@docusaurus/module-type-aliases (source)	3.2.0 -> 3.2.1
@docusaurus/preset-classic (source)	3.2.0 -> 3.2.1
@docusaurus/theme-classic (source)	^3.2.0 -> ^3.2.1
@docusaurus/tsconfig (source)	3.2.0 -> 3.2.1
@docusaurus/types (source)	3.2.0 -> 3.2.1
@reduxjs/toolkit (source)	^2.2.2 -> ^2.2.3
@types/node (source)	^20.12.2 -> ^20.12.4
@types/react (source)	^18.2.73 -> ^18.2.74
@types/react-dom (source)	^18.2.23 -> ^18.2.24
@typescript-eslint/utils (source)	^7.4.0 -> ^7.5.0
pnpm (source)	8.15.5 -> 8.15.6
postcss-preset-env (source)	^9.5.3 -> ^9.5.4
stylelint-config-standard-scss	^13.0.0 -> ^13.1.0
type-fest	^4.14.0 -> ^4.15.0
typescript (source)	^5.4.3 -> ^5.4.4
typescript-eslint (source)	^7.4.0 -> ^7.5.0
undici (source)	^6.10.2 -> ^6.11.1

---

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v2.12.1

Compare Source

   🐞 Bug Fixes

• Move no-new-symbol to no-new-native-nonconstructor  -  by @​antfu (a278b)

    View changes on GitHub

v2.12.0

Compare Source

   🚀 Features

• Update names for all config items  -  by @​antfu (9de13)

    View changes on GitHub

babel/babel (@​babel/core)

v7.24.4

Compare Source

👓 Spec Compliance

• babel-parser
  • #​16403 Forbid initializerless using (@​JLHwung)
• babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs3
  • #​16388 Ensure decorators are callable (@​JLHwung)

🐛 Bug Fix

• babel-generator
  • #​16402 fix: Correctly prints { [key in Bar]? } (@​liuxingbaoyu)
  • #​16394 fix: Correctly generate TSMappedType (@​liuxingbaoyu)
• babel-compat-data, babel-plugin-bugfix-firefox-class-in-computed-class-key, babel-preset-env
  • #​16390 Create bugfix plugin for classes in computed keys in Firefox (@​nicolo-ribaudo)
• babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators
  • #​16387 fix: support mutated outer decorated class binding (@​JLHwung)
  • #​16385 fix: Decorators when super() exists and protoInit is not needed (@​liuxingbaoyu)
• babel-plugin-transform-block-scoping
  • #​16384 fix: Transform scoping for for X in loop (@​liuxingbaoyu)
  • #​16368 fix: Capture let when the for body is not a block (@​liuxingbaoyu)
• babel-core, babel-plugin-transform-block-scoped-functions, babel-plugin-transform-block-scoping
  • #​16363 Fix incorrect function hoisting in some case statements (@​luiscubal)

facebook/docusaurus (@​docusaurus/core)

v3.2.1

Compare Source

facebook/docusaurus (@​docusaurus/module-type-aliases)

v3.2.1

Compare Source

facebook/docusaurus (@​docusaurus/preset-classic)

v3.2.1

Compare Source

facebook/docusaurus (@​docusaurus/theme-classic)

v3.2.1

Compare Source

🐛 Bug Fix

• docusaurus
  • #​10012 fix(core): fix configurePostCss v3.2 regression (@​slorber)

📝 Documentation

• #​9980 docs: remove old github action description (@​OzakIOne)
• #​10014 docs(website): fix SEO docs headTags example (@​OzakIOne)
• #​10004 docs(website): Announce v3.2 on website/homepage (@​slorber)

🤖 Dependencies

• #​10006 chore(deps): bump actions/dependency-review-action from 4.2.4 to 4.2.5 (@​dependabot[bot])

Committers: 2

• Sébastien Lorber (@​slorber)
• ozaki (@​OzakIOne)

facebook/docusaurus (@​docusaurus/tsconfig)

v3.2.1

Compare Source

facebook/docusaurus (@​docusaurus/types)

v3.2.1

Compare Source

reduxjs/redux-toolkit (@​reduxjs/toolkit)

v2.2.3

Compare Source

This minor release fixes the types for functions that accept a React Context instance to match the changes in React Redux v9.

What's Changed

• Update React Redux dependency to v9, and update docs to use .withTypes by @​aryaemami59 in https://github.com/reduxjs/redux-toolkit/pull/4308

Full Changelog: reduxjs/redux-toolkit@v2.2.2...v2.2.3

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

v7.5.0

Compare Source

This was a version bump only for utils to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

pnpm/pnpm (pnpm)

v8.15.6

Compare Source

Patch Changes

• The exit code of the child process should be preserved on pnpm run #​7817.
• When sorting packages in a workspace, take into account workspace dependencies specified as peerDependencies #​7813.
• Add --ignore-scripts argument to prune command #​7836.

Platinum Sponsors

Gold Sponsors

Silver Sponsors

csstools/postcss-plugins (postcss-preset-env)

v9.5.4

Compare Source

April 2, 2024

• Updated @csstools/postcss-light-dark-function to 1.0.3 (patch)

stylelint-scss/stylelint-config-standard-scss (stylelint-config-standard-scss)

v13.1.0

Compare Source

• Changed: scss/dollar-variable-colon-space-after from always to always-single-line to be compatible with the default formatting of Prettier.

sindresorhus/type-fest (type-fest)

v4.15.0

Compare Source

Microsoft/TypeScript (typescript)

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).

Downloads are available on:

• NuGet package

typescript-eslint/typescript-eslint (typescript-eslint)

v7.5.0

Compare Source

🩹 Fixes

• typescript-eslint: improve support for legacy configs

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

nodejs/undici (undici)

v6.11.1

Compare Source

v6.11.0

Compare Source

---

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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@antfu/eslint-config@2.12.1	environment Transitive: filesystem	+12	6.43 MB	antfu
npm/@babel/core@7.24.4	environment, filesystem, unsafe	+33	8.02 MB	nicolo-ribaudo
npm/@babel/preset-env@7.24.4	environment, filesystem Transitive: unsafe	+109	8.05 MB	nicolo-ribaudo
npm/@docusaurus/core@3.2.1	Transitive: environment, eval, filesystem, network, shell, unsafe	+116	15.2 MB	slorber
npm/@docusaurus/module-type-aliases@3.2.1	None	+5	116 kB	slorber
npm/@docusaurus/preset-classic@3.2.1	environment Transitive: filesystem, network	+120	13.6 MB	slorber
npm/@docusaurus/theme-classic@3.2.1	unsafe Transitive: environment, filesystem, network	+91	10.8 MB	slorber
npm/@docusaurus/tsconfig@3.2.1	None	0	2.13 kB	slorber
npm/@docusaurus/types@3.2.1	Transitive: filesystem, shell	+11	432 kB	slorber
npm/@reduxjs/toolkit@2.2.3	environment	0	5.44 MB	phryneas
npm/@types/node@20.12.4	None	0	2.03 MB	types
npm/@types/react-dom@18.2.24	None	0	34.9 kB	types
npm/@types/react@18.2.74	None	+2	1.68 MB	types
npm/@typescript-eslint/utils@7.5.0	Transitive: environment	+7	2.13 MB	jameshenry

🚮 Removed packages: npm/@antfu/eslint-config@2.11.6, npm/@babel/core@7.24.3, npm/@babel/preset-env@7.24.3, npm/@docusaurus/core@3.2.0, npm/@docusaurus/module-type-aliases@3.2.0, npm/@docusaurus/preset-classic@3.2.0, npm/@docusaurus/theme-classic@3.2.0, npm/@docusaurus/tsconfig@3.2.0, npm/@docusaurus/types@3.2.0, npm/@reduxjs/toolkit@2.2.2, npm/@types/node@20.12.2, npm/@types/react-dom@18.2.23, npm/@types/react@18.2.73, npm/@typescript-eslint/utils@7.4.0

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.29%. Comparing base (2ba8cd2) to head (6b900ed).
Report is 1 commits behind head on main.

❗ Current head 6b900ed differs from pull request most recent head b8aafe7. Consider uploading reports for the commit b8aafe7 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1165   +/-   ##
=======================================
  Coverage   96.29%   96.29%           
=======================================
  Files          21       21           
  Lines         189      189           
  Branches       17       18    +1     
=======================================
  Hits          182      182           
+ Misses          7        5    -2     
- Partials        0        2    +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Small
Size       : +34 -34
Percentile : 27.2%

Total files changed: 9

Change summary by file extension:
.json : +34 -34

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.

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Small
Size       : +32 -32
Percentile : 25.6%

Total files changed: 9

Change summary by file extension:
.json : +32 -32

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.