Bump esbuild from 0.14.27 to 0.14.30

[dependabot]

Bumps esbuild from 0.14.27 to 0.14.30.

Release notes

Sourced from esbuild's releases.

v0.14.30

• Change the context of TypeScript parameter decorators (#2147)

  While TypeScript parameter decorators are expressions, they are not evaluated where they exist in the code. They are moved to after the class declaration and evaluated there instead. Specifically this TypeScript code:

  class Class {
    method(@decorator() arg) {}
  }

  becomes this JavaScript code:

  class Class {
    method(arg) {}
  }
  __decorate([
    __param(0, decorator())
  ], Class.prototype, "method", null);

  This has several consequences:

  • Whether await is allowed inside a decorator expression or not depends on whether the class declaration itself is in an async context or not. With this release, you can now use await inside a decorator expression when the class declaration is either inside an async function or is at the top-level of an ES module and top-level await is supported. Note that the TypeScript compiler currently has a bug regarding this edge case: microsoft/TypeScript#48509.

    // Using "await" inside a decorator expression is now allowed
    async function fn(foo: Promise<any>) {
      class Class {
        method(@decorator(await foo) arg) {}
      }
      return Class
    }

    Also while TypeScript currently allows await to be used like this in async functions, it doesn't currently allow yield to be used like this in generator functions. It's not yet clear whether this behavior with yield is a bug or by design, so I haven't made any changes to esbuild's handling of yield inside decorator expressions in this release.

  • Since the scope of a decorator expression is the scope enclosing the class declaration, they cannot access private identifiers. Previously this was incorrectly allowed but with this release, esbuild no longer allows this. Note that the TypeScript compiler currently has a bug regarding this edge case: microsoft/TypeScript#48515.

    // Using private names inside a decorator expression is no longer allowed
    class Class {
      static #priv = 123
      method(@decorator(Class.#priv) arg) {}
    }

  • Since the scope of a decorator expression is the scope enclosing the class declaration, identifiers inside parameter decorator expressions should never be resolved to a parameter of the enclosing method. Previously this could happen, which was a bug with esbuild. This bug no longer happens in this release.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.30

• Change the context of TypeScript parameter decorators (#2147)

  While TypeScript parameter decorators are expressions, they are not evaluated where they exist in the code. They are moved to after the class declaration and evaluated there instead. Specifically this TypeScript code:

  class Class {
    method(@decorator() arg) {}
  }

  becomes this JavaScript code:

  class Class {
    method(arg) {}
  }
  __decorate([
    __param(0, decorator())
  ], Class.prototype, "method", null);

  This has several consequences:

  • Whether await is allowed inside a decorator expression or not depends on whether the class declaration itself is in an async context or not. With this release, you can now use await inside a decorator expression when the class declaration is either inside an async function or is at the top-level of an ES module and top-level await is supported. Note that the TypeScript compiler currently has a bug regarding this edge case: microsoft/TypeScript#48509.

    // Using "await" inside a decorator expression is now allowed
    async function fn(foo: Promise<any>) {
      class Class {
        method(@decorator(await foo) arg) {}
      }
      return Class
    }

    Also while TypeScript currently allows await to be used like this in async functions, it doesn't currently allow yield to be used like this in generator functions. It's not yet clear whether this behavior with yield is a bug or by design, so I haven't made any changes to esbuild's handling of yield inside decorator expressions in this release.

  • Since the scope of a decorator expression is the scope enclosing the class declaration, they cannot access private identifiers. Previously this was incorrectly allowed but with this release, esbuild no longer allows this. Note that the TypeScript compiler currently has a bug regarding this edge case: microsoft/TypeScript#48515.

    // Using private names inside a decorator expression is no longer allowed
    class Class {
      static #priv = 123
      method(@decorator(Class.#priv) arg) {}
    }

  • Since the scope of a decorator expression is the scope enclosing the class declaration, identifiers inside parameter decorator expressions should never be resolved to a parameter of the enclosing method. Previously this could happen, which was a bug with esbuild. This bug no longer happens in this release.

... (truncated)

Commits

• e568c4e publish 0.14.30 to npm
• c1fbfd0 changelog: containing => contained
• f4c6b54 fix another super class lowering edge case
• ae23f41 test coverage for potential default export failure
• c9e2fdb fix some generated temporary use counts
• e16cde0 async method + super + object + loop test coverage
• 8b236f3 internal: always pass the class name reference
• d8ec066 rename shouldLowerSuperPropertyAccess
• 02a794e always generate the class body shadow symbol
• 0c9ced5 fix an obscure super property access edge case
• 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 #107.