chore(deps-dev): bump vitest from 1.2.0 to 1.2.1

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps vitest from 1.2.0 to 1.2.1.

Release notes

Sourced from vitest's releases.

v1.2.1

   🐞 Bug Fixes

• browser:
  • Apply inlined workspace config to browser mode vite server  -  by @​hi-ogawa in vitest-dev/vitest#4947 (db01f)
  • Fix browser testing url for https  -  by @​hi-ogawa in vitest-dev/vitest#4855 (6c1cc)
  • Don't fail when calling vi.useFakeTimers  -  by @​sheremet-va in vitest-dev/vitest#4992 (6c5fe)
• coverage:
  • thresholds.autoUpdate to work with arrow function configuration files  -  by @​AriPerkkio in vitest-dev/vitest#4959 (4b411)
• expect:
  • Implement chai inspect for AsymmetricMatcher  -  by @​hi-ogawa and @​sheremet-va in vitest-dev/vitest#4942 (06bae)
• vite-node:
  • Externalize network imports  -  by @​hi-ogawa in vitest-dev/vitest#4987 (21f57)
• vitest:
  • Handle single await vi.hoisted  -  by @​hi-ogawa in vitest-dev/vitest#4962 (dcf2e)
  • Simplify hoist transform check regex to avoid expensive regex match  -  by @​hi-ogawa in vitest-dev/vitest#4974 (df0db)
  • Correctly find module if it has a version query  -  by @​sheremet-va in vitest-dev/vitest#4976 (952c3)
  • Check color support for intercepted console logging  -  by @​hi-ogawa in vitest-dev/vitest#4966 (39a71)
  • Use development/production conditions when resolving external modules  -  by @​sheremet-va in vitest-dev/vitest#4980 (8877e)
  • Throw a syntax error if vi.hoisted is directly exported  -  by @​sheremet-va in vitest-dev/vitest#4969 (f8bff)

    View changes on GitHub

Commits

• 6421c27 chore: release v1.2.1
• f8bff9e fix(vitest): throw a syntax error if vi.hoisted is directly exported (#4969)
• 6c5fe49 fix(browser): don't fail when calling vi.useFakeTimers (#4992)
• 8877e22 fix(vitest): use development/production conditions when resolving external mo...
• 39a7169 fix(vitest): check color support for intercepted console logging (#4966)
• 6c1cc78 fix(browser): fix browser testing url for https (#4855)
• 952c31d fix(vitest): correctly find module if it has a version query (#4976)
• df0db6a fix(vitest): simplify hoist transform check regex to avoid expensive regex ma...
• db01f6c fix(browser): apply inlined workspace config to browser mode vite server (#4947)
• 6bfdb5f refactor: improve highlighted function (#4967)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 2

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

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.