Update dependency esbuild to v0.8.6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
esbuild	devDependencies	patch	0.8.5 -> 0.8.6

---

Release Notes

evanw/esbuild

v0.8.6

Compare Source

• Changes to TypeScript's import name = syntax

  The parsing of TypeScript's import name = syntax should now match the official TypeScript parser. Previously esbuild incorrectly allowed any kind of expression after the equals sign. Now you can only use either a sequence of identifiers separated by periods or a call to the require function with a string literal.

• Do not report warnings about require() inside try (#​512)

  This release no longer reports warnings about un-bundled calls to require() if they are within a try block statement. Presumably the try/catch statement is there to handle the potential run-time error from the unbundled require() call failing, so the potential failure is expected and not worth warning about.

• Add the --keep-names option (#​510)

  In JavaScript the name property on functions and classes defaults to a nearby identifier in the source code. These syntax forms all set the name property of the function to 'fn':

  function fn() {}
  let fn = function() {};
  obj.fn = function() {};
  fn = function() {};
  let [fn = function() {}] = [];
  let {fn = function() {}} = {};
  [fn = function() {}] = [];
  ({fn = function() {}} = {});

  However, minification renames symbols to reduce code size. That changes value of the name property for many of these cases. This is usually fine because the name property is normally only used for debugging. However, some frameworks rely on the name property for registration and binding purposes. If this is the case, you can now enable --keep-names to preserve the original name values even in minified code.

• Omit unused TypeScript import assignment aliases (#​474)

  In TypeScript, import x = y is an alias statement that works for both values and types and can reach across files. Because esbuild doesn't replicate TypeScript's type system and because esbuild converts each file from TypeScript to JavaScript independently, it's not clear to esbuild if the alias refers to a value and should be kept as JavaScript or if the alias refers to a type and should be removed.

  Previously all import aliases were kept in the generated JavaScript. This could lead to problems if the alias actually referred to a type. Now import aliases are only kept if they are used as values. This way import aliases that are only used as types will be automatically removed. This doesn't exactly match what the TypeScript compiler does in complex scenarios but it should work for many real-world cases.

• Validate that on-resolve plugins return absolute paths in the file namespace

  The default path namespace for on-resolve plugins is the file namespace. Paths in this namespace are expected to be absolute paths. This is now enforced. If the returned path is not supposed to be a file system path, you should set a namespace other than file so esbuild doesn't treat it as a file system path.

• External paths returned by a plugin do not default to the file namespace

  The file namespace is normally implied if it's not specified. However, that probably does not match the intent of the plugin for paths that have been marked as external. Such paths will now have an empty namespace instead of the namespace file. You now have to explicitly specify the file namespace in your plugin if you want it for external paths.

---

Renovate 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, check this box

---

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

[codecov]

Codecov Report

Merging #26 (e39eb95) into main (a8d0266) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines           59        59           
  Branches         5         5           
=========================================
  Hits            59        59           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

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