build(deps-dev): Bump esbuild from 0.20.0 to 0.20.1

[dependabot]

Bumps esbuild from 0.20.0 to 0.20.1.

Release notes

Sourced from esbuild's releases.

v0.20.1

• Fix a bug with the CSS nesting transform (#3648)

  This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

  /* Original code */
  .foo {
    &:after,
    & .bar {
      color: red;
    }
  }
  /* Old output (with --supported:nesting=false) */
  .foo .bar,
  .foo .bar {
  color: red;
  }
  /* New output (with --supported:nesting=false) */
  .foo:after,
  .foo .bar {
  color: red;
  }

• Constant folding for JavaScript inequality operators (#3645)

  This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

  // Original code
  console.log(1 < 2, '🍕' > '🧀')
  // Old output (with --minify)
  console.log(1<2,"🍕">"🧀");
  // New output (with --minify)
  console.log(!0,!1);

• Better handling of __proto__ edge cases (#3651)

  JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

  // Original code
  function foo(__proto__) {
    return { __proto__: __proto__ } // Note: sets the prototype

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.1

• Fix a bug with the CSS nesting transform (#3648)

  This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

  /* Original code */
  .foo {
    &:after,
    & .bar {
      color: red;
    }
  }
  /* Old output (with --supported:nesting=false) */
  .foo .bar,
  .foo .bar {
  color: red;
  }
  /* New output (with --supported:nesting=false) */
  .foo:after,
  .foo .bar {
  color: red;
  }

• Constant folding for JavaScript inequality operators (#3645)

  This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

  // Original code
  console.log(1 < 2, '🍕' > '🧀')
  // Old output (with --minify)
  console.log(1<2,"🍕">"🧀");
  // New output (with --minify)
  console.log(!0,!1);

• Better handling of __proto__ edge cases (#3651)

  JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

  // Original code
  function foo(__proto__) {

... (truncated)

Commits

• 9f9e4f8 publish 0.20.1 to npm
• ac36537 fix #3651: handle __proto__ edge cases better
• 555db48 fix #3645: constant folding for \< > \<= >=
• 5650831 fix #3650: add a wrapper for float64 math
• d086889 fix some lints
• ad3d8c6 fix #3648: copy selectors before checking children
• a08f30d fix #3634: crash if resolving with bad source dir
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[flex-development]

lgtm 👍🏾

[flex-development]

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.