chore(deps): update dependency esbuild to v0.15.1 (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	0.15.0 -> 0.15.1

---

Release Notes

evanw/esbuild

v0.15.1

Compare Source

• Update esbuild's Yarn Plug'n'Play implementation to match the latest specification changes (#​2452, #​2453)

  This release updates esbuild's implementation of Yarn Plug'n'Play to match some changes to Yarn's specification that just landed. The changes are as follows:

  • Check for platform-specific absolute paths instead of always for the / prefix

    The specification previously said that Yarn Plug'n'Play path resolution rules should not apply for paths that start with /. The intent was to avoid accidentally processing absolute paths. However, absolute paths on Windows such as C:\project start with drive letters instead of with /. So the specification was changed to instead explicitly avoid processing absolute paths.

  • Make $$virtual an alias for __virtual__

    Supporting Yarn-style path resolution requires implementing a custom Yarn-specific path traversal scheme where certain path segments are considered no-ops. Specifically any path containing segments of the form __virtual__/<whatever>/<n> where <n> is an integer must be treated as if they were n times the .. operator instead (the <whatever> path segment is ignored). So /path/to/project/__virtual__/xyz/2/foo.js maps to the underlying file /path/to/project/../../foo.js. This scheme makes it possible for Yarn to get node (and esbuild) to load the same file multiple times (which is sometimes required for correctness) without actually duplicating the file on the file system.

    However, old versions of Yarn used to use $$virtual instead of __virtual__. This was changed because $$virtual was error-prone due to the use of the $ character, which can cause bugs when it's not correctly escaped within regular expressions. Now that esbuild makes $$virtual an alias for __virtual__, esbuild should now work with manifests from these old Yarn versions.

  • Ignore PnP manifests in virtual directories

    The specification describes the algorithm for how to find the Plug'n'Play manifest when starting from a certain point in the file system: search through all parent directories in reverse order until the manifest is found. However, this interacts poorly with virtual paths since it can end up finding a virtual copy of the manifest instead of the original. To avoid this, esbuild now ignores manifests in virtual directories so that the search for the manifest will continue and find the original manifest in another parent directory later on.

  These fixes mean that esbuild's implementation of Plug'n'Play now matches Yarn's implementation more closely, and esbuild can now correctly build more projects that use Plug'n'Play.

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• 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: cbd099d

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% ✓ 194488      ✗ 0    
     data_received..................: 26 MB   862 kB/s
     data_sent......................: 11 MB   373 kB/s
     http_req_blocked...............: avg=1.32µs   min=700ns   med=1.1µs    max=4.03ms  p(90)=1.5µs   p(95)=2µs     
     http_req_connecting............: avg=1ns      min=0s      med=0s       max=141.2µs p(90)=0s      p(95)=0s      
   ✓ http_req_duration..............: avg=232.39µs min=139.3µs med=206.11µs max=20.93ms p(90)=270.8µs p(95)=313.89µs
       { expected_response:true }...: avg=232.39µs min=139.3µs med=206.11µs max=20.93ms p(90)=270.8µs p(95)=313.89µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 97244
     http_req_receiving.............: avg=19.67µs  min=9.7µs   med=17.7µs   max=4.83ms  p(90)=25.3µs  p(95)=29.7µs  
     http_req_sending...............: avg=7.85µs   min=3.6µs   med=5.2µs    max=3.64ms  p(90)=12.2µs  p(95)=12.9µs  
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s       max=0s      p(90)=0s      p(95)=0s      
     http_req_waiting...............: avg=204.86µs min=121.9µs med=182.2µs  max=20.82ms p(90)=238.3µs p(95)=275.8µs 
     http_reqs......................: 97244   3241.330224/s
     iteration_duration.............: avg=303.35µs min=187.4µs med=272.5µs  max=21.42ms p(90)=357.5µs p(95)=409.11µs
     iterations.....................: 97244   3241.330224/s
     vus............................: 0       min=0         max=1  
     vus_max........................: 1       min=1         max=1