Bump esbuild from 0.13.12 to 0.17.19

[dependabot]

Bumps esbuild from 0.13.12 to 0.17.19.

Release notes

Sourced from esbuild's releases.

v0.17.19

• Fix CSS transform bugs with nested selectors that start with a combinator (#3096)

  This release fixes several bugs regarding transforming nested CSS into non-nested CSS for older browsers. The bugs were due to lack of test coverage for nested selectors with more than one compound selector where they all start with the same combinator. Here's what some problematic cases look like before and after these fixes:

  /* Original code */
  .foo {
    > &a,
    > &b {
      color: red;
    }
  }
  .bar {
    > &a,
    + &b {
      color: green;
    }
  }
  /* Old output (with --target=chrome90) */
  .foo :is(> .fooa, > .foob) {
  color: red;
  }
  .bar :is(> .bara, + .barb) {
  color: green;
  }
  /* New output (with --target=chrome90) */
  .foo > :is(a.foo, b.foo) {
  color: red;
  }
  .bar > a.bar,
  .bar + b.bar {
  color: green;
  }

• Fix bug with TypeScript parsing of instantiation expressions followed by = (#3111)

  This release fixes esbuild's TypeScript-to-JavaScript conversion code in the case where a potential instantiation expression is followed immediately by a = token (such that the trailing > becomes a >= token). Previously esbuild considered that to still be an instantiation expression, but the official TypeScript compiler considered it to be a >= operator instead. This release changes esbuild's interpretation to match TypeScript. This edge case currently appears to be problematic for other TypeScript-to-JavaScript converters as well:

  Original code	TypeScript	esbuild 0.17.18	esbuild 0.17.19	Sucrase	Babel
  x<y>=a<b<c>>()	x<y>=a();	x=a();	x<y>=a();	x=a()	Invalid left-hand side in assignment expression

• Avoid removing unrecognized directives from the directive prologue when minifying (#3115)

  The directive prologue in JavaScript is a sequence of top-level string expressions that come before your code. The only directives that JavaScript engines currently recognize are use strict and sometimes use asm. However, the people behind React have made up their own directive for their own custom dialect of JavaScript. Previously esbuild only preserved the use strict directive when minifying, although you could still write React JavaScript with esbuild using something like --banner:js="'your directive here';". With this release, you can now put arbitrary directives in the entry point and esbuild will preserve them in its minified output:

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2021

This changelog documents all esbuild versions published in the year 2021 (versions 0.8.29 through 0.14.10).

0.14.10

• Enable tree shaking of classes with lowered static fields (#175)

  If the configured target environment doesn't support static class fields, they are converted into a call to esbuild's __publicField function instead. However, esbuild's tree-shaking pass treated this call as a side effect, which meant that all classes with static fields were ineligible for tree shaking. This release fixes the problem by explicitly ignoring calls to the __publicField function during tree shaking side-effect determination. Tree shaking is now enabled for these classes:

  // Original code
  class Foo { static foo = 'foo' }
  class Bar { static bar = 'bar' }
  new Bar()
  // Old output (with --tree-shaking=true --target=es6)
  class Foo {
  }
  __publicField(Foo, "foo", "foo");
  class Bar {
  }
  __publicField(Bar, "bar", "bar");
  new Bar();
  // New output (with --tree-shaking=true --target=es6)
  class Bar {
  }
  __publicField(Bar, "bar", "bar");
  new Bar();

• Treat --define:foo=undefined as an undefined literal instead of an identifier (#1407)

  References to the global variable undefined are automatically replaced with the literal value for undefined, which appears as void 0 when printed. This allows for additional optimizations such as collapsing undefined ?? bar into just bar. However, this substitution was not done for values specified via --define:. As a result, esbuild could potentially miss out on certain optimizations in these cases. With this release, it's now possible to use --define: to substitute something with an undefined literal:

  // Original code
  let win = typeof window !== 'undefined' ? window : {}
  // Old output (with --define:window=undefined --minify)
  let win=typeof undefined!="undefined"?undefined:{};
  // New output (with --define:window=undefined --minify)
  let win={};

• Add the --drop:debugger flag (#1809)

  Passing this flag causes all debugger; statements to be removed from the output. This is similar to the drop_debugger: true flag available in the popular UglifyJS and Terser JavaScript minifiers.

... (truncated)

Commits

• d47ab43 publish 0.17.19 to npm
• 3a81eb5 update go 1.20.3 => 1.20.4
• 7cf5257 fix #3111: incorrect ts parsing of x \< y >= z
• a3fcf70 fix #3096: css transform bug with nested selectors
• c19689a fix #3115: pass through unknown js directives
• d686756 minify: fold more shift operations when shorter
• 7d11ef1 fix for validation warnings
• ee646b4 publish 0.17.18 to npm
• ecea1f4 put back comment that was removed
• 9092a1b perf(linker): Fixes brute force chunk cycle detection (#3069)
• 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)