Bump esbuild from 0.12.28 to 0.12.29

[dependabot]

Bumps esbuild from 0.12.28 to 0.12.29.

Release notes

Sourced from esbuild's releases.

v0.12.29

• Fix compilation of abstract class fields in TypeScript (#1623)

  This release fixes a bug where esbuild could incorrectly include a TypeScript abstract class field in the compiled JavaScript output. This is incorrect because the official TypeScript compiler never does this. Note that this only happened in scenarios where TypeScript's useDefineForClassFields setting was set to true (or equivalently where TypeScript's target setting was set to ESNext). Here is the difference:

  // Original code
  abstract class Foo {
    abstract foo: any;
  }
  // Old output
  class Foo {
  foo;
  }
  // New output
  class Foo {
  }

• Proxy from the __require shim to require (#1614)

  Some background: esbuild's bundler emulates a CommonJS environment. The bundling process replaces the literal syntax require(<string>) with the referenced module at compile-time. However, other uses of require such as require(someFunction()) are not bundled since the value of someFunction() depends on code evaluation, and esbuild does not evaluate code at compile-time. So it's possible for some references to require to remain after bundling.

  This was causing problems for some CommonJS code that was run in the browser and that expected typeof require === 'function' to be true (see #1202), since the browser does not provide a global called require. Thus esbuild introduced a shim require function called __require (shown below) and replaced all references to require in the bundled code with __require:

  var __require = x => {
    if (typeof require !== 'undefined') return require(x);
    throw new Error('Dynamic require of "' + x + '" is not supported');
  };

  However, this broke code that referenced require.resolve inside the bundle, which could hypothetically actually work since you could assign your own implementation to window.require.resolve (see #1579). So the implementation of __require was changed to this:

  var __require = typeof require !== 'undefined' ? require : x => {
    throw new Error('Dynamic require of "' + x + '" is not supported');
  };

  However, that broke code that assigned to window.require later on after the bundle was loaded (#1614). So with this release, the code for __require now handles all of these edge cases:

  • typeof require is still function even if window.require is undefined
  • window.require can be assigned to either before or after the bundle is loaded
  • require.resolve and arbitrary other properties can still be accessed
  • require will now forward any number of arguments, not just the first one

  Handling all of these edge cases is only possible with the Proxy API. So the implementation of __require now looks like this:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.12.29

• Fix compilation of abstract class fields in TypeScript (#1623)

  This release fixes a bug where esbuild could incorrectly include a TypeScript abstract class field in the compiled JavaScript output. This is incorrect because the official TypeScript compiler never does this. Note that this only happened in scenarios where TypeScript's useDefineForClassFields setting was set to true (or equivalently where TypeScript's target setting was set to ESNext). Here is the difference:

  // Original code
  abstract class Foo {
    abstract foo: any;
  }
  // Old output
  class Foo {
  foo;
  }
  // New output
  class Foo {
  }

• Proxy from the __require shim to require (#1614)

  Some background: esbuild's bundler emulates a CommonJS environment. The bundling process replaces the literal syntax require(<string>) with the referenced module at compile-time. However, other uses of require such as require(someFunction()) are not bundled since the value of someFunction() depends on code evaluation, and esbuild does not evaluate code at compile-time. So it's possible for some references to require to remain after bundling.

  This was causing problems for some CommonJS code that was run in the browser and that expected typeof require === 'function' to be true (see #1202), since the browser does not provide a global called require. Thus esbuild introduced a shim require function called __require (shown below) and replaced all references to require in the bundled code with __require:

  var __require = x => {
    if (typeof require !== 'undefined') return require(x);
    throw new Error('Dynamic require of "' + x + '" is not supported');
  };

  However, this broke code that referenced require.resolve inside the bundle, which could hypothetically actually work since you could assign your own implementation to window.require.resolve (see #1579). So the implementation of __require was changed to this:

  var __require = typeof require !== 'undefined' ? require : x => {
    throw new Error('Dynamic require of "' + x + '" is not supported');
  };

  However, that broke code that assigned to window.require later on after the bundle was loaded (#1614). So with this release, the code for __require now handles all of these edge cases:

  • typeof require is still function even if window.require is undefined
  • window.require can be assigned to either before or after the bundle is loaded
  • require.resolve and arbitrary other properties can still be accessed
  • require will now forward any number of arguments, not just the first one

... (truncated)

Commits

• 7d15c6d publish 0.12.29 to npm
• 9452fce add "--analyze" to cli help text
• d4d0d65 fix missing return in "IsNumericValue"
• 7ecdc28 fix mangle syntax edge case with "==" and "!="
• 61155d5 fix "__require" to have no side effects
• 0b90b0a "typeof identifier" has no side effects
• 3249e05 fix #1623: ignore class fields marked "abstract"
• e03e743 fix #1614: proxy from "__require" to "require"
• See full diff 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)