Bump esbuild from 0.14.34 to 0.14.36

[dependabot]

Bumps esbuild from 0.14.34 to 0.14.36.

Release notes

Sourced from esbuild's releases.

v0.14.36

• Revert path metadata validation for now (#2177)

  This release reverts the path metadata validation that was introduced in the previous release. This validation has uncovered a potential issue with how esbuild handles onResolve callbacks in plugins that will need to be fixed before path metadata validation is re-enabled.

v0.14.35

• Add support for parsing typeof on #private fields from TypeScript 4.7 (#2174)

  The upcoming version of TypeScript now lets you use #private fields in typeof type expressions:

  https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/#typeof-on-private-fields

  class Container {
    #data = "hello!";
  get data(): typeof this.#data {
  return this.#data;
  }
  set data(value: typeof this.#data) {
  this.#data = value;
  }
  }

  With this release, esbuild can now parse these new type expressions as well. This feature was contributed by @​magic-akari.

• Add Opera and IE to internal CSS feature support matrix (#2170)

  Version 0.14.18 of esbuild added Opera and IE as available target environments, and added them to the internal JS feature support matrix. CSS feature support was overlooked, however. This release adds knowledge of Opera and IE to esbuild's internal CSS feature support matrix:

  /* Original input */
  a {
    color: rgba(0, 0, 0, 0.5);
  }
  /* Old output (with --target=opera49 --minify) */
  a{color:rgba(0,0,0,.5)}
  /* New output (with --target=opera49 --minify) */
  a{color:#00000080}

  The fix for this issue was contributed by @​sapphi-red.

• Change TypeScript class field behavior when targeting ES2022

  TypeScript 4.3 introduced a breaking change where class field behavior changes from assign semantics to define semantics when the target setting in tsconfig.json is set to ESNext. Specifically, the default value for TypeScript's useDefineForClassFields setting when unspecified is true if and only if target is ESNext. TypeScript 4.6 introduced another change where this behavior now happens for both ESNext and ES2022. Presumably this will be the case for ES2023 and up as well. With this release, esbuild's behavior has also been changed to match. Now configuring esbuild with --target=es2022 will also cause TypeScript files to use the new class field behavior.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.36

• Revert path metadata validation for now (#2177)

  This release reverts the path metadata validation that was introduced in the previous release. This validation has uncovered a potential issue with how esbuild handles onResolve callbacks in plugins that will need to be fixed before path metadata validation is re-enabled.

0.14.35

• Add support for parsing typeof on #private fields from TypeScript 4.7 (#2174)

  The upcoming version of TypeScript now lets you use #private fields in typeof type expressions:

  https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/#typeof-on-private-fields

  class Container {
    #data = "hello!";
  get data(): typeof this.#data {
  return this.#data;
  }
  set data(value: typeof this.#data) {
  this.#data = value;
  }
  }

  With this release, esbuild can now parse these new type expressions as well. This feature was contributed by @​magic-akari.

• Add Opera and IE to internal CSS feature support matrix (#2170)

  Version 0.14.18 of esbuild added Opera and IE as available target environments, and added them to the internal JS feature support matrix. CSS feature support was overlooked, however. This release adds knowledge of Opera and IE to esbuild's internal CSS feature support matrix:

  /* Original input */
  a {
    color: rgba(0, 0, 0, 0.5);
  }
  /* Old output (with --target=opera49 --minify) */
  a{color:rgba(0,0,0,.5)}
  /* New output (with --target=opera49 --minify) */
  a{color:#00000080}

  The fix for this issue was contributed by @​sapphi-red.

• Change TypeScript class field behavior when targeting ES2022

... (truncated)

Commits

• 962eed8 publish 0.14.36 to npm
• a6d80fc fix #2177: Revert "check for consistent path metadata from plugins"
• 757d7d9 quoted comma separated string array helper
• ebcb111 publish 0.14.35 to npm
• 6491d15 change . to : in suggestion text
• 0286f66 suggest enabling missing exports condition (#2163)
• 45c0ab2 changelog for #2170
• 049e43c add opera/ie to css feature table (#2170)
• 7b4b5e3 feat: support typeof on #private Fields (#2174)
• ddd53f9 fix test flake with non-deterministic build
• 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)