chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cypress	~10.4.0 -> ~10.6.0
esbuild	~0.15.2 -> ~0.15.5
eslint (source)	~8.21.0 -> ~8.22.0
vite	~3.0.7 -> ~3.0.8

---

Release Notes

cypress-io/cypress

v10.6.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-6-0

v10.5.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#​10-5-0

evanw/esbuild

v0.15.5

Compare Source

• Fix issues with Yarn PnP and Yarn's workspaces feature (#​2476)

  This release makes sure esbuild works with a Yarn feature called workspaces. Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix exports map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working.

v0.15.4

Compare Source

• Consider TypeScript import assignments to be side-effect free (#​2468)

  TypeScript has a legacy import syntax for working with TypeScript namespaces that looks like this:

  import { someNamespace } from './some-file'
  import bar = someNamespace.foo;
  
  // some-file.ts
  export namespace someNamespace {
    export let foo = 123
  }

  Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if bar is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps bar in the output, which is done because someNamespace.foo is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case).

  With this release, esbuild will now consider someNamespace.foo to have no side effects. This means bar will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of bar, so it would be incorrect to remove it. If you want bar to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output).

• Change the order of the banner and the "use strict" directive (#​2467)

  Previously the top of the file contained the following things in order:

  1. The hashbang comment (see below) from the source code, if present
  2. The "use strict" directive from the source code, if present
  3. The content of esbuild's banner API option, if specified

  This was problematic for people that used the banner API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to:

  1. The hashbang comment (see below) from the source code, if present
  2. The content of esbuild's banner API option, if specified
  3. The "use strict" directive from the source code, if present

  I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the banner API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the "use strict" directive.

  For context: JavaScript files recently allowed using a hashbang comment, which starts with #! and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the node command. This comment typically has the value #!/usr/bin/env node. Hashbang comments will be a part of ES2023 when it's released next year.

• Fix exports maps with Yarn PnP path resolution (#​2473)

  The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that exports in package.json is not respected because node's module resolution algorithm doesn't interpret exports for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP.

v0.15.3

Compare Source

• Change the Yarn PnP manifest to a singleton (#​2463)

  Previously esbuild searched for the Yarn PnP manifest in the parent directories of each file. But with Yarn's enableGlobalCache setting it's possible to configure Yarn PnP's implementation to reach outside of the directory subtree containing the Yarn PnP manifest. This was causing esbuild to fail to bundle projects with the enableGlobalCache setting enabled.

  To handle this case, esbuild will now only search for the Yarn PnP manifest in the current working directory of the esbuild process. If you're using esbuild's CLI, this means you will now have to cd into the appropriate directory first. If you're using esbuild's API, you can override esbuild's value for the current working directory with the absWorkingDir API option.

• Fix Yarn PnP resolution failures due to backslashes in paths on Windows (#​2462)

  Previously dependencies of a Yarn PnP virtual dependency failed to resolve on Windows. This was because Windows uses \ instead of / as a path separator, and the path manipulation algorithms used for Yarn PnP expected /. This release converts \ into / in Windows paths, which fixes this issue.

• Fix sideEffects patterns containing slashes on Windows (#​2465)

  The sideEffects field in package.json lets you specify an array of patterns to mark which files have side effects (which causes all other files to be considered to not have side effects by exclusion). That looks like this:

  "sideEffects": [
    "**/index.js",
    "**/index.prod.js"
  ]

  However, the presence of the / character in the pattern meant that the pattern failed to match Windows-style paths, which broke sideEffects on Windows in this case. This release fixes this problem by adding additional code to handle Windows-style paths.

eslint/eslint

v8.22.0

Compare Source

Features

• 2b97607 feat: Implement caching for FlatESLint (#​16190) (Nicholas C. Zakas)
• fd5d3d3 feat: add methodsIgnorePattern option to object-shorthand rule (#​16185) (Milos Djermanovic)

Documentation

• 9f5a752 docs: optimize image assets (#​16170) (Sam Chen)
• 61b2948 docs: add svgo command to pre commit hook (#​16178) (Amaresh S M)
• 784096d docs: improve search result UI (#​16187) (Sam Chen)
• d0f4cb4 docs: use shorthand property name in example (#​16180) (Kevin Elliott)

Chores

• 10a6e0e chore: remove deploy workflow for playground (#​16186) (Milos Djermanovic)

vitejs/vite

v3.0.8

Compare Source

• fix: allow ping to http from https website (#​9561) (f4b4405), closes #​9561
• fix: use browser field if likely esm (fixes #​9652) (#​9653) (85e387a), closes #​9652 #​9653
• fix(ssr-manifest): filter path undefined when dynamic import (#​9655) (1478a2f), closes #​9655
• docs: update WSL2 watch limitation explanation (#​8939) (afbb87d), closes #​8939

---

Configuration

📅 Schedule: Branch creation - "before 2am" (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, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

Merging #1274 (49ad43b) into main (34cd449) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1274   +/-   ##
=======================================
  Coverage   99.62%   99.62%           
=======================================
  Files        2154     2154           
  Lines      239914   239914           
  Branches     1003     1003           
=======================================
  Hits       239015   239015           
  Misses        878      878           
  Partials       21       21