Bump esbuild from 0.20.2 to 0.21.3

[dependabot]

Bumps esbuild from 0.20.2 to 0.21.3.

Release notes

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

v0.21.3

• Implement the decorator metadata proposal ([PNI homepage/categories: only show products with review date within one year #3760](https://redirect.github.com/Feature request: Implement the Decorator Metadata proposal evanw/esbuild#3760))

  This release implements the [decorator metadata proposal](https://github.com/tc39/proposal-decorator-metadata), which is a sub-proposal of the [decorators proposal](https://github.com/tc39/proposal-decorators). Microsoft shipped the decorators proposal in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) and the decorator metadata proposal in [TypeScript 5.2](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata), so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
  }
  class Foo {
  @​track foo = 1
  @​track bar = 2
  }
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes ([Fix lang reset #3768](https://redirect.github.com/ES decorators bug with inheritance and --bundle evanw/esbuild#3768))

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories ([PNI: update badge #3767](https://redirect.github.com/compilerOptions.paths not resolved when tsconfig extends from another package evanw/esbuild#3767))

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

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 }

... (truncated)

Changelog

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

0.21.3

• Implement the decorator metadata proposal ([PNI homepage/categories: only show products with review date within one year #3760](https://redirect.github.com/Feature request: Implement the Decorator Metadata proposal evanw/esbuild#3760))

  This release implements the [decorator metadata proposal](https://github.com/tc39/proposal-decorator-metadata), which is a sub-proposal of the [decorators proposal](https://github.com/tc39/proposal-decorators). Microsoft shipped the decorators proposal in [TypeScript 5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators) and the decorator metadata proposal in [TypeScript 5.2](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata), so it's important that esbuild also supports both of these features. Here's a quick example:

  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
  }
  class Foo {
  @​track foo = 1
  @​track bar = 2
  }
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)

  ⚠️ WARNING ⚠️

  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

• Fix bundled decorators in derived classes ([Fix lang reset #3768](https://redirect.github.com/ES decorators bug with inheritance and --bundle evanw/esbuild#3768))

  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

  class Foo extends Object {
    @(x => x) foo() {
      return Foo
    }
  }
  console.log(new Foo().foo())

• Fix tsconfig.json files inside symlinked directories ([PNI: update badge #3767](https://redirect.github.com/compilerOptions.paths not resolved when tsconfig extends from another package evanw/esbuild#3767))

  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

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:

... (truncated)

Commits

• efa3dd2 publish 0.21.3 to npm
• 5e7cf25 fix [PNI homepage/categories: only show products with review date within one year #3760](https://redirect.github.com/Feature request: Implement the Decorator Metadata proposal evanw/esbuild#3760): implement decorator metadata proposal
• bd0b13b lowering: always propagate class expression names
• 90acd14 explicit bitwise operators for initializer flags
• ba548df move decorator initializer list to after the class
• 66b7c6d fix [Fix lang reset #3768](https://redirect.github.com/ES decorators bug with inheritance and --bundle evanw/esbuild#3768): bundled decorators in derived classes
• 6e6f15f fix [PNI: update badge #3767](https://redirect.github.com/compilerOptions.paths not resolved when tsconfig extends from another package evanw/esbuild#3767): tsconfig.json files inside symlinks
• b7dcb95 transform: reuse lowerField for auto-accessors
• 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
• Additional commits viewable in [compare view](https://github.com/evanw/esbuild/compare/v0.20.2...v0.21.3)

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 #12378.

[data-sync-user]

➤ Simon Acosta Torres commented:

PR has been closed.