fix(deps): update dependency @netlify/esbuild to v0.14.23

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@netlify/esbuild	0.13.6 -> 0.14.23

---

Release Notes

evanw/esbuild

v0.14.23

Compare Source

• Update feature database to indicate that node 16.14+ supports import assertions (#​2030)

  Node versions 16.14 and above now support import assertions according to these release notes. This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with --target=node16.14:

  // Original code
  import data from './package.json' assert { type: 'json' }
  console.log(data)
  
  // Old output (with --target=node16.14)
  import data from "./package.json";
  console.log(data);
  
  // New output (with --target=node16.14)
  import data from "./package.json" assert { type: "json" };
  console.log(data);

• Basic support for CSS @layer rules (#​2027)

  This adds basic parsing support for a new CSS feature called @layer that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of @layer rules:

  /* Original code */
  @​layer a {
    @​layer b {
      div {
        color: yellow;
        margin: 0.0px;
      }
    }
  }
  
  /* Old output (with --minify) */
  @​layer a{@​layer b {div {color: yellow; margin: 0px;}}}
  
  /* New output (with --minify) */
  @​layer a.b{div{color:#ff0;margin:0}}

  You can read more about @layer here:

  • Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/[@​layer](https://togithub.com/layer)
  • Motivation: https://developer.chrome.com/blog/cascade-layers/

  Note that the support added in this release is only for parsing and printing @layer rules. The bundler does not yet know about these rules and bundling with @layer may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the first instance while with every other CSS rule, the order is derived from the last instance.

v0.13.13

Compare Source

• Add more information about skipping "main" in package.json (#​1754)

  Configuring mainFields: [] breaks most npm packages since it tells esbuild to ignore the "main" field in package.json, which most npm packages use to specify their entry point. This is not a bug with esbuild because esbuild is just doing what it was told to do. However, people may do this without understanding how npm packages work, and then be confused about why it doesn't work. This release now includes additional information in the error message:

   > foo.js:1:27: error: Could not resolve "events" (use "--platform=node" when building for node)
       1 │ var EventEmitter = require('events')
         ╵                            ~~~~~~~~
     node_modules/events/package.json:20:2: note: The "main" field was ignored because the list of main fields to use is currently set to []
      20 │   "main": "./events.js",
         ╵   ~~~~~~
  

• Fix a tree-shaking bug with var exports (#​1739)

  This release fixes a bug where a variable named var exports = {} was incorrectly removed by tree-shaking (i.e. dead code elimination). The exports variable is a special variable in CommonJS modules that is automatically provided by the CommonJS runtime. CommonJS modules are transformed into something like this before being run:

  function(exports, module, require) {
    var exports = {}
  }

  So using var exports = {} should have the same effect as exports = {} because the variable exports should already be defined. However, esbuild was incorrectly overwriting the definition of the exports variable with the one provided by CommonJS. This release merges the definitions together so both are included, which fixes the bug.

• Merge adjacent CSS selector rules with duplicate content (#​1755)

  With this release, esbuild will now merge adjacent selectors when minifying if they have the same content:

  /* Original code */
  a { color: red }
  b { color: red }
  
  /* Old output (with --minify) */
  a{color:red}b{color:red}
  
  /* New output (with --minify) */
  a,b{color:red}

• Shorten top, right, bottom, left CSS property into inset when it is supported (#​1758)

  This release enables collapsing of inset related properties:

  /* Original code */
  div {
    top: 0;
    right: 0;
    bottom: 0;
    left: 0;
  }
  
  /* Output with "--minify-syntax" */
  div {
    inset: 0;
  }

  This minification rule is only enabled when inset property is supported by the target environment. Make sure to set esbuild's target setting correctly when minifying if the code will be running in an older environment (e.g. earlier than Chrome 87).

  This feature was contributed by @​sapphi-red.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.