build(deps-dev): Bump esbuild from 0.18.6 to 0.18.11

[dependabot]

Bumps esbuild from 0.18.6 to 0.18.11.

Release notes

Sourced from esbuild's releases.

v0.18.11

• Fix a TypeScript code generation edge case (#3199)

  This release fixes a regression in version 0.18.4 where using a TypeScript namespace that exports a class declaration combined with --keep-names and a --target of es2021 or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to X2._Y vs. X2.Y):

  // Original code
  // Old output (with --keep-names --target=es2021)
  var X;
  ((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2._Y = _Y;
  })(X || (X = {}));
  // New output (with --keep-names --target=es2021)
  var X;
  ((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2.Y = _Y;
  })(X || (X = {}));

v0.18.10

• Fix a tree-shaking bug that removed side effects (#3195)

  This fixes a regression in version 0.18.4 where combining --minify-syntax with --keep-names could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because --keep-names generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then --minify-syntax could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.

• Fix an incorrect warning about CSS nesting (#3197)

  A warning is currently generated when transforming nested CSS to a browser that doesn't support :is() because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as @top-left within @page. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.

v0.18.9

• Fix await using declarations inside async generator functions

  I forgot about the new await using declarations when implementing lowering for async generator functions in the previous release. This change fixes the transformation of await using declarations when they are inside lowered async generator functions:

  // Original code
  async function* foo() {
    await using x = await y
  }
  // Old output (with --supported:async-generator=false)

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.18.11

• Fix a TypeScript code generation edge case (#3199)

  This release fixes a regression in version 0.18.4 where using a TypeScript namespace that exports a class declaration combined with --keep-names and a --target of es2021 or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to X2._Y vs. X2.Y):

  // Original code
  // Old output (with --keep-names --target=es2021)
  var X;
  ((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2._Y = _Y;
  })(X || (X = {}));
  // New output (with --keep-names --target=es2021)
  var X;
  ((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2.Y = _Y;
  })(X || (X = {}));

0.18.10

• Fix a tree-shaking bug that removed side effects (#3195)

  This fixes a regression in version 0.18.4 where combining --minify-syntax with --keep-names could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because --keep-names generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then --minify-syntax could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.

• Fix an incorrect warning about CSS nesting (#3197)

  A warning is currently generated when transforming nested CSS to a browser that doesn't support :is() because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as @top-left within @page. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.

0.18.9

• Fix await using declarations inside async generator functions

  I forgot about the new await using declarations when implementing lowering for async generator functions in the previous release. This change fixes the transformation of await using declarations when they are inside lowered async generator functions:

  // Original code
  async function* foo() {
    await using x = await y

... (truncated)

Commits

• 2703f90 publish 0.18.11 to npm
• cd23ee5 fix #3199: keep names + namespace + export class
• 52110fd fix catch block mapping in source maps
• babcb2c alphabetize engine names in generated code
• cdb6c7c publish 0.18.10 to npm
• 8a15942 fix #3197: css nesting warning in selector subtree
• b677152 fix #3195: tree-shaking bug that didn't keep code
• d568ff0 publish 0.18.9 to npm
• 7e10dd6 fix #2041: add text loader data to source maps
• 9ed47f5 fix #3122: prefix some more css properties
• 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

[flexdevelopment]

lgtm 👍🏾

[flexdevelopment]

lgtm 👍🏾

[flexdevelopment]

lgtm 👍🏾

[codecov]

Codecov Report

Merging #305 (1830bf7) into main (aa6c595) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #305   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           67        67           
  Lines         1869      1869           
  Branches        73        73           
=========================================
  Hits          1869      1869           

Flag	Coverage Δ
node16	100.00% <ø> (ø)
node18	100.00% <ø> (ø)
node19	100.00% <ø> (ø)
node20	100.00% <ø> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3daf94b...1830bf7. Read the comment docs.

[github-actions]

This pull request has been automatically locked since there has not been any recent
activity after it was closed. Please open a new issue for related bugs or features. Be
sure to reference this issue.