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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	^7.19.1 -> ^7.19.3
@types/inquirer (source)	^8.2.3 -> ^8.2.4
@types/jest (source)	^29.0.3 -> ^29.1.1
@types/node (source)	^16.11.60 -> ^16.11.62
@typescript-eslint/eslint-plugin	^5.38.0 -> ^5.38.1
@typescript-eslint/parser	^5.38.0 -> ^5.38.1
babel-jest	^29.0.3 -> ^29.1.2
commander	^9.4.0 -> ^9.4.1
css-minimizer-webpack-plugin	^4.1.0 -> ^4.2.0
dotenv	^16.0.2 -> ^16.0.3
jest (source)	^29.0.3 -> ^29.1.2
jest-environment-jsdom	^29.0.3 -> ^29.1.2
jest-resolve	^29.0.3 -> ^29.1.2
lerna (source)	^5.5.2 -> ^5.5.4
postcss (source)	^8.4.16 -> ^8.4.17
stylelint (source)	^14.12.1 -> ^14.13.0
ts-jest (source)	^29.0.2 -> ^29.0.3
typescript (source)	^4.8.3 -> ^4.8.4
verdaccio (source)	^5.15.3 -> ^5.15.4

---

Release Notes

babel/babel

v7.19.3

Compare Source

🐛 Bug Fix

• babel-plugin-proposal-decorators
  • #​8566 Correctly update bindings of decorated class declarations (@​nicolo-ribaudo)
• babel-parser
  • #​14974 fix: Normal parsing of JSXText following JSXSpreadChild (@​liuxingbaoyu)
  • #​14941 fix: Support local exports in TS declare modules (@​liuxingbaoyu)
  • #​14940 fix: allow ts redeclaration with import = and var (@​liuxingbaoyu)
• babel-generator
  • #​14962 Fix printing of Flow internal slot functions (@​liuxingbaoyu)
• babel-cli
  • #​14950 Emit @babel/cli source maps based on configuration files (@​liuxingbaoyu)
• babel-plugin-transform-typescript
  • #​14946 fix: ts exported vars are shadowed by declare (@​liuxingbaoyu)

💅 Polish

• babel-core
  • #​14954 Optional filename when preset uses fn test/include/exclude (@​nicolo-ribaudo)

🏠 Internal

• babel-helper-compilation-targets, babel-helper-transform-fixture-test-runner, babel-parser, babel-preset-env, babel-traverse
  • #​14961 chore: use c8 for coverage testing (@​liuxingbaoyu)

🔬 Output optimization

• babel-plugin-transform-typescript
  • #​14952 [ts] remove nested declare namespace (@​liuxingbaoyu)

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

v5.38.1

Compare Source

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

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

v5.38.1

Compare Source

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

facebook/jest

v29.1.2

Compare Source

Fixes

• [expect, @​jest/expect] Revert buggy inference of argument types for *CalledWith and *ReturnedWith matchers introduced in 29.1.0 (#​13339)
• [jest-worker] Add missing dependency on jest-util (#​13341)

v29.1.0

Compare Source

Features

• [expect, @​jest/expect] Support type inference for function parameters in CalledWith assertions (#​13268)
• [expect, @​jest/expect] Infer type of *ReturnedWith matchers argument (#​13278)
• [@jest/environment, jest-runtime] Allow jest.requireActual and jest.requireMock to take a type argument (#​13253)
• [@jest/environment] Allow jest.mock and jest.doMock to take a type argument (#​13254)
• [@jest/fake-timers] Add jest.now() to return the current fake clock time (#​13244, #​13246)
• [@jest/mock] Add withImplementation method for temporarily overriding a mock (#​13281)
• [expect] Export toThrow* matchers (#​13328)

Fixes

• [jest-circus, jest-jasmine2] Fix error messages for Node's assert.throes (#​13322)
• [jest-haste-map] Remove __proto__ usage (#​13256)
• [jest-mock] Improve spyOn typings to handle optional properties (#​13247)
• [jest-mock] Fix mocking of getters and setters on classes (#​13145)
• [jest-snapshot] Throw useful error when an array is passed as property matchers (#​13263)
• [jest-snapshot] Prioritize parser used in the project (#​13323)
• [jest-transform] Attempt to work around issues with atomic writes on Windows (#​11423)

tj/commander.js

v9.4.1

Compare Source

Fixed

• .setOptionValue() now also clears option source ([#​1795])
• TypeScript: add implied to OptionValueSource for option values set by using .implies() ([#​1794])
• TypeScript : add undefined to return type of .getOptionValueSource() ([#​1794])

Changed

• additions to README

webpack-contrib/css-minimizer-webpack-plugin

v4.2.0

Compare Source

Features

• added swc minimizer (#​197) (5461421)

motdotla/dotenv

v16.0.3

Compare Source

Changed

• Added library version to debug logs (#​682)

lerna/lerna

v5.5.4

Compare Source

Note: Version bump only for package lerna

postcss/postcss

v8.4.17

Compare Source

• Fixed Node.before() unexpected behavior (by Romain Menke).
• Added TOC to docs (by Mikhail Dedov).

stylelint/stylelint

v14.13.0

Compare Source

• Added: cacheStrategy option (#​6357) (@​kaorun343).
• Fixed: cache refresh when config is changed (#​6356) (@​kimulaco).
• Fixed: selector-pseudo-element-no-unknown false positives for ::highlight pseudo-element (#​6367) (@​jathak).

kulshekhar/ts-jest

v29.0.3

Compare Source

Bug Fixes

• merge config from globals with transformer config correctly (#​3842) (9c9fd60), closes #​3841
• presets: allow merging transform config when using presets (#​3833) (afc6a94)

Features

• add useESM option to pathsToModuleNameMapper options (#​3792) (eabe906)

Microsoft/TypeScript

v4.8.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 4.8.0 (Beta).
• fixed issues query for Typescript 4.8.1 (RC).
• fixed issues query for Typescript 4.8.2 (Stable).
• fixed issues query for Typescript 4.8.3 (Stable).
• fixed issues query for Typescript 4.8.4 (Stable).

Downloads are available on:

• npm
• Visual Studio 2022/2019 (Select new version in project options)
• NuGet package

verdaccio/verdaccio

v5.15.4

Compare Source

5.15.4 (2022-09-29)

Bug Fixes

• docker base image upgraded 14.20.1 (#​3405) (1d6b763)
• deps: update dependency @​verdaccio/ui-theme to v6.0.0-6-next.48 (#​3404) (be5c9f9) by @​mbtools

---

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.

[pull-request-quantifier-deprecated]

This PR has 62 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       : +31 -31
Percentile : 24.8%

Total files changed: 9

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

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 #823 (56a9f8a) into main (6f44e49) will not change coverage.
The diff coverage is n/a.

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