chore: bump esbuild from 0.14.10 to 0.14.24

[dependabot]

Bumps esbuild from 0.14.10 to 0.14.24.

Release notes

Sourced from esbuild's releases.

v0.14.24

• Allow es2022 as a target environment (#2012)

  TypeScript recently added support for es2022 as a compilation target so esbuild now supports this too. Support for this is preliminary as there is no published ES2022 specification yet (i.e. https://tc39.es/ecma262/2021/ exists but https://tc39.es/ecma262/2022/ is a 404 error). The meaning of esbuild's es2022 target may change in the future when the specification is finalized. Right now I have made the es2022 target enable support for the syntax-related finished proposals that are marked as 2022:

  • Class fields
  • Class private members
  • Class static blocks
  • Ergonomic class private member checks
  • Top-level await

  I have also included the "arbitrary module namespace names" feature since I'm guessing it will end up in the ES2022 specification (this syntax feature was added to the specification without a proposal). TypeScript has not added support for this yet.

• Match define to strings in index expressions (#2050)

  With this release, configuring --define:foo.bar=baz now matches and replaces both foo.bar and foo['bar'] expressions in the original source code. This is necessary for people who have enabled TypeScript's noPropertyAccessFromIndexSignature feature, which prevents you from using normal property access syntax on a type with an index signature such as in the following code:

  declare let foo: { [key: string]: any }
  foo.bar // This is a type error if noPropertyAccessFromIndexSignature is enabled
  foo['bar']

  Previously esbuild would generate the following output with --define:foo.bar=baz:

  baz;
  foo["bar"];

  Now esbuild will generate the following output instead:

  baz;
  baz;

• Add --mangle-quoted to mangle quoted properties (#218)

  The --mangle-props= flag tells esbuild to automatically rename all properties matching the provided regular expression to shorter names to save space. Previously esbuild never modified the contents of string literals. In particular, --mangle-props=_ would mangle foo._bar but not foo['_bar']. There are some coding patterns where renaming quoted property names is desirable, such as when using TypeScript's noPropertyAccessFromIndexSignature feature or when using TypeScript's discriminated union narrowing behavior:

  interface Foo { _foo: string }
  interface Bar { _bar: number }
  declare const value: Foo | Bar
  console.log('_foo' in value ? value._foo : value._bar)

  The '_foo' in value check tells TypeScript to narrow the type of value to Foo in the true branch and to Bar in the false branch. Previously esbuild didn't mangle the property name '_foo' because it was inside a string literal. With this release, you can now use --mangle-quoted to also rename property names inside string literals:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.24

• Allow es2022 as a target environment (#2012)

  TypeScript recently added support for es2022 as a compilation target so esbuild now supports this too. Support for this is preliminary as there is no published ES2022 specification yet (i.e. https://tc39.es/ecma262/2021/ exists but https://tc39.es/ecma262/2022/ is a 404 error). The meaning of esbuild's es2022 target may change in the future when the specification is finalized. Right now I have made the es2022 target enable support for the syntax-related finished proposals that are marked as 2022:

  • Class fields
  • Class private members
  • Class static blocks
  • Ergonomic class private member checks
  • Top-level await

  I have also included the "arbitrary module namespace names" feature since I'm guessing it will end up in the ES2022 specification (this syntax feature was added to the specification without a proposal). TypeScript has not added support for this yet.

• Match define to strings in index expressions (#2050)

  With this release, configuring --define:foo.bar=baz now matches and replaces both foo.bar and foo['bar'] expressions in the original source code. This is necessary for people who have enabled TypeScript's noPropertyAccessFromIndexSignature feature, which prevents you from using normal property access syntax on a type with an index signature such as in the following code:

  declare let foo: { [key: string]: any }
  foo.bar // This is a type error if noPropertyAccessFromIndexSignature is enabled
  foo['bar']

  Previously esbuild would generate the following output with --define:foo.bar=baz:

  baz;
  foo["bar"];

  Now esbuild will generate the following output instead:

  baz;
  baz;

• Add --mangle-quoted to mangle quoted properties (#218)

  The --mangle-props= flag tells esbuild to automatically rename all properties matching the provided regular expression to shorter names to save space. Previously esbuild never modified the contents of string literals. In particular, --mangle-props=_ would mangle foo._bar but not foo['_bar']. There are some coding patterns where renaming quoted property names is desirable, such as when using TypeScript's noPropertyAccessFromIndexSignature feature or when using TypeScript's discriminated union narrowing behavior:

  interface Foo { _foo: string }
  interface Bar { _bar: number }
  declare const value: Foo | Bar
  console.log('_foo' in value ? value._foo : value._bar)

  The '_foo' in value check tells TypeScript to narrow the type of value to Foo in the true branch and to Bar in the false branch. Previously esbuild didn't mangle the property name '_foo' because it was inside a string literal. With this release, you can now use --mangle-quoted to also rename property names inside string literals:

... (truncated)

Commits

• b6648af publish 0.14.24 to npm
• 351eb5b add wasm early-exit performance hack for linux arm
• 9a7b108 add wasm early-exit performance hack for macos arm
• b690fe8 attempt wasm fallback on android x64 (#2068)
• 8e28f5a follow-up to #2035
• e0f9d7d disable Go compiler optimization for riscv64 (#2035)
• 7835274 add an "es2022" target (#2012)
• d40ff59 follow-up to #2075
• 8602fd1 Ignore type-only entries in paths (#2075)
• 3c399c1 forgot to commit test snapshots
• Additional commits viewable 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)

[dependabot]

Superseded by #103.