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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@testing-library/jest-dom	^6.1.2 -> ^6.1.3
core-js	^3.32.1 -> ^3.32.2
vitest	^0.34.3 -> ^0.34.4
vue-tsc	^1.8.8 -> ^1.8.10

---

Release Notes

testing-library/jest-dom (@​testing-library/jest-dom)

v6.1.3

Compare Source

Bug Fixes

• proper @​jest/globals import (#​530) (5b492ac)

zloirock/core-js (core-js)

v3.32.2

Compare Source

• Fixed structuredClone feature detection [email protected] bug, #​1288
• Added a workaround of old WebKit + eval bug, #​1287
• Compat data improvements:
  • Added Samsung Internet 23 compat data mapping
  • Added Quest Browser 29 compat data mapping

vitest-dev/vitest (vitest)

v0.34.4

Compare Source

   🐞 Bug Fixes

• Resolving dep optimizer issues with workspace  -  by @​thebanjomatic in https://github.com/vitest-dev/vitest/issues/4036 (0c13c)
• Don't process config file twice  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4077 (a84a8)
• coverage:
  • Log info only when terminal reporter is used  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/4027 (9f043)
• happy-dom:
  • Use the nodejs console in happy-dom v11  -  by @​capricorn86 in https://github.com/vitest-dev/vitest/issues/4090 (59434)
• runner:
  • Incorrect test name pattern matching  -  by @​Dunqing in https://github.com/vitest-dev/vitest/issues/4071 (b5bf3)
• vite-node:
  • Check more precisely for root/base paths  -  by @​danielroe in https://github.com/vitest-dev/vitest/issues/4049 (80741)
• vitest:
  • "vi" doesn't rely on context  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4031 (0d0f3)
  • Only override ssr.optimizer instead of the whole ssr object  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4080 (410bc)
  • Don't start the server when optimizer is enabled  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4095 (00e81)
  • Set SSR env only when transformMode is ssr  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4083 (f8ea7)
  • Show error when calling API on files that user has no access to  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4085 (8b39c)
• web-worker:
  • Don't rely on browser API when it's not provided  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/4014 (e78a4)

    View changes on GitHub

vuejs/language-tools (vue-tsc)

v1.8.10

Compare Source

• feat: added Portuguese integration documentation (#​3535)
• feat: exposed configFileName for createParsedCommandLineByJson() function (#​3456) - thanks @​qmhc
• feat: support nested plugins (#​3530) - thanks @​so1ve
• feat(vscode): add vue.server.runtime setting and support for Bun runtime
• feat(vscode): add vue.server.path setting for customize server module path
• fix: correctly hyphen-case props (#​3424) - thanks @​so1ve
• fix: generic components should respect strictTemplates (#​3487) - thanks @​so1ve
• fix(vue-component-type-helpers): correctly handle generic components when using ComponentExposed (#​3536) - thanks @​so1ve

Full-time Support by

WebContainer API is here.

Our Platinum Sponsors

	The Intuitive Web Framework
	The Progressive JavaScript Framework

Our Silver Sponsors

Add you via GitHub Sponsors or Open Collective

---

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 8 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       : +4 -4
Percentile : 3.2%

Total files changed: 5

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

Patch and project coverage have no change.

Comparison is base (965f234) 100.00% compared to head (c5b5840) 100.00%.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #522   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            7         7           
=========================================
  Hits             7         7           

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

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: [email protected]