chore(deps-dev): bump esbuild from 0.10.2 to 0.12.17

Bumps esbuild from 0.10.2 to 0.12.17.

Release notes

v0.12.17
Fix a bug with private fields and logical assignment operators (#1418)

This release fixes a bug where code using private fields in combination with logical assignment operators was transformed incorrectly if the target environment supported logical assignment operators but not private fields. Since logical assignment operators are assignment operators, the entire operator must be transformed even if the operator is supported. This should now work correctly:
// Original code
class Foo {
  #x
  foo() {
    this.#x &&= 2
    this.#x ||= 2
    this.#x ??= 2
  }
}
// Old output
var _x;
class Foo {
constructor() {
__privateAdd(this, _x, void 0);
}
foo() {
this._x &&= 2;
this._x ||= 2;
this._x ??= 2;
}
}
_x = new WeakMap();
// New output
var _x, _a;
class Foo {
constructor() {
__privateAdd(this, _x, void 0);
}
foo() {
__privateGet(this, _x) && __privateSet(this, _x, 2);
__privateGet(this, _x) || __privateSet(this, _x, 2);
__privateGet(this, _x) ?? __privateSet(this, _x, 2);
}
}
_x = new WeakMap();
Fix a hoisting bug in the bundler (#1455)

This release fixes a bug where variables declared using var inside of top-level for loop initializers were not hoisted inside lazily-initialized ES modules (such as those that are generated when bundling code that loads an ES module using require). This meant that hoisted function declarations incorrectly didn't have access to these loop variables:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.12.17
Fix a bug with private fields and logical assignment operators (#1418)

This release fixes a bug where code using private fields in combination with logical assignment operators was transformed incorrectly if the target environment supported logical assignment operators but not private fields. Since logical assignment operators are assignment operators, the entire operator must be transformed even if the operator is supported. This should now work correctly:
// Original code
class Foo {
  #x
  foo() {
    this.#x &&= 2
    this.#x ||= 2
    this.#x ??= 2
  }
}
// Old output
var _x;
class Foo {
constructor() {
__privateAdd(this, _x, void 0);
}
foo() {
this._x &&= 2;
this._x ||= 2;
this._x ??= 2;
}
}
_x = new WeakMap();
// New output
var _x, _a;
class Foo {
constructor() {
__privateAdd(this, _x, void 0);
}
foo() {
__privateGet(this, _x) && __privateSet(this, _x, 2);
__privateGet(this, _x) || __privateSet(this, _x, 2);
__privateGet(this, _x) ?? __privateSet(this, _x, 2);
}
}
_x = new WeakMap();
Fix a hoisting bug in the bundler (#1455)

This release fixes a bug where variables declared using var inside of top-level for loop initializers were not hoisted inside lazily-initialized ES modules (such as those that are generated when bundling code that loads an ES module using require). This meant that hoisted function declarations incorrectly didn't have access to these loop variables:

... (truncated)

Commits

fe3659e publish 0.12.17 to npm
f95072d fix #1424: always generate private method names
db673c3 release notes for #1449
4267bef Abort esbuild if stdin is closed when serving (#1449)
748d8b4 fix #1418: private fields and logical assignment
bb3a4cd fix #1455: bundler hoisting bug with var+for loops
773f15f publish 0.12.16 to npm
d2a4f36 Consider \ and / to be the same in file paths (#1472)
025d64e fix #1466: paths with "node:" prefix are external
6d35ea9 fix #1462: avoid worker_threads in node <v12.17.0
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 will not automatically merge this PR because this dependency is pre-1.0.0.

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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

egoist / docup

chore(deps-dev): bump esbuild from 0.10.2 to 0.12.17 #255

v0.12.17

0.12.17