Update all dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@​gauntface/logger	3.0.69 -> 3.0.70
@typescript-eslint/eslint-plugin	5.47.0 -> 5.47.1
@typescript-eslint/parser	5.47.0 -> 5.47.1
esbuild	0.16.10 -> 0.16.11

---

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.47.1

Compare Source

Bug Fixes

• ast-spec: correct some incorrect ast types (#​6257) (0f3f645)
• eslint-plugin: [member-ordering] correctly invert optionalityOrder (#​6256) (ccd45d4)

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.47.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

evanw/esbuild

v0.16.11

Compare Source

• Avoid a syntax error in the presence of direct eval (#​2761)

  The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

  // Original code
  if (true) {
    function foo() {}
    console.log(!!foo)
    foo = null
    console.log(!!foo)
  }
  console.log(!!foo)
  
  // Transformed code
  if (true) {
    let foo2 = function() {
    };
    var foo = foo2;
    console.log(!!foo2);
    foo2 = null;
    console.log(!!foo2);
  }
  console.log(!!foo);

  In the above example, the original code should print true false true because it's not run in strict mode (it doesn't contain "use strict" and is not an ES module). The code that esbuild generates has been transformed such that it prints true false true regardless of whether it's run in strict mode or not.

  However, this transformation is impossible if the code contains direct eval because direct eval "poisons" all containing scopes by preventing anything in those scopes from being renamed. That prevents esbuild from splitting up accesses to foo into two separate variables with different names. Previously esbuild still did this transformation but with two variables both named foo, which is a syntax error. With this release esbuild will now skip doing this transformation when direct eval is present to avoid generating code with a syntax error. This means that the generated code may no longer behave as intended since the behavior depends on the run-time strict mode setting instead of the strict mode setting present in the original source code. To fix this problem, you will need to remove the use of direct eval.

• Fix a bundling scenario involving multiple symlinks (#​2773, #​2774)

  This release contains a fix for a bundling scenario involving an import path where multiple path segments are symlinks. Previously esbuild was unable to resolve certain import paths in this scenario, but these import paths should now work starting with this release. This fix was contributed by @​onebytegone.

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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