chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	~20.10.3 -> ~20.10.4
cypress (source)	~13.6.0 -> ~13.6.1
esbuild	~0.19.8 -> ~0.19.9
eslint-plugin-vitest	~0.3.10 -> ~0.3.15
tsx	~3.13.0 -> ~3.14.0
vue (source)	~3.3.10 -> ~3.3.11

---

Release Notes

cypress-io/cypress (cypress)

v13.6.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-6-1

evanw/esbuild (esbuild)

v0.19.9

Compare Source

• Add support for transforming new CSS gradient syntax for older browsers

  The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in Mozilla's blog post about new CSS gradient features.

  With this release, esbuild will now automatically transform this syntax for older browsers in the target list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax:

  /* Original code */
  .rainbow-gradient {
    width: 100px;
    height: 100px;
    background: linear-gradient(in hsl longer hue, #​7ff, #​77f);
  }
  
  /* New output (with --target=chrome99) */
  .rainbow-gradient {
    width: 100px;
    height: 100px;
    background:
      linear-gradient(
        #​77ffff,
        #​77ffaa 12.5%,
        #​77ff80 18.75%,
        #​84ff77 21.88%,
        #​99ff77 25%,
        #eeff77 37.5%,
        #fffb77 40.62%,
        #ffe577 43.75%,
        #ffbb77 50%,
        #ff9077 56.25%,
        #ff7b77 59.38%,
        #ff7788 62.5%,
        #ff77dd 75%,
        #ff77f2 78.12%,
        #f777ff 81.25%,
        #cc77ff 87.5%,
        #​7777ff);
  }

  You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate:

  /* Original code */
  .stripes {
    width: 100px;
    height: 100px;
    background: linear-gradient(#e65 33%, #ff2 33% 67%, #​99e 67%);
  }
  .glow {
    width: 100px;
    height: 100px;
    background: radial-gradient(white 10%, 20%, black);
  }
  
  /* New output (with --target=chrome33) */
  .stripes {
    width: 100px;
    height: 100px;
    background:
      linear-gradient(
        #e65 33%,
        #ff2 33%,
        #ff2 67%,
        #​99e 67%);
  }
  .glow {
    width: 100px;
    height: 100px;
    background:
      radial-gradient(
        #ffffff 10%,
        #aaaaaa 12.81%,
        #​959595 15.62%,
        #​7b7b7b 21.25%,
        #​5a5a5a 32.5%,
        #​444444 43.75%,
        #​323232 55%,
        #​161616 77.5%,
        #​000000);
  }

  You can see visual examples of these new syntax features by looking at esbuild's gradient transformation tests.

  If necessary, esbuild will construct a new gradient that approximates the original gradient by recursively splitting the interval in between color stops until the approximation error is within a small threshold. That is why the above output CSS contains many more color stops than the input CSS.

  Note that esbuild deliberately replaces the original gradient with the approximation instead of inserting the approximation before the original gradient as a fallback. The latest version of Firefox has multiple gradient rendering bugs (including incorrect interpolation of partially-transparent colors and interpolating non-sRGB colors using the incorrect color space). If esbuild didn't replace the original gradient, then Firefox would use the original gradient instead of the fallback the appearance would be incorrect in Firefox. In other words, the latest version of Firefox supports modern gradient syntax but interprets it incorrectly.

• Add support for color(), lab(), lch(), oklab(), oklch(), and hwb() in CSS

  CSS has recently added lots of new ways of specifying colors. You can read more about this in Chrome's blog post about CSS color spaces.

  This release adds support for minifying colors that use the color(), lab(), lch(), oklab(), oklch(), or hwb() syntax and/or transforming these colors for browsers that don't support it yet:

  /* Original code */
  div {
    color: hwb(90deg 20% 40%);
    background: color(display-p3 1 0 0);
  }
  
  /* New output (with --target=chrome99) */
  div {
    color: #​669933;
    background: #ff0f0e;
    background: color(display-p3 1 0 0);
  }

  As you can see, colors outside of the sRGB color space such as color(display-p3 1 0 0) are mapped back into the sRGB gamut and inserted as a fallback for browsers that don't support the new color syntax.

• Allow empty type parameter lists in certain cases (#​3512)

  TypeScript allows interface declarations and type aliases to have empty type parameter lists. Previously esbuild didn't handle this edge case but with this release, esbuild will now parse this syntax:

  interface Foo<> {}
  type Bar<> = {}

  This fix was contributed by @​magic-akari.

veritem/eslint-plugin-vitest (eslint-plugin-vitest)

v0.3.15

Compare Source

v0.3.14

Compare Source

Features

• new rule no-import-node-test (#​317) (ccd7e88)

v0.3.13

Compare Source

Features

• vitest/require-local-test-context-for-concurrent-snapshots: add rule (#​315) (ffce7e1)

What's Changed

• feat(vitest/require-local-test-context-for-concurrent-snapshots): add rule by @​Haberkamp in https://github.com/veritem/eslint-plugin-vitest/pull/315
• chore(outdated docs): improve documentation by @​veritem in https://github.com/veritem/eslint-plugin-vitest/pull/316

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.12...v0.3.13

v0.3.12

Compare Source

Bug Fixes

• packages: update packages (#​298) (4ab7238)
• vitest/no-done-callback: do not report accesssing of text context when test runs concurrently (#​313) (b7eb2ce)

Features

• engines: update minimum node version (9ff1c16)

privatenumber/tsx (tsx)

v3.14.0

Compare Source

Bug Fixes

• cache: scope cache directory to user (#​332) (7e916f5)

Features

• support Node v20.6.0 module.register() & --import flag (#​337) (23e4694)

---

This release is also available on:

• npm package (@​latest dist-tag)

vuejs/core (vue)

v3.3.11

Compare Source

Bug Fixes

• custom-element: correctly handle number type props in prod (#​8989) (d74d364)
• reactivity: fix mutation on user proxy of reactive Array (6ecbd5c), closes #​9742 #​9751 #​9750
• runtime-dom: fix width and height prop check condition (5b00286), closes #​9762
• shared: handle Map with symbol keys in toDisplayString (#​9731) (364821d), closes #​9727
• shared: handle more Symbol cases in toDisplayString (983d45d)
• Suspense: properly get anchor when mount fallback vnode (#​9770) (b700328), closes #​9769
• types: ref() return type should not be any when initial value is any (#​9768) (cdac121)
• watch: should not fire pre watcher on child component unmount (#​7181) (6784f0b), closes #​7030

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

[codecov]

Codecov Report

Merging #2571 (e25e915) into next (1a67381) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #2571   +/-   ##
=======================================
  Coverage   99.57%   99.57%           
=======================================
  Files        2805     2805           
  Lines      250179   250179           
  Branches     1107     1106    -1     
=======================================
+ Hits       249120   249122    +2     
+ Misses       1031     1029    -2     
  Partials       28       28           

see 2 files with indirect coverage changes

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.