chore(deps): update all non-major dependencies (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vercel/node (source)	2.5.7 -> 2.5.8
esbuild	0.15.1 -> 0.15.2

---

Release Notes

vercel/vercel

v2.5.8

Compare Source

evanw/esbuild

v0.15.2

Compare Source

• Fix Yarn PnP issue with packages containing index.js (#​2455, #​2461)

  Yarn PnP's tests require the resolved paths to end in /. That's not how the rest of esbuild's internals work, however, and doing this messed up esbuild's node module path resolution regarding automatically-detected index.js files. Previously packages that relied on implicit index.js resolution rules didn't work with esbuild under Yarn PnP. Removing this slash has fixed esbuild's path resolution behavior regarding index.js, which should now the same both with and without Yarn PnP.

• Fix Yarn PnP support for extends in tsconfig.json (#​2456)

  Previously using extends in tsconfig.json with a path in a Yarn PnP package didn't work. This is because the process of setting up package path resolution rules requires parsing tsconfig.json files (due to the baseUrl and paths features) and resolving extends to a package path requires package path resolution rules to already be set up, which is a circular dependency. This cycle is broken by using special rules for extends in tsconfig.json that bypasses esbuild's normal package path resolution process. This is why using extends with a Yarn PnP package didn't automatically work. With this release, these special rules have been modified to check for a Yarn PnP manifest so this case should work now.

• Fix Yarn PnP support in esbuild-wasm (#​2458)

  When running esbuild via WebAssembly, Yarn PnP support previously failed because Go's file system internals return EINVAL when trying to read a .zip file as a directory when run with WebAssembly. This was unexpected because Go's file system internals return ENOTDIR for this case on native. This release updates esbuild to treat EINVAL like ENOTDIR in this case, which fixes using esbuild-wasm to bundle a Yarn PnP project.

  Note that to be able to use esbuild-wasm for Yarn PnP successfully, you currently have to run it using node instead of yarn node. This is because the file system shim that Yarn overwrites node's native file system API with currently generates invalid file descriptors with negative values when inside a .zip file. This prevents esbuild from working correctly because Go's file system internals don't expect syscalls that succeed without an error to return an invalid file descriptor. Yarn is working on fixing their use of invalid file descriptors.

---

Configuration

📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: ca389a5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

✅ Benchmark Results

     ✓ no_errors
     ✓ expected_result

     checks.........................: 100.00% ✓ 158352      ✗ 0    
     data_received..................: 21 MB   702 kB/s
     data_sent......................: 9.1 MB  304 kB/s
     http_req_blocked...............: avg=1.53µs   min=800ns    med=1.3µs    max=512.22µs p(90)=1.9µs    p(95)=2.29µs  
     http_req_connecting............: avg=2ns      min=0s       med=0s       max=194.01µs p(90)=0s       p(95)=0s      
   ✓ http_req_duration..............: avg=287.16µs min=155.41µs med=256.31µs max=21.58ms  p(90)=332.82µs p(95)=369.22µs
       { expected_response:true }...: avg=287.16µs min=155.41µs med=256.31µs max=21.58ms  p(90)=332.82µs p(95)=369.22µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 79176
     http_req_receiving.............: avg=23.82µs  min=10.7µs   med=21.9µs   max=7.88ms   p(90)=29.6µs   p(95)=32.7µs  
     http_req_sending...............: avg=10.4µs   min=4µs      med=8.5µs    max=5.79ms   p(90)=13.3µs   p(95)=14.4µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=252.92µs min=137µs    med=225.11µs max=21.36ms  p(90)=294.61µs p(95)=331.01µs
     http_reqs......................: 79176   2639.037242/s
     iteration_duration.............: avg=373.01µs min=216.51µs med=339.22µs max=22.33ms  p(90)=429.72µs p(95)=470.12µs
     iterations.....................: 79176   2639.037242/s
     vus............................: 1       min=1         max=1  
     vus_max........................: 1       min=1         max=1