chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cypress	~10.6.0 -> ~10.7.0
esbuild	~0.15.5 -> ~0.15.7
prettier-plugin-organize-imports	~3.1.0 -> ~3.1.1

---

Release Notes

cypress-io/cypress

v10.7.0

Compare Source

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

evanw/esbuild

v0.15.7

Compare Source

• Add --watch=forever to allow esbuild to never terminate (#​1511, #​1885)

  Currently using esbuild's watch mode via --watch from the CLI will stop watching if stdin is closed. The rationale is that stdin is automatically closed by the OS when the parent process exits, so stopping watch mode when stdin is closed ensures that esbuild's watch mode doesn't keep running forever after the parent process has been closed. For example, it would be bad if you wrote a shell script that did esbuild --watch & to run esbuild's watch mode in the background, and every time you run the script it creates a new esbuild process that runs forever.

  However, there are cases when it makes sense for esbuild's watch mode to never exit. One such case is within a short-lived VM where the lifetime of all processes inside the VM is expected to be the lifetime of the VM. Previously you could easily do this by piping the output of a long-lived command into esbuild's stdin such as sleep 999999999 | esbuild --watch &. However, this possibility often doesn't occur to people, and it also doesn't work on Windows. People also sometimes attempt to keep esbuild open by piping an infinite stream of data to esbuild such as with esbuild --watch </dev/zero & which causes esbuild to spin at 100% CPU. So with this release, esbuild now has a --watch=forever flag that will not stop watch mode when stdin is closed.

• Work around PATH without node in install script (#​2519)

  Some people install esbuild's npm package in an environment without the node command in their PATH. This fails on Windows because esbuild's install script runs the esbuild command before exiting as a sanity check, and on Windows the esbuild command has to be a JavaScript file because of some internal details about how npm handles the bin folder (specifically the esbuild command lacks the .exe extension, which is required on Windows). This release attempts to work around this problem by using process.execPath instead of "node" as the command for running node. In theory this means the installer can now still function on Windows if something is wrong with PATH.

v0.15.6

Compare Source

• Lower for await loops (#​1930)

  This release lowers for await loops to the equivalent for loop containing await when esbuild is configured such that for await loops are unsupported. This transform still requires at least generator functions to be supported since esbuild's lowering of await currently relies on generators. This new transformation is mostly modeled after what the TypeScript compiler does. Here's an example:

  async function f() {
    for await (let x of y)
      x()
  }

  The code above will now become the following code with --target=es2017 (omitting the code for the __forAwait helper function):

  async function f() {
    try {
      for (var iter = __forAwait(y), more, temp, error; more = !(temp = await iter.next()).done; more = false) {
        let x = temp.value;
        x();
      }
    } catch (temp) {
      error = [temp];
    } finally {
      try {
        more && (temp = iter.return) && await temp.call(iter);
      } finally {
        if (error)
          throw error[0];
      }
    }
  }

• Automatically fix invalid supported configurations (#​2497)

  The --target= setting lets you tell esbuild to target a specific version of one or more JavaScript runtimes such as chrome80,node14 and esbuild will restrict its output to only those features supported by all targeted JavaScript runtimes. More recently, esbuild introduced the --supported: setting that lets you override which features are supported on a per-feature basis. However, this now lets you configure nonsensical things such as --supported:async-await=false --supported:async-generator=true. Previously doing this could result in esbuild building successfully but producing invalid output.

  Starting with this release, esbuild will now attempt to automatically fix nonsensical feature override configurations by introducing more overrides until the configuration makes sense. So now the configuration from previous example will be changed such that async-await=false implies async-generator=false. The full list of implications that were introduced is below:

  • async-await=false implies:

    • async-generator=false
    • for-await=false
    • top-level-await=false

  • generator=false implies:

    • async-generator=false

  • object-accessors=false implies:

    • class-private-accessor=false
    • class-private-static-accessor=false

  • class-field=false implies:

    • class-private-field=false

  • class-static-field=false implies:

    • class-private-static-field=false

  • class=false implies:

    • class-field=false
    • class-private-accessor=false
    • class-private-brand-check=false
    • class-private-field=false
    • class-private-method=false
    • class-private-static-accessor=false
    • class-private-static-field=false
    • class-private-static-method=false
    • class-static-blocks=false
    • class-static-field=false

• Implement a small minification improvement (#​2496)

  Some people write code that contains a label with an immediate break such as x: break x. Previously this code was not removed during minification but it will now be removed during minification starting with this release.

• Fix installing esbuild via Yarn with enableScripts: false configured (#​2457)

  If esbuild is installed with Yarn with the enableScripts: false setting configured, then Yarn will not "unplug" the esbuild package (i.e. it will keep the entire package inside a .zip file). This messes with esbuild's library code that extracts the platform-specific binary executable because that code copies the binary executable into the esbuild package directory, and Yarn's .zip file system shim doesn't let you write to a directory inside of a .zip file. This release fixes this problem by writing to the node_modules/.cache/esbuild directory instead in this case. So you should now be able to use esbuild with Yarn when enableScripts: false is configured.

  This fix was contributed by @​jonaskuske.

simonhaenisch/prettier-plugin-organize-imports

v3.1.1

Compare Source

• fix: path comparison on Windows
• fix: bump @volar/vue-typescript peer dependency to higher version which fixes removal of imports used in the template only

---

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, click this checkbox.

---

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

[codecov]

Codecov Report

Merging #1332 (751fdec) into main (ebb4e2c) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1332      +/-   ##
==========================================
- Coverage   99.63%   99.62%   -0.01%     
==========================================
  Files        2163     2163              
  Lines      240701   240701              
  Branches     1018     1014       -4     
==========================================
- Hits       239818   239794      -24     
- Misses        862      886      +24     
  Partials       21       21              

Impacted Files	Coverage Δ
src/modules/internet/user-agent.ts	81.74% <0.00%> (-6.35%)	⬇️