Bump esbuild from 0.17.10 to 0.17.11 in /internal/ui

[dependabot]

Bumps esbuild from 0.17.10 to 0.17.11.

Release notes

Sourced from esbuild's releases.

v0.17.11

• Fix the alias feature to always prefer the longest match (#2963)

  It's possible to configure conflicting aliases such as --alias:a=b and --alias:a/c=d, which is ambiguous for the import path a/c/x (since it could map to either b/c/x or d/x). Previously esbuild would pick the first matching alias, which would non-deterministically pick between one of the possible matches. This release fixes esbuild to always deterministically pick the longest possible match.

• Minify calls to some global primitive constructors (#2962)

  With this release, esbuild's minifier now replaces calls to Boolean/Number/String/BigInt with equivalent shorter code when relevant:

  // Original code
  console.log(
    Boolean(a ? (b | c) !== 0 : (c & d) !== 0),
    Number(e ? '1' : '2'),
    String(e ? '1' : '2'),
    BigInt(e ? 1n : 2n),
  )
  // Old output (with --minify)
  console.log(Boolean(a?(b|c)!==0:(c&d)!==0),Number(e?"1":"2"),String(e?"1":"2"),BigInt(e?1n:2n));
  // New output (with --minify)
  console.log(!!(a?b|c:c&d),+(e?"1":"2"),e?"1":"2",e?1n:2n);

• Adjust some feature compatibility tables for node (#2940)

  This release makes the following adjustments to esbuild's internal feature compatibility tables for node, which tell esbuild which versions of node are known to support all aspects of that feature:

  • class-private-brand-checks: node v16.9+ => node v16.4+ (a decrease)
  • hashbang: node v12.0+ => node v12.5+ (an increase)
  • optional-chain: node v16.9+ => node v16.1+ (a decrease)
  • template-literal: node v4+ => node v10+ (an increase)

  Each of these adjustments was identified by comparing against data from the node-compat-table package and was manually verified using old node executables downloaded from https://nodejs.org/download/release/.

Changelog

Sourced from esbuild's changelog.

0.17.11

• Fix the alias feature to always prefer the longest match (#2963)

  It's possible to configure conflicting aliases such as --alias:a=b and --alias:a/c=d, which is ambiguous for the import path a/c/x (since it could map to either b/c/x or d/x). Previously esbuild would pick the first matching alias, which would non-deterministically pick between one of the possible matches. This release fixes esbuild to always deterministically pick the longest possible match.

• Minify calls to some global primitive constructors (#2962)

  With this release, esbuild's minifier now replaces calls to Boolean/Number/String/BigInt with equivalent shorter code when relevant:

  // Original code
  console.log(
    Boolean(a ? (b | c) !== 0 : (c & d) !== 0),
    Number(e ? '1' : '2'),
    String(e ? '1' : '2'),
    BigInt(e ? 1n : 2n),
  )
  // Old output (with --minify)
  console.log(Boolean(a?(b|c)!==0:(c&d)!==0),Number(e?"1":"2"),String(e?"1":"2"),BigInt(e?1n:2n));
  // New output (with --minify)
  console.log(!!(a?b|c:c&d),+(e?"1":"2"),e?"1":"2",e?1n:2n);

• Adjust some feature compatibility tables for node (#2940)

  This release makes the following adjustments to esbuild's internal feature compatibility tables for node, which tell esbuild which versions of node are known to support all aspects of that feature:

  • class-private-brand-checks: node v16.9+ => node v16.4+ (a decrease)
  • hashbang: node v12.0+ => node v12.5+ (an increase)
  • optional-chain: node v16.9+ => node v16.1+ (a decrease)
  • template-literal: node v4+ => node v10+ (an increase)

  Each of these adjustments was identified by comparing against data from the node-compat-table package and was manually verified using old node executables downloaded from https://nodejs.org/download/release/.

Commits

• 38cfd53 publish 0.17.11 to npm
• f93e25d update go 1.20 => 1.20.1
• 3f51381 fix #2964: install script reads version from file
• 1978946 fix #2963: a non-determinism bug with alias
• 2176b35 fix #2962: minify global primitive constructors
• a5f781e fix #2940: adjust node's values in compat-table
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)