chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	16.2.1 -> 16.2.3
@typescript-eslint/eslint-plugin	5.14.0 -> 5.15.0
@typescript-eslint/parser	5.14.0 -> 5.15.0
esbuild	0.14.25 -> 0.14.27
fetch-blob	3.1.4 -> 3.1.5
lint-staged	12.3.5 -> 12.3.7
prettier (source)	2.5.1 -> 2.6.0
undici (source)	^4.15.1 -> ^4.16.0

---

Release Notes

conventional-changelog/commitlint

v16.2.3

Compare Source

Note: Version bump only for package @​commitlint/cli

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

v5.15.0

Compare Source

Features

• parser: add parserOptions.emitDecoratorMetadata (#​4646) (e3dd343)

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

v5.15.0

Compare Source

Features

• parser: add parserOptions.emitDecoratorMetadata (#​4646) (e3dd343)

evanw/esbuild

v0.14.27

Compare Source

• Avoid generating an enumerable default import for CommonJS files in Babel mode (#​2097)

  Importing a CommonJS module into an ES module can be done in two different ways. In node mode the default import is always set to module.exports, while in Babel mode the default import passes through to module.exports.default instead. Node mode is triggered when the importing file ends in .mjs, has type: "module" in its package.json file, or the imported module does not have a __esModule marker.

  Previously esbuild always created the forwarding default import in Babel mode, even if module.exports had no property called default. This was problematic because the getter named default still showed up as a property on the imported namespace object, and could potentially interfere with code that iterated over the properties of the imported namespace object. With this release the getter named default will now only be added in Babel mode if the default property exists at the time of the import.

• Fix a circular import edge case regarding ESM-to-CommonJS conversion (#​1894, #​2059)

  This fixes a regression that was introduced in version 0.14.5 of esbuild. Ever since that version, esbuild now creates two separate export objects when you convert an ES module file into a CommonJS module: one for ES modules and one for CommonJS modules. The one for CommonJS modules is written to module.exports and exported from the file, and the one for ES modules is internal and can be accessed by bundling code that imports the entry point (for example, the entry point might import itself to be able to inspect its own exports).

  The reason for these two separate export objects is that CommonJS modules are supposed to see a special export called __esModule which indicates that the module used to be an ES module, while ES modules are not supposed to see any automatically-added export named __esModule. This matters for real-world code both because people sometimes iterate over the properties of ES module export namespace objects and because some people write ES module code containing their own exports named __esModule that they expect other ES module code to be able to read.

  However, this change to split exports into two separate objects broke ES module re-exports in the edge case where the imported module is involved in an import cycle. This happened because the CommonJS module.exports object was no longer mutated as exports were added. Instead it was being initialized at the end of the generated file after the import statements to other modules (which are converted into require() calls). This release changes module.exports initialization to happen earlier in the file and then double-writes further exports to both the ES module and CommonJS module export objects.

  This fix was contributed by @​indutny.

v0.14.26

Compare Source

• Fix a tree shaking regression regarding var declarations (#​2080, #​2085, #​2098, #​2099)

  Version 0.14.8 of esbuild enabled removal of duplicate function declarations when minification is enabled (see #​610):

  // Original code
  function x() { return 1 }
  console.log(x())
  function x() { return 2 }
  
  // Output (with --minify-syntax)
  console.log(x());
  function x() {
    return 2;
  }

  This transformation is safe because function declarations are "hoisted" in JavaScript, which means they are all done first before any other code is evaluted. This means the last function declaration will overwrite all previous function declarations with the same name.

  However, this introduced an unintentional regression for var declarations in which all but the last declaration was dropped if tree-shaking was enabled. This only happens for top-level var declarations that re-declare the same variable multiple times. This regression has now been fixed:

  // Original code
  var x = 1
  console.log(x)
  var x = 2
  
  // Old output (with --tree-shaking=true)
  console.log(x);
  var x = 2;
  
  // New output (with --tree-shaking=true)
  var x = 1;
  console.log(x);
  var x = 2;

  This case now has test coverage.

• Add support for parsing "instantiation expressions" from TypeScript 4.7 (#​2038)

  The upcoming version of TypeScript now lets you specify <...> type parameters on a JavaScript identifier without using a call expression:

  const ErrorMap = Map<string, Error>;  // new () => Map<string, Error>
  const errorMap = new ErrorMap();  // Map<string, Error>

  With this release, esbuild can now parse these new type annotations. This feature was contributed by @​g-plane.

• Avoid new Function in esbuild's library code (#​2081)

  Some JavaScript environments such as Cloudflare Workers or Deno Deploy don't allow new Function because they disallow dynamic JavaScript evaluation. Previously esbuild's WebAssembly-based library used this to construct the WebAssembly worker function. With this release, the code is now inlined without using new Function so it will be able to run even when this restriction is in place.

• Drop superfluous __name() calls (#​2062)

  When the --keep-names option is specified, esbuild inserts calls to a __name helper function to ensure that the .name property on function and class objects remains consistent even if the function or class name is renamed to avoid a name collision or because name minification is enabled. With this release, esbuild will now try to omit these calls to the __name helper function when the name of the function or class object was not renamed during the linking process after all:

  // Original code
  import { foo as foo1 } from 'data:text/javascript,export function foo() { return "foo1" }'
  import { foo as foo2 } from 'data:text/javascript,export function foo() { return "foo2" }'
  console.log(foo1.name, foo2.name)
  
  // Old output (with --bundle --keep-names)
  (() => {
    var __defProp = Object.defineProperty;
    var __name = (target, value) => __defProp(target, "name", { value, configurable: true });
    function foo() {
      return "foo1";
    }
    __name(foo, "foo");
    function foo2() {
      return "foo2";
    }
    __name(foo2, "foo");
    console.log(foo.name, foo2.name);
  })();
  
  // New output (with --bundle --keep-names)
  (() => {
    var __defProp = Object.defineProperty;
    var __name = (target, value) => __defProp(target, "name", { value, configurable: true });
    function foo() {
      return "foo1";
    }
    function foo2() {
      return "foo2";
    }
    __name(foo2, "foo");
    console.log(foo.name, foo2.name);
  })();

  Notice how one of the calls to __name is now no longer printed. This change was contributed by @​indutny.

node-fetch/fetch-blob

v3.1.5

Compare Source

What's Changed

• fix: avoid reading files when the size is empty by @​jimmywarting in https://github.com/node-fetch/fetch-blob/pull/134

Full Changelog: node-fetch/fetch-blob@v3.1.4...v3.1.5

okonet/lint-staged

v12.3.7

Compare Source

Bug Fixes

• improve renderer logic for --silent and FORCE_COLOR settings (d327873)

v12.3.6

Compare Source

Bug Fixes

• kill other running tasks on failure (#​1117) (34fe319)

prettier/prettier

v2.6.0

Compare Source

diff

🔗 Release Notes

nodejs/undici

v4.16.0

Compare Source

What's Changed

• fix: remove hash from intercept dispatch key by @​galvez in https://github.com/nodejs/undici/pull/1273
• feat(mock): allow matching the complete header list by @​panva in https://github.com/nodejs/undici/pull/1275
• build: fix lint errors and introduce CI check by @​JustinBeckwith in https://github.com/nodejs/undici/pull/1277
• remove istanbule ignore and add test for bad upgrade by @​is2ei in https://github.com/nodejs/undici/pull/1279
• docs: document the behavior of consuming body twice by @​is2ei in https://github.com/nodejs/undici/pull/1281
• chore: update undici-fetch to fair benchmarks by @​RafaelGSS in https://github.com/nodejs/undici/pull/1283
• chore: fix import readablestream by @​RafaelGSS in https://github.com/nodejs/undici/pull/1284
• tests: fix CI failure by @​KhafraDev in https://github.com/nodejs/undici/pull/1286
• docs: add examples to fetch/request by @​RafaelGSS in https://github.com/nodejs/undici/pull/1287
• chore: fix duplicated error import in test/agent.js by @​is2ei in https://github.com/nodejs/undici/pull/1288
• chore: html reporter by @​is2ei in https://github.com/nodejs/undici/pull/1289
• fix: Do not use WeakRef on mocks. by @​ShogunPanda in https://github.com/nodejs/undici/pull/1290

New Contributors

• @​galvez made their first contribution in https://github.com/nodejs/undici/pull/1273
• @​panva made their first contribution in https://github.com/nodejs/undici/pull/1275
• @​JustinBeckwith made their first contribution in https://github.com/nodejs/undici/pull/1277

Full Changelog: nodejs/undici@v4.15.1...v4.16.0

---

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 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, click this checkbox.

---

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

[codecov]

Codecov Report

Merging #26 (acd3202) into trunk (0717e66) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            trunk      #26   +/-   ##
=======================================
  Coverage   95.41%   95.41%           
=======================================
  Files           1        1           
  Lines         109      109           
  Branches       21       21           
=======================================
  Hits          104      104           
  Misses          5        5           

[github-actions]

🎉 This PR is included in version 2.0.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀