build(deps-dev): bump esbuild from 0.14.43 to 0.14.45

[dependabot]

Bumps esbuild from 0.14.43 to 0.14.45.

Release notes

Sourced from esbuild's releases.

v0.14.45

• Add a log message for ambiguous re-exports (#2322)

  In JavaScript, you can re-export symbols from another file using export * from './another-file'. When you do this from multiple files that export different symbols with the same name, this creates an ambiguous export which is causes that name to not be exported. This is harmless if you don't plan on using the ambiguous export name, so esbuild doesn't have a warning for this. But if you do want a warning for this (or if you want to make it an error), you can now opt-in to seeing this log message with --log-override:ambiguous-reexport=warning or --log-override:ambiguous-reexport=error. The log message looks like this:

  ▲ [WARNING] Re-export of "common" in "example.js" is ambiguous and has been removed [ambiguous-reexport]
  One definition of "common" comes from "a.js" here:
  a.js:2:11:
    2 │ export let common = 2
      ╵            ~~~~~~
  
  Another definition of "common" comes from "b.js" here:
  b.js:3:14:
    3 │ export { b as common }
      ╵               ~~~~~~
  
  

• Optimize the output of the JSON loader (#2161)

  The json loader (which is enabled by default for .json files) parses the file as JSON and generates a JavaScript file with the parsed expression as the default export. This behavior is standard and works in both node and the browser (well, as long as you use an import assertion). As an extension, esbuild also allows you to import additional top-level properties of the JSON object directly as a named export. This is beneficial for tree shaking. For example:

  import { version } from 'esbuild/package.json'
  console.log(version)

  If you bundle the above code with esbuild, you'll get something like the following:

  // node_modules/esbuild/package.json
  var version = "0.14.44";
  // example.js
  console.log(version);

  Most of the package.json file is irrelevant and has been omitted from the output due to tree shaking. The way esbuild implements this is to have the JavaScript file that's generated from the JSON look something like this with a separate exported variable for each property on the top-level object:

  // node_modules/esbuild/package.json
  export var name = "esbuild";
  export var version = "0.14.44";
  export var repository = "https://github.com/evanw/esbuild";
  export var bin = {
    esbuild: "bin/esbuild"
  };

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.14.45

• Add a log message for ambiguous re-exports (#2322)

  In JavaScript, you can re-export symbols from another file using export * from './another-file'. When you do this from multiple files that export different symbols with the same name, this creates an ambiguous export which is causes that name to not be exported. This is harmless if you don't plan on using the ambiguous export name, so esbuild doesn't have a warning for this. But if you do want a warning for this (or if you want to make it an error), you can now opt-in to seeing this log message with --log-override:ambiguous-reexport=warning or --log-override:ambiguous-reexport=error. The log message looks like this:

  ▲ [WARNING] Re-export of "common" in "example.js" is ambiguous and has been removed [ambiguous-reexport]
  One definition of "common" comes from "a.js" here:
  a.js:2:11:
    2 │ export let common = 2
      ╵            ~~~~~~
  
  Another definition of "common" comes from "b.js" here:
  b.js:3:14:
    3 │ export { b as common }
      ╵               ~~~~~~
  
  

• Optimize the output of the JSON loader (#2161)

  The json loader (which is enabled by default for .json files) parses the file as JSON and generates a JavaScript file with the parsed expression as the default export. This behavior is standard and works in both node and the browser (well, as long as you use an import assertion). As an extension, esbuild also allows you to import additional top-level properties of the JSON object directly as a named export. This is beneficial for tree shaking. For example:

  import { version } from 'esbuild/package.json'
  console.log(version)

  If you bundle the above code with esbuild, you'll get something like the following:

  // node_modules/esbuild/package.json
  var version = "0.14.44";
  // example.js
  console.log(version);

  Most of the package.json file is irrelevant and has been omitted from the output due to tree shaking. The way esbuild implements this is to have the JavaScript file that's generated from the JSON look something like this with a separate exported variable for each property on the top-level object:

  // node_modules/esbuild/package.json
  export var name = "esbuild";
  export var version = "0.14.44";
  export var repository = "https://github.com/evanw/esbuild";
  export var bin = {
    esbuild: "bin/esbuild"

... (truncated)

Commits

• dc55e16 publish 0.14.45 to npm
• d777765 document id in the release notes
• f015d27 add id to plugin tests
• 3bea172 pass the message id through to the public api
• 8b567ab enable certain log messages even when not bundling
• 3f3d716 fix #2161: optimized output for the json loader
• 4ee0aad throw when initialize gets wasmModule (#2323)
• d500061 fix #2322: a log message for ambiguous re-exports
• 4f73331 publish 0.14.44 to npm
• 538e848 update go 1.18.2 => 1.18.3
• 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)