Bump esbuild from 0.20.2 to 0.21.2

[dependabot]

Bumps esbuild from 0.20.2 to 0.21.2.

Release notes

Sourced from [esbuild's releases](https://github.com/evanw/esbuild/releases).

v0.21.2

• Correct this in field and accessor decorators ([YouTube mobile newsletter sign up  #3761](https://redirect.github.com/ES Decorators no binding to this evanw/esbuild#3761))

  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

  const dec = () => function() { this.bar = true }
  class Foo { dec static foo }
  console.log(Foo.bar) // Should be "true"

• Allow es2023 as a target environment ([Uplift pni tristate fields #3762](https://redirect.github.com/Missing es2023 target evanw/esbuild#3762))

  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

v0.21.1

• Fix a regression with --keep-names ([YouTube: add newsletter signup to mobile #3756](https://redirect.github.com/invalid code generation evanw/esbuild#3756))

  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

  // Original code
  x = { get y() {} }
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @PURE */ __name(function() {
  }, "y") };
  // Output from this version (with --keep-names)
  x = { get y() {
  } };

v0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

• Implement the JavaScript decorators proposal ([Home Page Iteration - merging tickets #104](https://redirect.github.com/Feature request: Decorators support evanw/esbuild#104))

  With this release, esbuild now contains an implementation of the upcoming [JavaScript decorators proposal](https://github.com/tc39/proposal-decorators). This is the same feature that shipped in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: [https://2ality.com/2022/10/javascript-decorators.html](https://2ality.com/2022/10/javascript-decorators.html). Here's a quick example:

  const log = (fn, context) => function() {
    console.log(`before ${context.name}`)
    const it = fn.apply(this, arguments)
    console.log(`after ${context.name}`)
    return it
  }
  class Foo {
  @​log static foo() {

... (truncated)

Changelog

Sourced from [esbuild's changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md).

0.21.2

• Correct this in field and accessor decorators ([YouTube mobile newsletter sign up  #3761](https://redirect.github.com/ES Decorators no binding to this evanw/esbuild#3761))

  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

  const dec = () => function() { this.bar = true }
  class Foo { dec static foo }
  console.log(Foo.bar) // Should be "true"

• Allow es2023 as a target environment ([Uplift pni tristate fields #3762](https://redirect.github.com/Missing es2023 target evanw/esbuild#3762))

  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.

0.21.1

• Fix a regression with --keep-names ([YouTube: add newsletter signup to mobile #3756](https://redirect.github.com/invalid code generation evanw/esbuild#3756))

  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

  // Original code
  x = { get y() {} }
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @PURE */ __name(function() {
  }, "y") };
  // Output from this version (with --keep-names)
  x = { get y() {
  } };

0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

• Implement the JavaScript decorators proposal ([Home Page Iteration - merging tickets #104](https://redirect.github.com/Feature request: Decorators support evanw/esbuild#104))

  With this release, esbuild now contains an implementation of the upcoming [JavaScript decorators proposal](https://github.com/tc39/proposal-decorators). This is the same feature that shipped in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: [https://2ality.com/2022/10/javascript-decorators.html](https://2ality.com/2022/10/javascript-decorators.html). Here's a quick example:

  const log = (fn, context) => function() {
    console.log(`before ${context.name}`)
    const it = fn.apply(this, arguments)
    console.log(`after ${context.name}`)
    return it
  }

... (truncated)

Commits

• b24180e publish 0.21.2 to npm
• f82e0ad fix [YouTube mobile newsletter sign up  #3761](https://redirect.github.com/ES Decorators no binding to this evanw/esbuild#3761): this in field and accessor decorators
• 46ea596 fix [Uplift pni tristate fields #3762](https://redirect.github.com/Missing es2023 target evanw/esbuild#3762): add es2023 as an alias for es2022
• e876394 publish 0.21.1 to npm
• 4abc387 adjust decorator source map locations
• e7a9256 fix [YouTube: add newsletter signup to mobile #3756](https://redirect.github.com/invalid code generation evanw/esbuild#3756): regression with --keep-names
• 33cbbea run make update-compat-table
• c6da2c3 publish 0.21.0 to npm
• 4bc834c initial implementation of the decorators proposal ([YouTube Regrets - newsletter button and style tweaks #3754](https://redirect.github.com/initial implementation of the decorators proposal evanw/esbuild#3754))
• 07cdbe0 some small adjustments to runtime library code
• Additional commits viewable in [compare view](https://github.com/evanw/esbuild/compare/v0.20.2...v0.21.2)

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

┆Issue is synchronized with this Jira Story

[dependabot]

Superseded by #12339.

[data-sync-user]

➤ Simon Acosta Torres commented:

PR has already been closed.