build(deps): bump github.com/evanw/esbuild from 0.13.12 to 0.13.13

[dependabot]

Bumps github.com/evanw/esbuild from 0.13.12 to 0.13.13.

Release notes

Sourced from github.com/evanw/esbuild's releases.

v0.13.13

• 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;

... (truncated)

Changelog

Sourced from github.com/evanw/esbuild's changelog.

0.13.13

• 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 {

... (truncated)

Commits

• c09d098 publish 0.13.13 to npm
• 98fbfc1 add credit to changelog
• c153d63 Shorten "top", "right" properties into "inset" property (#1758)
• 4416658 add spack to benchmarks (not ready due to bugs)
• c5cf17b fix #1755: merge adjacent selectors with same body
• 01b65ec say if "main" is missing from main fields (#1754)
• 0441a6b make debug meta available to the entire resolver
• 74f38a3 move "main fields" logic to a separate function
• d532cf7 allow empty string for CLI string arrays
• 9235001 Add css to help text for --loader (#1744)
• 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)