chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vueuse/core	~9.5.0 -> ~9.6.0
cypress	~11.1.0 -> ~11.2.0
esbuild	~0.15.15 -> ~0.15.16
eslint-plugin-jsdoc	~39.6.2 -> ~39.6.4
lint-staged	~13.0.3 -> ~13.0.4
prettier-plugin-organize-imports	~3.2.0 -> ~3.2.1

---

Release Notes

vueuse/vueuse

v9.6.0

Compare Source

   🐞 Bug Fixes

• onClickOutside: Call handler if click event is fired by a keypress  -  by @​sibbng in https://github.com/vueuse/vueuse/issues/2426 (ff96d)
• ssr-plugin: Use useHead instead of useMeta  -  by @​daniil4udo in https://github.com/vueuse/vueuse/issues/2449 (01c28)
• useFirestore: Fix falsy type error  -  by @​kiyopikko in https://github.com/vueuse/vueuse/issues/2431 (6886e)
• useIDBKeyval: Incorrect value init set  -  by @​sun0day in https://github.com/vueuse/vueuse/issues/2416 (1d841)
• useStyleTag: Allow use of existing node  -  by @​jameswragg in https://github.com/vueuse/vueuse/issues/2442 (94413)
• useTransition: Call pause() to stop useRafFn when disabling  -  by @​huodoushigemi, 李众豪 and @​antfu in https://github.com/vueuse/vueuse/issues/2360 (0a49e)

    View changes on GitHub

cypress-io/cypress

v11.2.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​11-2-0

evanw/esbuild

v0.15.16

Compare Source

• Add a package alias feature (#​2191)

  With this release, you can now easily substitute one package for another at build time with the new alias feature. For example, --alias:oldpkg=newpkg replaces all imports of oldpkg with newpkg. One use case for this is easily replacing a node-only package with a browser-friendly package in 3rd-party code that you don't control. These new substitutions happen first before all of esbuild's existing path resolution logic.

  Note that when an import path is substituted using an alias, the resulting import path is resolved in the working directory instead of in the directory containing the source file with the import path. If needed, the working directory can be set with the cd command when using the CLI or with the absWorkingDir setting when using the JS or Go APIs.

• Fix crash when pretty-printing minified JSX with object spread of object literal with computed property (#​2697)

  JSX elements are translated to JavaScript function calls and JSX element attributes are translated to properties on a JavaScript object literal. These properties are always either strings (e.g. in <x y />, y is a string) or an object spread (e.g. in <x {...y} />, y is an object spread) because JSX doesn't provide syntax for directly passing a computed property as a JSX attribute. However, esbuild's minifier has a rule that tries to inline object spread with an inline object literal in JavaScript. For example, x = { ...{ y } } is minified to x={y} when minification is enabled. This means that there is a way to generate a non-string non-spread JSX attribute in esbuild's internal representation. One example is with <x {...{ [y]: z }} />. When minification is enabled, esbuild's internal representation of this is something like <x [y]={z} /> due to object spread inlining, which is not valid JSX syntax. If this internal representation is then pretty-printed as JSX using --minify --jsx=preserve, esbuild previously crashed when trying to print this invalid syntax. With this release, esbuild will now print <x {...{[y]:z}}/> in this scenario instead of crashing.

gajus/eslint-plugin-jsdoc

v39.6.4

Compare Source

Bug Fixes

• require-return-checks: check return statements prior to last line; fixes #​935 (65e927b)

v39.6.3

Compare Source

Bug Fixes

• update jsdoccomment; fixes #​934 (124d327)

okonet/lint-staged

v13.0.4

Compare Source

Bug Fixes

• deps: update all dependencies (336f3b5)
• deps: update all dependencies (ec995e5)

simonhaenisch/prettier-plugin-organize-imports

v3.2.1

Compare Source

This version fixes the implementation of the language service host's getCurrentDirectory method to return the directory containing the tsconfig, rather than using ts.sys.getCurrentDirectory (which returns process.cwd()). This should prevent issues with resolving compiler plugins with Volar (which is used for Vue support).

Hopefully it doesn't break anything else 🤞 I don't think the tsconfig location is always the project root because of nested/extended tsconfigs, but it should be good enough for module resolution. If someone knows a better way of finding a project's root via the TypeScript API please let me know 🙏

---

Configuration

📅 Schedule: Branch creation - "before 3am 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 #1616 (f26897a) into next (91d093b) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #1616   +/-   ##
=======================================
  Coverage   99.64%   99.64%           
=======================================
  Files        2221     2221           
  Lines      239065   239065           
  Branches     1045     1045           
=======================================
  Hits       238209   238209           
  Misses        835      835           
  Partials       21       21