chore(deps-dev): bump esbuild from 0.20.1 to 0.20.2

[dependabot]

Bumps esbuild from 0.20.1 to 0.20.2.

Release notes

Sourced from esbuild's releases.

v0.20.2

• Support TypeScript experimental decorators on abstract class fields (#3684)

  With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

  // Original code
  const log = (x: any, y: string) => console.log(y)
  abstract class Foo { @log abstract foo: string }
  new class extends Foo { foo = '' }
  // Old output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  new class extends Foo {
  foo = "";
  }();
  // New output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  __decorateClass([
  log
  ], Foo.prototype, "foo", 2);
  new class extends Foo {
  foo = "";
  }();

• JSON loader now preserves __proto__ properties (#3700)

  Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

  // Original code
  import data from 'data:application/json,{"__proto__":{"fail":true}}'
  if (Object.getPrototypeOf(data)?.fail) throw 'fail'
  // Old output (with --bundle)
  (() => {
  // <data:application/json,{"proto":{"fail":true}}>
  var json_proto_fail_true_default = { proto: { fail: true } };
  // entry.js
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
  throw "fail";
  })();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.2

• Support TypeScript experimental decorators on abstract class fields (#3684)

  With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

  // Original code
  const log = (x: any, y: string) => console.log(y)
  abstract class Foo { @log abstract foo: string }
  new class extends Foo { foo = '' }
  // Old output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  new class extends Foo {
  foo = "";
  }();
  // New output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
  const log = (x, y) => console.log(y);
  class Foo {
  }
  __decorateClass([
  log
  ], Foo.prototype, "foo", 2);
  new class extends Foo {
  foo = "";
  }();

• JSON loader now preserves __proto__ properties (#3700)

  Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

  // Original code
  import data from 'data:application/json,{"__proto__":{"fail":true}}'
  if (Object.getPrototypeOf(data)?.fail) throw 'fail'
  // Old output (with --bundle)
  (() => {
  // <data:application/json,{"proto":{"fail":true}}>
  var json_proto_fail_true_default = { proto: { fail: true } };
  // entry.js
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
  throw "fail";
  })();

... (truncated)

Commits

• 617edda publish 0.20.2 to npm
• 4780075 fix #3700: json loader preserves __proto__ keys
• 30bed2d better errors for invalid js decorator syntax
• 300eeb7 ts: allow non-null assertions in js decorators
• 4d997d9 fix #3698: yarn pnp edge case with tsconfig.json
• cf42954 resolver: improve some debug logging
• b0765ae fix some lints
• dfa6206 fix some comments (closes #3683)
• ae5cc17 fix #3684: abstract experimental decorators
• c809af0 fix #2388: allow consuming types without dom types (#3679)
• 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 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)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a2037b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[andykenward]

@dependabot rebase