typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.61.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5601v5610-2023-07-03)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.1...v5.61.0)
##### Features
- **eslint-plugin:** \[ban-types] ban types in extends and implements ([#7129](https://togithub.com/typescript-eslint/typescript-eslint/issues/7129)) ([997783f](https://togithub.com/typescript-eslint/typescript-eslint/commit/997783ff108ca18af709667ef3fdfa7134a8eefe))
- use graphemer instead of grapheme-splitter ([#7069](https://togithub.com/typescript-eslint/typescript-eslint/issues/7069)) ([faea3ff](https://togithub.com/typescript-eslint/typescript-eslint/commit/faea3ff8b4d750974c41262b44db314f20d0c99c))
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
#### [5.60.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) (2023-06-26)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
### [`v5.60.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5601-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5600v5601-2023-06-26)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
### [`v5.60.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5600-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55911v5600-2023-06-19)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0)
##### Features
- **eslint-plugin:** \[restrict-plus-operands] add allow\* options ([#6161](https://togithub.com/typescript-eslint/typescript-eslint/issues/6161)) ([def09f8](https://togithub.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0))
#### [5.59.11](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) (2023-06-12)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.10](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) (2023-06-12)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.9](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) (2023-06-05)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.8](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.7...v5.59.8) (2023-05-29)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.6...v5.59.7) (2023-05-22)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.5...v5.59.6) (2023-05-15)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.4...v5.59.5) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.3...v5.59.4) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.2...v5.59.3) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2) (2023-05-01)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.59.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) (2023-04-24)
##### Bug Fixes
- **eslint-plugin:** \[prefer-regexp-exec] skip malformed regexes ([#6935](https://togithub.com/typescript-eslint/typescript-eslint/issues/6935)) ([05ed60e](https://togithub.com/typescript-eslint/typescript-eslint/commit/05ed60e25f1de9d1bb83d56c81a349130960bec8))
- **eslint-plugin:** \[unified-signatures] no parameters function ([#6940](https://togithub.com/typescript-eslint/typescript-eslint/issues/6940)) ([2970861](https://togithub.com/typescript-eslint/typescript-eslint/commit/297086154acc568a0ae8eb41c8977b7a7ba4e0ed))
### [`v5.59.11`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#55911-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55910v55911-2023-06-12)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
### [`v5.59.10`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#55910-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5599v55910-2023-06-12)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
### [`v5.59.9`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5599-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5598v5599-2023-06-05)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.61.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5601v5610-2023-07-03)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.1...v5.61.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
#### [5.60.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) (2023-06-26)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
### [`v5.60.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5601-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5600v5601-2023-06-26)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
### [`v5.60.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5600-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55911v5600-2023-06-19)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.11](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) (2023-06-12)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.10](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) (2023-06-12)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.9](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) (2023-06-05)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.8](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.7...v5.59.8) (2023-05-29)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.6...v5.59.7) (2023-05-22)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.5...v5.59.6) (2023-05-15)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.4...v5.59.5) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.3...v5.59.4) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.2...v5.59.3) (2023-05-08)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2) (2023-05-01)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.59.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) (2023-04-24)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.59.11`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#55911-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55910v55911-2023-06-12)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.59.10`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#55910-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5599v55910-2023-06-12)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.59.9`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5599-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5598v5599-2023-06-05)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
evanw/esbuild (esbuild)
### [`v0.18.11`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01811)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.10...v0.18.11)
- Fix a TypeScript code generation edge case ([#3199](https://togithub.com/evanw/esbuild/issues/3199))
This release fixes a regression in version 0.18.4 where using a TypeScript `namespace` that exports a `class` declaration combined with `--keep-names` and a `--target` of `es2021` or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to `X2._Y` vs. `X2.Y`):
```ts
// Original code
// Old output (with --keep-names --target=es2021)
var X;
((X2) => {
const _Y = class _Y {
};
__name(_Y, "Y");
let Y = _Y;
X2._Y = _Y;
})(X || (X = {}));
// New output (with --keep-names --target=es2021)
var X;
((X2) => {
const _Y = class _Y {
};
__name(_Y, "Y");
let Y = _Y;
X2.Y = _Y;
})(X || (X = {}));
```
### [`v0.18.10`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01810)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.9...v0.18.10)
- Fix a tree-shaking bug that removed side effects ([#3195](https://togithub.com/evanw/esbuild/issues/3195))
This fixes a regression in version 0.18.4 where combining `--minify-syntax` with `--keep-names` could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because `--keep-names` generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then `--minify-syntax` could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.
- Fix an incorrect warning about CSS nesting ([#3197](https://togithub.com/evanw/esbuild/issues/3197))
A warning is currently generated when transforming nested CSS to a browser that doesn't support `:is()` because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as `@top-left` within `@page`. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.
### [`v0.18.9`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0189)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.8...v0.18.9)
- Fix `await using` declarations inside `async` generator functions
I forgot about the new `await using` declarations when implementing lowering for `async` generator functions in the previous release. This change fixes the transformation of `await using` declarations when they are inside lowered `async` generator functions:
```js
// Original code
async function* foo() {
await using x = await y
}
// Old output (with --supported:async-generator=false)
function foo() {
return __asyncGenerator(this, null, function* () {
await using x = yield new __await(y);
});
}
// New output (with --supported:async-generator=false)
function foo() {
return __asyncGenerator(this, null, function* () {
var _stack = [];
try {
const x = __using(_stack, yield new __await(y), true);
} catch (_) {
var _error = _, _hasError = true;
} finally {
var _promise = __callDispose(_stack, _error, _hasError);
_promise && (yield new __await(_promise));
}
});
}
```
- Insert some prefixed CSS properties when appropriate ([#3122](https://togithub.com/evanw/esbuild/issues/3122))
With this release, esbuild will now insert prefixed CSS properties in certain cases when the `target` setting includes browsers that require a certain prefix. This is currently done for the following properties:
- `appearance: *;` => `-webkit-appearance: *; -moz-appearance: *;`
- `backdrop-filter: *;` => `-webkit-backdrop-filter: *;`
- `background-clip: text` => `-webkit-background-clip: text;`
- `box-decoration-break: *;` => `-webkit-box-decoration-break: *;`
- `clip-path: *;` => `-webkit-clip-path: *;`
- `font-kerning: *;` => `-webkit-font-kerning: *;`
- `hyphens: *;` => `-webkit-hyphens: *;`
- `initial-letter: *;` => `-webkit-initial-letter: *;`
- `mask-image: *;` => `-webkit-mask-image: *;`
- `mask-origin: *;` => `-webkit-mask-origin: *;`
- `mask-position: *;` => `-webkit-mask-position: *;`
- `mask-repeat: *;` => `-webkit-mask-repeat: *;`
- `mask-size: *;` => `-webkit-mask-size: *;`
- `position: sticky;` => `position: -webkit-sticky;`
- `print-color-adjust: *;` => `-webkit-print-color-adjust: *;`
- `tab-size: *;` => `-moz-tab-size: *; -o-tab-size: *;`
- `text-decoration-color: *;` => `-webkit-text-decoration-color: *; -moz-text-decoration-color: *;`
- `text-decoration-line: *;` => `-webkit-text-decoration-line: *; -moz-text-decoration-line: *;`
- `text-decoration-skip: *;` => `-webkit-text-decoration-skip: *;`
- `text-emphasis-color: *;` => `-webkit-text-emphasis-color: *;`
- `text-emphasis-position: *;` => `-webkit-text-emphasis-position: *;`
- `text-emphasis-style: *;` => `-webkit-text-emphasis-style: *;`
- `text-orientation: *;` => `-webkit-text-orientation: *;`
- `text-size-adjust: *;` => `-webkit-text-size-adjust: *; -ms-text-size-adjust: *;`
- `user-select: *;` => `-webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;`
Here is an example:
```css
/* Original code */
div {
mask-image: url(x.png);
}
/* Old output (with --target=chrome99) */
div {
mask-image: url(x.png);
}
/* New output (with --target=chrome99) */
div {
-webkit-mask-image: url(x.png);
mask-image: url(x.png);
}
```
Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate.
- Fix an obscure identifier minification bug ([#2809](https://togithub.com/evanw/esbuild/issues/2809))
Function declarations in nested scopes behave differently depending on whether or not `"use strict"` is present. To avoid generating code that behaves differently depending on whether strict mode is enabled or not, esbuild transforms nested function declarations into variable declarations. However, there was a bug where the generated variable name was not being recorded as declared internally, which meant that it wasn't being renamed correctly by the minifier and could cause a name collision. This bug has been fixed:
```js
// Original code
const n = ''
for (let i of [0,1]) {
function f () {}
}
// Old output (with --minify-identifiers --format=esm)
const f = "";
for (let o of [0, 1]) {
let n = function() {
};
var f = n;
}
// New output (with --minify-identifiers --format=esm)
const f = "";
for (let o of [0, 1]) {
let n = function() {
};
var t = n;
}
```
- Fix a bug in esbuild's compatibility table script ([#3179](https://togithub.com/evanw/esbuild/pull/3179))
Setting esbuild's `target` to a specific JavaScript engine tells esbuild to use the JavaScript syntax feature compatibility data from https://kangax.github.io/compat-table/es6/ for that engine to determine which syntax features to allow. However, esbuild's script that builds this internal compatibility table had a bug that incorrectly ignores tests for engines that still have outstanding implementation bugs which were never fixed. This change fixes this bug with the script.
The only case where this changed the information in esbuild's internal compatibility table is that the `hermes` target is marked as no longer supporting destructuring. This is because there is a failing destructuring-related test for Hermes on https://kangax.github.io/compat-table/es6/. If you want to use destructuring with Hermes anyway, you can pass `--supported:destructuring=true` to esbuild to override the `hermes` target and force esbuild to accept this syntax.
This fix was contributed by [@ArrayZoneYour](https://togithub.com/ArrayZoneYour).
### [`v0.18.8`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0188)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.7...v0.18.8)
- Implement transforming `async` generator functions ([#2780](https://togithub.com/evanw/esbuild/issues/2780))
With this release, esbuild will now transform `async` generator functions into normal generator functions when the configured target environment doesn't support them. These functions behave similar to normal generator functions except that they use the `Symbol.asyncIterator` interface instead of the `Symbol.iterator` interface and the iteration methods return promises. Here's an example (helper functions are omitted):
```js
// Original code
async function* foo() {
yield Promise.resolve(1)
await new Promise(r => setTimeout(r, 100))
yield *[Promise.resolve(2)]
}
async function bar() {
for await (const x of foo()) {
console.log(x)
}
}
bar()
// New output (with --target=es6)
function foo() {
return __asyncGenerator(this, null, function* () {
yield Promise.resolve(1);
yield new __await(new Promise((r) => setTimeout(r, 100)));
yield* __yieldStar([Promise.resolve(2)]);
});
}
function bar() {
return __async(this, null, function* () {
try {
for (var iter = __forAwait(foo()), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
const x = temp.value;
console.log(x);
}
} catch (temp) {
error = [temp];
} finally {
try {
more && (temp = iter.return) && (yield temp.call(iter));
} finally {
if (error)
throw error[0];
}
}
});
}
bar();
```
This is an older feature that was added to JavaScript in ES2018 but I didn't implement the transformation then because it's a rarely-used feature. Note that esbuild already added support for transforming `for await` loops (the other part of the [asynchronous iteration proposal](https://togithub.com/tc39/proposal-async-iteration)) a year ago, so support for asynchronous iteration should now be complete.
I have never used this feature myself and code that uses this feature is hard to come by, so this transformation has not yet been tested on real-world code. If you do write code that uses this feature, please let me know if esbuild's `async` generator transformation doesn't work with your code.
### [`v0.18.7`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0187)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.6...v0.18.7)
- Add support for `using` declarations in TypeScript 5.2+ ([#3191](https://togithub.com/evanw/esbuild/issues/3191))
TypeScript 5.2 (due to be released in August of 2023) will introduce `using` declarations, which will allow you to automatically dispose of the declared resources when leaving the current scope. You can read the [TypeScript PR for this feature](https://togithub.com/microsoft/TypeScript/pull/54505) for more information. This release of esbuild adds support for transforming this syntax to target environments without support for `using` declarations (which is currently all targets other than `esnext`). Here's an example (helper functions are omitted):
```js
// Original code
class Foo {
[Symbol.dispose]() {
console.log('cleanup')
}
}
using foo = new Foo;
foo.bar();
// New output (with --target=es6)
var _stack = [];
try {
var Foo = class {
[Symbol.dispose]() {
console.log("cleanup");
}
};
var foo = __using(_stack, new Foo());
foo.bar();
} catch (_) {
var _error = _, _hasError = true;
} finally {
__callDispose(_stack, _error, _hasError);
}
```
The injected helper functions ensure that the method named `Symbol.dispose` is called on `new Foo` when control exits the scope. Note that as with all new JavaScript APIs, you'll need to polyfill `Symbol.dispose` if it's not present before you use it. This is not something that esbuild does for you because esbuild only handles syntax, not APIs. Polyfilling it can be done with something like this:
```js
Symbol.dispose ||= Symbol('Symbol.dispose')
```
This feature also introduces `await using` declarations which are like `using` declarations but they call `await` on the disposal method (not on the initializer). Here's an example (helper functions are omitted):
```js
// Original code
class Foo {
async [Symbol.asyncDispose]() {
await new Promise(done => {
setTimeout(done, 1000)
})
console.log('cleanup')
}
}
await using foo = new Foo;
foo.bar();
// New output (with --target=es2022)
var _stack = [];
try {
var Foo = class {
async [Symbol.asyncDispose]() {
await new Promise((done) => {
setTimeout(done, 1e3);
});
console.log("cleanup");
}
};
var foo = __using(_stack, new Foo(), true);
foo.bar();
} catch (_) {
var _error = _, _hasError = true;
} finally {
var _promise = __callDispose(_stack, _error, _hasError);
_promise && await _promise;
}
```
The injected helper functions ensure that the method named `Symbol.asyncDispose` is called on `new Foo` when control exits the scope, and that the returned promise is awaited. Similarly to `Symbol.dispose`, you'll also need to polyfill `Symbol.asyncDispose` before you use it.
- Add a `--line-limit=` flag to limit line length ([#3170](https://togithub.com/evanw/esbuild/issues/3170))
Long lines are common in minified code. However, many tools and text editors can't handle long lines. This release introduces the `--line-limit=` flag to tell esbuild to wrap lines longer than the provided number of bytes. For example, `--line-limit=80` tells esbuild to insert a newline soon after a given line reaches 80 bytes in length. This setting applies to both JavaScript and CSS, and works even when minification is disabled. Note that turning this setting on will make your files bigger, as the extra newlines take up additional space in the file (even after gzip compression).
### [`v0.18.6`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0186)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.5...v0.18.6)
- Fix tree-shaking of classes with decorators ([#3164](https://togithub.com/evanw/esbuild/issues/3164))
This release fixes a bug where esbuild incorrectly allowed tree-shaking on classes with decorators. Each decorator is a function call, so classes with decorators must never be tree-shaken. This bug was a regression that was unintentionally introduced in version 0.18.2 by the change that enabled tree-shaking of lowered private fields. Previously decorators were always lowered, and esbuild always considered the automatically-generated decorator code to be a side effect. But this is no longer the case now that esbuild analyzes side effects using the AST before lowering takes place. This bug was fixed by considering any decorator a side effect.
- Fix a minification bug involving function expressions ([#3125](https://togithub.com/evanw/esbuild/issues/3125))
When minification is enabled, esbuild does limited inlining of `const` symbols at the top of a scope. This release fixes a bug where inlineable symbols were incorrectly removed assuming that they were inlined. They may not be inlined in cases where they were referenced by earlier constants in the body of a function expression. The declarations involved in these edge cases are now kept instead of being removed:
```js
// Original code
{
const fn = () => foo
const foo = 123
console.log(fn)
}
// Old output (with --minify-syntax)
console.log((() => foo)());
// New output (with --minify-syntax)
{
const fn = () => foo, foo = 123;
console.log(fn);
}
```
### [`v0.18.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0185)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.4...v0.18.5)
- Implement auto accessors ([#3009](https://togithub.com/evanw/esbuild/issues/3009))
This release implements the new auto-accessor syntax from the upcoming [JavaScript decorators proposal](https://togithub.com/tc39/proposal-decorators). The auto-accessor syntax looks like this:
```js
class Foo {
accessor foo;
static accessor bar;
}
new Foo().foo = Foo.bar;
```
This syntax is not yet a part of JavaScript but it was [added to TypeScript in version 4.9](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/#auto-accessors-in-classes). More information about this feature can be found in [microsoft/TypeScript#49705](https://togithub.com/microsoft/TypeScript/pull/49705). Auto-accessors will be transformed if the target is set to something other than `esnext`:
```js
// Output (with --target=esnext)
class Foo {
accessor foo;
static accessor bar;
}
new Foo().foo = Foo.bar;
// Output (with --target=es2022)
class Foo {
#foo;
get foo() {
return this.#foo;
}
set foo(_) {
this.#foo = _;
}
static #bar;
static get bar() {
return this.#bar;
}
static set bar(_) {
this.#bar = _;
}
}
new Foo().foo = Foo.bar;
// Output (with --target=es2021)
var _foo, _bar;
class Foo {
constructor() {
__privateAdd(this, _foo, void 0);
}
get foo() {
return __privateGet(this, _foo);
}
set foo(_) {
__privateSet(this, _foo, _);
}
static get bar() {
return __privateGet(this, _bar);
}
static set bar(_) {
__privateSet(this, _bar, _);
}
}
_foo = new WeakMap();
_bar = new WeakMap();
__privateAdd(Foo, _bar, void 0);
new Foo().foo = Foo.bar;
```
You can also now use auto-accessors with esbuild's TypeScript experimental decorator transformation, which should behave the same as decorating the underlying getter/setter pair.
**Please keep in mind that this syntax is not yet part of JavaScript.** This release enables auto-accessors in `.js` files with the expectation that it will be a part of JavaScript soon. However, esbuild may change or remove this feature in the future if JavaScript ends up changing or removing this feature. Use this feature with caution for now.
- Pass through JavaScript decorators ([#104](https://togithub.com/evanw/esbuild/issues/104))
In this release, esbuild now parses decorators from the upcoming [JavaScript decorators proposal](https://togithub.com/tc39/proposal-decorators) and passes them through to the output unmodified (as long as the language target is set to `esnext`). Transforming JavaScript decorators to environments that don't support them has not been implemented yet. The only decorator transform that esbuild currently implements is still the TypeScript experimental decorator transform, which only works in `.ts` files and which requires `"experimentalDecorators": true` in your `tsconfig.json` file.
- Static fields with assign semantics now use static blocks if possible
Setting `useDefineForClassFields` to false in TypeScript requires rewriting class fields to assignment statements. Previously this was done by removing the field from the class body and adding an assignment statement after the class declaration. However, this also caused any private fields to also be lowered by necessity (in case a field initializer uses a private symbol, either directly or indirectly). This release changes this transform to use an inline static block if it's supported, which avoids needing to lower private fields in this scenario:
```js
// Original code
class Test {
static #foo = 123
static bar = this.#foo
}
// Old output (with useDefineForClassFields=false)
var _foo;
const _Test = class _Test {
};
_foo = new WeakMap();
__privateAdd(_Test, _foo, 123);
_Test.bar = __privateGet(_Test, _foo);
let Test = _Test;
// New output (with useDefineForClassFields=false)
class Test {
static #foo = 123;
static {
this.bar = this.#foo;
}
}
```
- Fix TypeScript experimental decorators combined with `--mangle-props` ([#3177](https://togithub.com/evanw/esbuild/issues/3177))
Previously using TypeScript experimental decorators combined with the `--mangle-props` setting could result in a crash, as the experimental decorator transform was not expecting a mangled property as a class member. This release fixes the crash so you can now combine both of these features together safely.
### [`v0.18.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0184)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.3...v0.18.4)
- Bundling no longer unnecessarily transforms class syntax ([#1360](https://togithub.com/evanw/esbuild/issues/1360), [#1328](https://togithub.com/evanw/esbuild/issues/1328), [#1524](https://togithub.com/evanw/esbuild/issues/1524), [#2416](https://togithub.com/evanw/esbuild/issues/2416))
When bundling, esbuild automatically converts top-level class statements to class expressions. Previously this conversion had the unfortunate side-effect of also transforming certain other class-related syntax features to avoid correctness issues when the references to the class name within the class body. This conversion has been reworked to avoid doing this:
```js
// Original code
export class Foo {
static foo = () => Foo
}
// Old output (with --bundle)
var _Foo = class {
};
var Foo = _Foo;
__publicField(Foo, "foo", () => _Foo);
// New output (with --bundle)
var Foo = class _Foo {
static foo = () => _Foo;
};
```
This conversion process is very complicated and has many edge cases (including interactions with static fields, static blocks, private class properties, and TypeScript experimental decorators). It should already be pretty robust but a change like this may introduce new unintentional behavior. Please report any issues with this upgrade on the esbuild bug tracker.
You may be wondering why esbuild needs to do this at all. One reason to do this is that esbuild's bundler sometimes needs to lazily-evaluate a module. For example, a module may end up being both the target of a dynamic `import()` call and a static `import` statement. Lazy module evaluation is done by wrapping the top-level module code in a closure. To avoid a performance hit for static `import` statements, esbuild stores top-level exported symbols outside of the closure and references them directly instead of indirectly.
Another reason to do this is that multiple JavaScript VMs have had and continue to have performance issues with TDZ (i.e. "temporal dead zone") checks. These checks validate that a let, or const, or class symbol isn't used before it's initialized. Here are two issues with well-known VMs:
- V8: https://bugs.chromium.org/p/v8/issues/detail?id=13723 (10% slowdown)
- JavaScriptCore: https://bugs.webkit.org/show_bug.cgi?id=199866 (1,000% slowdown!)
JavaScriptCore had a severe performance issue as their TDZ implementation had time complexity that was quadratic in the number of variables needing TDZ checks in the same scope (with the top-level scope typically being the worst offender). V8 has ongoing issues with TDZ checks being present throughout the code their JIT generates even when they have already been checked earlier in the same function or when the function in question has already been run (so the checks have already happened).
Due to esbuild's parallel architecture, esbuild both a) needs to convert class statements into class expressions during parsing and b) doesn't yet know whether this module will need to be lazily-evaluated or not in the parser. So esbuild always does this conversion during bundling in case it's needed for correctness (and also to avoid potentially catastrophic performance issues due to bundling creating a large scope with many TDZ variables).
- Enforce TDZ errors in computed class property keys ([#2045](https://togithub.com/evanw/esbuild/issues/2045))
JavaScript allows class property keys to be generated at run-time using code, like this:
```js
class Foo {
static foo = 'foo'
static [Foo.foo + '2'] = 2
}
```
Previously esbuild treated references to the containing class name within computed property keys as a reference to the partially-initialized class object. That meant code that attempted to reference properties of the class object (such as the code above) would get back `undefined` instead of throwing an error.
This release rewrites references to the containing class name within computed property keys into code that always throws an error at run-time, which is how this JavaScript code is supposed to work. Code that does this will now also generate a warning. You should never write code like this, but it now should be more obvious when incorrect code like this is written.
- Fix an issue with experimental decorators and static fields ([#2629](https://togithub.com/evanw/esbuild/issues/2629))
This release also fixes a bug regarding TypeScript experimental decorators and static class fields which reference the enclosing class name in their initializer. This affected top-level classes when bundling was enabled. Previously code that does this could crash because the class name wasn't initialized yet. This case should now be handled correctly:
```ts
// Original code
class Foo {
@someDecorator
static foo = 'foo'
static bar = Foo.foo.length
}
// Old output
const _Foo = class {
static foo = "foo";
static bar = _Foo.foo.length;
};
let Foo = _Foo;
__decorateClass([
someDecorator
], Foo, "foo", 2);
// New output
const _Foo = class _Foo {
static foo = "foo";
static bar = _Foo.foo.length;
};
__decorateClass([
someDecorator
], _Foo, "foo", 2);
let Foo = _Foo;
```
- Fix a minification regression with negative numeric properties ([#3169](https://togithub.com/evanw/esbuild/issues/3169))
Version 0.18.0 introduced a regression where computed properties with negative numbers were incorrectly shortened into a non-computed property when minification was enabled. This regression has been fixed:
```js
// Original code
x = {
[1]: 1,
[-1]: -1,
[NaN]: NaN,
[Infinity]: Infinity,
[-Infinity]: -Infinity,
}
// Old output (with --minify)
x={1:1,-1:-1,NaN:NaN,1/0:1/0,-1/0:-1/0};
// New output (with --minify)
x={1:1,[-1]:-1,NaN:NaN,[1/0]:1/0,[-1/0]:-1/0};
```
### [`v0.18.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0183)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.2...v0.18.3)
- Fix a panic due to empty static class blocks ([#3161](https://togithub.com/evanw/esbuild/issues/3161))
This release fixes a bug where an internal invariant that was introduced in the previous release was sometimes violated, which then caused a panic. It happened when bundling code containing an empty static class block with both minification and bundling enabled.
### [`v0.18.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0182)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.1...v0.18.2)
- Lower static blocks when static fields are lowered ([#2800](https://togithub.com/evanw/esbuild/issues/2800), [#2950](https://togithub.com/evanw/esbuild/issues/2950), [#3025](https://togithub.com/evanw/esbuild/issues/3025))
This release fixes a bug where esbuild incorrectly did not lower static class blocks when static class fields needed to be lowered. For example, the following code should print `1 2 3` but previously printed `2 1 3` instead due to this bug:
```js
// Original code
class Foo {
static x = console.log(1)
static { console.log(2) }
static y = console.log(3)
}
// Old output (with --supported:class-static-field=false)
class Foo {
static {
console.log(2);
}
}
__publicField(Foo, "x", console.log(1));
__publicField(Foo, "y", console.log(3));
// New output (with --supported:class-static-field=false)
class Foo {
}
__publicField(Foo, "x", console.log(1));
console.log(2);
__publicField(Foo, "y", console.log(3));
```
- Use static blocks to implement `--keep-names` on classes ([#2389](https://togithub.com/evanw/esbuild/issues/2389))
This change fixes a bug where the `name` property could previously be incorrect within a class static context when using `--keep-names`. The problem was that the `name` property was being initialized after static blocks were run instead of before. This has been fixed by moving the `name` property initializer into a static block at the top of the class body:
```js
// Original code
if (typeof Foo === 'undefined') {
let Foo = class {
static test = this.name
}
console.log(Foo.test)
}
// Old output (with --keep-names)
if (typeof Foo === "undefined") {
let Foo2 = /* @__PURE__ */ __name(class {
static test = this.name;
}, "Foo");
console.log(Foo2.test);
}
// New output (with --keep-names)
if (typeof Foo === "undefined") {
let Foo2 = class {
static {
__name(this, "Foo");
}
static test = this.name;
};
console.log(Foo2.test);
}
```
This change was somewhat involved, especially regarding what esbuild considers to be side-effect free. Some unused classes that weren't removed by tree shaking in previous versions of esbuild may now be tree-shaken. One example is classes with static private fields that are transformed by esbuild into code that doesn't use JavaScript's private field syntax. Previously esbuild's tree shaking analysis ran on the class after syntax lowering, but with this release it will run on the class before syntax lowering, meaning it should no longer be confused by class mutations resulting from automatically-generated syntax lowering code.
### [`v0.18.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01811)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.0...v0.18.1)
- Fix a TypeScript code generation edge case ([#3199](https://togithub.com/evanw/esbuild/issues/3199))
This release fixes a regression in version 0.18.4 where using a TypeScript `namespace` that exports a `class` declaration combined with `--keep-names` and a `--target` of `es2021` or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to `X2._Y` vs. `X2.Y`):
```ts
// Original code
// Old output (with --keep-names --target=es2021)
var X;
((X2) => {
const _Y = class _Y {
};
__name(_Y, "Y");
let Y = _Y;
X2._Y = _Y;
})(X || (X = {}));
// New output (with --keep-names --target=es2021)
var X;
((X2) => {
const _Y = class _Y {
};
__name(_Y, "Y");
let Y = _Y;
X2.Y = _Y;
})(X || (X = {}));
```
### [`v0.18.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0180)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.19...v0.18.0)
**This release deliberately contains backwards-incompatible changes.** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.17.0` or `~0.17.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.
The breaking changes in this release mainly focus on fixing some long-standing issues with esbuild's handling of `tsconfig.json` files. Here are all the changes in this release, in detail:
- Add a way to try esbuild online ([#797](https://togithub.com/evanw/esbuild/issues/797))
There is now a way to try esbuild live on esbuild's website without installing it: https://esbuild.github.io/try/. In addition to being able to more easily evaluate esbuild, this should also make it more efficient to generate esbuild bug reports. For example, you can use it to compare the behavior of different versions of esbuild on the same input. The state of the page is stored in the URL for easy sharing. Many thanks to [@hyrious](https://togithub.com/hyrious) for creating https://hyrious.me/esbuild-repl/, which was the main inspiration for this addition to esbuild's website.
Two forms of build options are supported: either CLI-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AC0tbG9hZGVyPXRzeCAtLW1pbmlmeSAtLXNvdXJjZW1hcABsZXQgZWw6IEpTWC5FbGVtZW50ID0gPGRpdiAvPg)) or JS-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AHsKICBsb2FkZXI6ICd0c3gnLAogIG1pbmlmeTogdHJ1ZSwKICBzb3VyY2VtYXA6IHRydWUsCn0AbGV0IGVsOiBKU1guRWxlbWVudCA9IDxkaXYgLz4)). Both are converted into a JS object that's passed to esbuild's WebAssembly API. The CLI-style argument parser is a custom one that simulates shell quoting rules, and the JS-style argument parser is also custom and parses a superset of JSON (basically JSON5 + regular expressions). So argument parsing is an approximate simulation of what happens for real but hopefully it should be close enough.
- Changes to esbuild's `tsconfig.json` support ([#3019](https://togithub.com/evanw/esbuild/issues/3019)):
This release makes the following changes to esbuild's `tsconfig.json` support:
- Using experimental decorators now requires `"experimentalDecorators": true` ([#104](https://togithub.com/evanw/esbuild/issues/104))
Previously esbuild would always compile decorators in TypeScript code using TypeScript's experimental decorator transform. Now that standard JavaScript decorators are close to being finalized, esbuild will now require you to use `"experimentalDecorators": true` to do this. This new requirement makes it possible for esbuild to introduce a transform for standard JavaScript decorators in TypeScript code in the future. Such a transform has not been implemented yet, however.
- TypeScript's `target` no longer affects esbuild's `target` ([#2628](https://togithub.com/evanw/esbuild/issues/2628))
Some people requested that esbuild support TypeScript's `target` setting, so support for it was added (in [version 0.12.4](https://togithub.com/evanw/esbuild/releases/v0.12.4)). However, esbuild supports reading from multiple `tsconfig.json` files within a single build, which opens up the possibility that different files in the build have different language targets configured. There isn't really any reason to do this and it can lead to unexpected results. So with this release, the `target` setting in `tsconfig.json` will no longer affect esbuild's own `target` setting. You will have to use esbuild's own target setting instead (which is a single, global value).
- TypeScript's `jsx` setting no longer causes esbuild to preserve JSX syntax ([#2634](https://togithub.com/evanw/esbuild/issues/2634))
TypeScript has a setting called [`jsx`](https://www.typescriptlang.org/tsconfig#jsx) that controls how to transform JSX into JS. The tool-agnostic transform is called `react`, and the React-specific transform is called `react-jsx` (or `react-jsxdev`). There is also a setting called `preserve` which indicates JSX should be passed through untransformed. Previously people would run esbuild with `"jsx": "preserve"` in their `tsconfig.json` files and then be surprised when esbuild preserved their JSX. So with this release, esbuild will now ignore `"jsx": "preserve"` in `tsconfig.json` files. If you want to preserve JSX syntax with esbuild, you now have to use `--jsx=preserve`.
Note: Some people have suggested that esbuild's equivalent `jsx` setting override the one in `tsconfig.json`. However, some projects need to legitimately have different files within the same build use different transforms (i.e. `react` vs. `react-jsx`) and having esbuild's global `jsx` setting override `tsconfig.json` would prevent this from working. This release ignores `"jsx": "preserve"` but still allows other `jsx` values in `tsconfig.json` files to override esbuild's global `jsx` setting to keep the ability for multiple files within the same build to use different transforms.
- `useDefineForClassFields` behavior has changed ([#2584](https://togithub.com/evanw/esbuild/issues/2584), [#2993](https://togithub.com/evanw/esbuild/issues/2993))
Class fields in TypeScript look like this (`x` is a class field):
```js
class Foo {
x = 123
}
```
TypeScript has legacy behavior that uses assignment semantics instead of define semantics for class fields when [`useDefineForClassFields`](https://www.typescriptlang.org/tsconfig#useDefineForClassFields) is enabled (in which case class fields in TypeScript behave differently than they do in JavaScript, which is arguably "wrong").
This legacy behavior exists because TypeScript added class fields to TypeScript before they were added to JavaScript. The TypeScript team decided to go with assignment semantics and shipped their implementation. Much later on TC39 decided to go with define semantics for class fields in JavaScript instead. This behaves differently if the base class has a setter with the same name:
```js
class Base {
set x(_) {
console.log('x:', _)
}
}
// useDefineForClassFields: false
class AssignSemantics extends Base {
constructor() {
super()
this.x = 123
}
}
// useDefineForClassFields: true
class DefineSemantics extends Base {
constructor() {
super()
Object.defineProperty(this, 'x', { value: 123 })
}
}
console.log(
new AssignSemantics().x, // Calls the setter
new DefineSemantics().x // Doesn't call the setter
)
```
When you run `tsc`, the value of `useDefineForClassFields` defaults to `false` when it's not specified and the `target` in `tsconfig.json` is present but earlier than `ES2022`. This sort of makes sense because the class field language feature was added in ES2022, so before ES2022 class fields didn't exist (and thus TypeScript's legacy behavior is active). However, TypeScript's `target` setting currently defaults to `ES3` which unfortunately means that the `useDefineForClassFields` setting currently defaults to false (i.e. to "wrong"). In other words if you run `tsc` with all default settings, class fields will behave incorrectly.
Previously esbuild tried to do what `tsc` did. That meant esbuild's version of `useDefineForClassFields` was `false` by default, and was also `false` if esbuild's `--target=` was present but earlier than `es2022`. However, TypeScript's legacy class field behavior is becoming increasingly irrelevant and people who expect class fields in TypeScript to work like they do in JavaScript are confused when they use esbuild with default settings. It's also confusing that the behavior of class fields would change if you changed the language target (even though that's exactly how TypeScript works).
So with this release, esbuild will now only use the information in `tsconfig.json` to determine whether `useDefineForClassFields` is true or not. Specifically `useDefineForClassFields` will be respected if present, otherwise it will be `false` if `target` is present in `tsconfig.json` and is `ES2021` or earlier, otherwise it will be `true`. Targets passed to esbuild's `--target=` setting will no longer affect `us
Configuration
📅 Schedule: Branch creation - "on the first day of the month" (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.
This PR contains the following updates:
5.59.8->5.61.05.59.8->5.61.00.17.19->0.18.118.42.0->8.44.05.6.3->5.6.4Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.61.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5601v5610-2023-07-03) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.1...v5.61.0) ##### Features - **eslint-plugin:** \[ban-types] ban types in extends and implements ([#7129](https://togithub.com/typescript-eslint/typescript-eslint/issues/7129)) ([997783f](https://togithub.com/typescript-eslint/typescript-eslint/commit/997783ff108ca18af709667ef3fdfa7134a8eefe)) - use graphemer instead of grapheme-splitter ([#7069](https://togithub.com/typescript-eslint/typescript-eslint/issues/7069)) ([faea3ff](https://togithub.com/typescript-eslint/typescript-eslint/commit/faea3ff8b4d750974c41262b44db314f20d0c99c)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. #### [5.60.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) (2023-06-26) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. ### [`v5.60.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5601-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5600v5601-2023-06-26) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. ### [`v5.60.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5600-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55911v5600-2023-06-19) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0) ##### Features - **eslint-plugin:** \[restrict-plus-operands] add allow\* options ([#6161](https://togithub.com/typescript-eslint/typescript-eslint/issues/6161)) ([def09f8](https://togithub.com/typescript-eslint/typescript-eslint/commit/def09f88cdb4a85cebb8619b45931f7e2c88dfc0)) #### [5.59.11](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) (2023-06-12) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.10](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) (2023-06-12) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.9](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) (2023-06-05) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.8](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.7...v5.59.8) (2023-05-29) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.6...v5.59.7) (2023-05-22) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.5...v5.59.6) (2023-05-15) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.4...v5.59.5) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.3...v5.59.4) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.2...v5.59.3) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2) (2023-05-01) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.59.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) (2023-04-24) ##### Bug Fixes - **eslint-plugin:** \[prefer-regexp-exec] skip malformed regexes ([#6935](https://togithub.com/typescript-eslint/typescript-eslint/issues/6935)) ([05ed60e](https://togithub.com/typescript-eslint/typescript-eslint/commit/05ed60e25f1de9d1bb83d56c81a349130960bec8)) - **eslint-plugin:** \[unified-signatures] no parameters function ([#6940](https://togithub.com/typescript-eslint/typescript-eslint/issues/6940)) ([2970861](https://togithub.com/typescript-eslint/typescript-eslint/commit/297086154acc568a0ae8eb41c8977b7a7ba4e0ed)) ### [`v5.59.11`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#55911-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55910v55911-2023-06-12) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) ### [`v5.59.10`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#55910-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5599v55910-2023-06-12) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) ### [`v5.59.9`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5599-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5598v5599-2023-06-05) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.61.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5610-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5601v5610-2023-07-03) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.1...v5.61.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. #### [5.60.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) (2023-06-26) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. ### [`v5.60.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5601-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5600v5601-2023-06-26) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. ### [`v5.60.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5600-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55911v5600-2023-06-19) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.11...v5.60.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.11](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) (2023-06-12) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.10](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) (2023-06-12) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.9](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) (2023-06-05) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.8](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.7...v5.59.8) (2023-05-29) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.6...v5.59.7) (2023-05-22) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.5...v5.59.6) (2023-05-15) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.4...v5.59.5) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.3...v5.59.4) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.2...v5.59.3) (2023-05-08) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.1...v5.59.2) (2023-05-01) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.59.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) (2023-04-24) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.59.11`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#55911-httpsgithubcomtypescript-eslinttypescript-eslintcomparev55910v55911-2023-06-12) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.10...v5.59.11) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.59.10`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#55910-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5599v55910-2023-06-12) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.9...v5.59.10) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.59.9`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5599-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5598v5599-2023-06-05) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.8...v5.59.9) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)evanw/esbuild (esbuild)
### [`v0.18.11`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01811) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.10...v0.18.11) - Fix a TypeScript code generation edge case ([#3199](https://togithub.com/evanw/esbuild/issues/3199)) This release fixes a regression in version 0.18.4 where using a TypeScript `namespace` that exports a `class` declaration combined with `--keep-names` and a `--target` of `es2021` or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to `X2._Y` vs. `X2.Y`): ```ts // Original code // Old output (with --keep-names --target=es2021) var X; ((X2) => { const _Y = class _Y { }; __name(_Y, "Y"); let Y = _Y; X2._Y = _Y; })(X || (X = {})); // New output (with --keep-names --target=es2021) var X; ((X2) => { const _Y = class _Y { }; __name(_Y, "Y"); let Y = _Y; X2.Y = _Y; })(X || (X = {})); ``` ### [`v0.18.10`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01810) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.9...v0.18.10) - Fix a tree-shaking bug that removed side effects ([#3195](https://togithub.com/evanw/esbuild/issues/3195)) This fixes a regression in version 0.18.4 where combining `--minify-syntax` with `--keep-names` could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because `--keep-names` generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then `--minify-syntax` could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together. - Fix an incorrect warning about CSS nesting ([#3197](https://togithub.com/evanw/esbuild/issues/3197)) A warning is currently generated when transforming nested CSS to a browser that doesn't support `:is()` because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as `@top-left` within `@page`. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning. ### [`v0.18.9`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0189) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.8...v0.18.9) - Fix `await using` declarations inside `async` generator functions I forgot about the new `await using` declarations when implementing lowering for `async` generator functions in the previous release. This change fixes the transformation of `await using` declarations when they are inside lowered `async` generator functions: ```js // Original code async function* foo() { await using x = await y } // Old output (with --supported:async-generator=false) function foo() { return __asyncGenerator(this, null, function* () { await using x = yield new __await(y); }); } // New output (with --supported:async-generator=false) function foo() { return __asyncGenerator(this, null, function* () { var _stack = []; try { const x = __using(_stack, yield new __await(y), true); } catch (_) { var _error = _, _hasError = true; } finally { var _promise = __callDispose(_stack, _error, _hasError); _promise && (yield new __await(_promise)); } }); } ``` - Insert some prefixed CSS properties when appropriate ([#3122](https://togithub.com/evanw/esbuild/issues/3122)) With this release, esbuild will now insert prefixed CSS properties in certain cases when the `target` setting includes browsers that require a certain prefix. This is currently done for the following properties: - `appearance: *;` => `-webkit-appearance: *; -moz-appearance: *;` - `backdrop-filter: *;` => `-webkit-backdrop-filter: *;` - `background-clip: text` => `-webkit-background-clip: text;` - `box-decoration-break: *;` => `-webkit-box-decoration-break: *;` - `clip-path: *;` => `-webkit-clip-path: *;` - `font-kerning: *;` => `-webkit-font-kerning: *;` - `hyphens: *;` => `-webkit-hyphens: *;` - `initial-letter: *;` => `-webkit-initial-letter: *;` - `mask-image: *;` => `-webkit-mask-image: *;` - `mask-origin: *;` => `-webkit-mask-origin: *;` - `mask-position: *;` => `-webkit-mask-position: *;` - `mask-repeat: *;` => `-webkit-mask-repeat: *;` - `mask-size: *;` => `-webkit-mask-size: *;` - `position: sticky;` => `position: -webkit-sticky;` - `print-color-adjust: *;` => `-webkit-print-color-adjust: *;` - `tab-size: *;` => `-moz-tab-size: *; -o-tab-size: *;` - `text-decoration-color: *;` => `-webkit-text-decoration-color: *; -moz-text-decoration-color: *;` - `text-decoration-line: *;` => `-webkit-text-decoration-line: *; -moz-text-decoration-line: *;` - `text-decoration-skip: *;` => `-webkit-text-decoration-skip: *;` - `text-emphasis-color: *;` => `-webkit-text-emphasis-color: *;` - `text-emphasis-position: *;` => `-webkit-text-emphasis-position: *;` - `text-emphasis-style: *;` => `-webkit-text-emphasis-style: *;` - `text-orientation: *;` => `-webkit-text-orientation: *;` - `text-size-adjust: *;` => `-webkit-text-size-adjust: *; -ms-text-size-adjust: *;` - `user-select: *;` => `-webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;` Here is an example: ```css /* Original code */ div { mask-image: url(x.png); } /* Old output (with --target=chrome99) */ div { mask-image: url(x.png); } /* New output (with --target=chrome99) */ div { -webkit-mask-image: url(x.png); mask-image: url(x.png); } ``` Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate. - Fix an obscure identifier minification bug ([#2809](https://togithub.com/evanw/esbuild/issues/2809)) Function declarations in nested scopes behave differently depending on whether or not `"use strict"` is present. To avoid generating code that behaves differently depending on whether strict mode is enabled or not, esbuild transforms nested function declarations into variable declarations. However, there was a bug where the generated variable name was not being recorded as declared internally, which meant that it wasn't being renamed correctly by the minifier and could cause a name collision. This bug has been fixed: ```js // Original code const n = '' for (let i of [0,1]) { function f () {} } // Old output (with --minify-identifiers --format=esm) const f = ""; for (let o of [0, 1]) { let n = function() { }; var f = n; } // New output (with --minify-identifiers --format=esm) const f = ""; for (let o of [0, 1]) { let n = function() { }; var t = n; } ``` - Fix a bug in esbuild's compatibility table script ([#3179](https://togithub.com/evanw/esbuild/pull/3179)) Setting esbuild's `target` to a specific JavaScript engine tells esbuild to use the JavaScript syntax feature compatibility data from https://kangax.github.io/compat-table/es6/ for that engine to determine which syntax features to allow. However, esbuild's script that builds this internal compatibility table had a bug that incorrectly ignores tests for engines that still have outstanding implementation bugs which were never fixed. This change fixes this bug with the script. The only case where this changed the information in esbuild's internal compatibility table is that the `hermes` target is marked as no longer supporting destructuring. This is because there is a failing destructuring-related test for Hermes on https://kangax.github.io/compat-table/es6/. If you want to use destructuring with Hermes anyway, you can pass `--supported:destructuring=true` to esbuild to override the `hermes` target and force esbuild to accept this syntax. This fix was contributed by [@ArrayZoneYour](https://togithub.com/ArrayZoneYour). ### [`v0.18.8`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0188) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.7...v0.18.8) - Implement transforming `async` generator functions ([#2780](https://togithub.com/evanw/esbuild/issues/2780)) With this release, esbuild will now transform `async` generator functions into normal generator functions when the configured target environment doesn't support them. These functions behave similar to normal generator functions except that they use the `Symbol.asyncIterator` interface instead of the `Symbol.iterator` interface and the iteration methods return promises. Here's an example (helper functions are omitted): ```js // Original code async function* foo() { yield Promise.resolve(1) await new Promise(r => setTimeout(r, 100)) yield *[Promise.resolve(2)] } async function bar() { for await (const x of foo()) { console.log(x) } } bar() // New output (with --target=es6) function foo() { return __asyncGenerator(this, null, function* () { yield Promise.resolve(1); yield new __await(new Promise((r) => setTimeout(r, 100))); yield* __yieldStar([Promise.resolve(2)]); }); } function bar() { return __async(this, null, function* () { try { for (var iter = __forAwait(foo()), more, temp, error; more = !(temp = yield iter.next()).done; more = false) { const x = temp.value; console.log(x); } } catch (temp) { error = [temp]; } finally { try { more && (temp = iter.return) && (yield temp.call(iter)); } finally { if (error) throw error[0]; } } }); } bar(); ``` This is an older feature that was added to JavaScript in ES2018 but I didn't implement the transformation then because it's a rarely-used feature. Note that esbuild already added support for transforming `for await` loops (the other part of the [asynchronous iteration proposal](https://togithub.com/tc39/proposal-async-iteration)) a year ago, so support for asynchronous iteration should now be complete. I have never used this feature myself and code that uses this feature is hard to come by, so this transformation has not yet been tested on real-world code. If you do write code that uses this feature, please let me know if esbuild's `async` generator transformation doesn't work with your code. ### [`v0.18.7`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0187) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.6...v0.18.7) - Add support for `using` declarations in TypeScript 5.2+ ([#3191](https://togithub.com/evanw/esbuild/issues/3191)) TypeScript 5.2 (due to be released in August of 2023) will introduce `using` declarations, which will allow you to automatically dispose of the declared resources when leaving the current scope. You can read the [TypeScript PR for this feature](https://togithub.com/microsoft/TypeScript/pull/54505) for more information. This release of esbuild adds support for transforming this syntax to target environments without support for `using` declarations (which is currently all targets other than `esnext`). Here's an example (helper functions are omitted): ```js // Original code class Foo { [Symbol.dispose]() { console.log('cleanup') } } using foo = new Foo; foo.bar(); // New output (with --target=es6) var _stack = []; try { var Foo = class { [Symbol.dispose]() { console.log("cleanup"); } }; var foo = __using(_stack, new Foo()); foo.bar(); } catch (_) { var _error = _, _hasError = true; } finally { __callDispose(_stack, _error, _hasError); } ``` The injected helper functions ensure that the method named `Symbol.dispose` is called on `new Foo` when control exits the scope. Note that as with all new JavaScript APIs, you'll need to polyfill `Symbol.dispose` if it's not present before you use it. This is not something that esbuild does for you because esbuild only handles syntax, not APIs. Polyfilling it can be done with something like this: ```js Symbol.dispose ||= Symbol('Symbol.dispose') ``` This feature also introduces `await using` declarations which are like `using` declarations but they call `await` on the disposal method (not on the initializer). Here's an example (helper functions are omitted): ```js // Original code class Foo { async [Symbol.asyncDispose]() { await new Promise(done => { setTimeout(done, 1000) }) console.log('cleanup') } } await using foo = new Foo; foo.bar(); // New output (with --target=es2022) var _stack = []; try { var Foo = class { async [Symbol.asyncDispose]() { await new Promise((done) => { setTimeout(done, 1e3); }); console.log("cleanup"); } }; var foo = __using(_stack, new Foo(), true); foo.bar(); } catch (_) { var _error = _, _hasError = true; } finally { var _promise = __callDispose(_stack, _error, _hasError); _promise && await _promise; } ``` The injected helper functions ensure that the method named `Symbol.asyncDispose` is called on `new Foo` when control exits the scope, and that the returned promise is awaited. Similarly to `Symbol.dispose`, you'll also need to polyfill `Symbol.asyncDispose` before you use it. - Add a `--line-limit=` flag to limit line length ([#3170](https://togithub.com/evanw/esbuild/issues/3170)) Long lines are common in minified code. However, many tools and text editors can't handle long lines. This release introduces the `--line-limit=` flag to tell esbuild to wrap lines longer than the provided number of bytes. For example, `--line-limit=80` tells esbuild to insert a newline soon after a given line reaches 80 bytes in length. This setting applies to both JavaScript and CSS, and works even when minification is disabled. Note that turning this setting on will make your files bigger, as the extra newlines take up additional space in the file (even after gzip compression). ### [`v0.18.6`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0186) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.5...v0.18.6) - Fix tree-shaking of classes with decorators ([#3164](https://togithub.com/evanw/esbuild/issues/3164)) This release fixes a bug where esbuild incorrectly allowed tree-shaking on classes with decorators. Each decorator is a function call, so classes with decorators must never be tree-shaken. This bug was a regression that was unintentionally introduced in version 0.18.2 by the change that enabled tree-shaking of lowered private fields. Previously decorators were always lowered, and esbuild always considered the automatically-generated decorator code to be a side effect. But this is no longer the case now that esbuild analyzes side effects using the AST before lowering takes place. This bug was fixed by considering any decorator a side effect. - Fix a minification bug involving function expressions ([#3125](https://togithub.com/evanw/esbuild/issues/3125)) When minification is enabled, esbuild does limited inlining of `const` symbols at the top of a scope. This release fixes a bug where inlineable symbols were incorrectly removed assuming that they were inlined. They may not be inlined in cases where they were referenced by earlier constants in the body of a function expression. The declarations involved in these edge cases are now kept instead of being removed: ```js // Original code { const fn = () => foo const foo = 123 console.log(fn) } // Old output (with --minify-syntax) console.log((() => foo)()); // New output (with --minify-syntax) { const fn = () => foo, foo = 123; console.log(fn); } ``` ### [`v0.18.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0185) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.4...v0.18.5) - Implement auto accessors ([#3009](https://togithub.com/evanw/esbuild/issues/3009)) This release implements the new auto-accessor syntax from the upcoming [JavaScript decorators proposal](https://togithub.com/tc39/proposal-decorators). The auto-accessor syntax looks like this: ```js class Foo { accessor foo; static accessor bar; } new Foo().foo = Foo.bar; ``` This syntax is not yet a part of JavaScript but it was [added to TypeScript in version 4.9](https://devblogs.microsoft.com/typescript/announcing-typescript-4-9/#auto-accessors-in-classes). More information about this feature can be found in [microsoft/TypeScript#49705](https://togithub.com/microsoft/TypeScript/pull/49705). Auto-accessors will be transformed if the target is set to something other than `esnext`: ```js // Output (with --target=esnext) class Foo { accessor foo; static accessor bar; } new Foo().foo = Foo.bar; // Output (with --target=es2022) class Foo { #foo; get foo() { return this.#foo; } set foo(_) { this.#foo = _; } static #bar; static get bar() { return this.#bar; } static set bar(_) { this.#bar = _; } } new Foo().foo = Foo.bar; // Output (with --target=es2021) var _foo, _bar; class Foo { constructor() { __privateAdd(this, _foo, void 0); } get foo() { return __privateGet(this, _foo); } set foo(_) { __privateSet(this, _foo, _); } static get bar() { return __privateGet(this, _bar); } static set bar(_) { __privateSet(this, _bar, _); } } _foo = new WeakMap(); _bar = new WeakMap(); __privateAdd(Foo, _bar, void 0); new Foo().foo = Foo.bar; ``` You can also now use auto-accessors with esbuild's TypeScript experimental decorator transformation, which should behave the same as decorating the underlying getter/setter pair. **Please keep in mind that this syntax is not yet part of JavaScript.** This release enables auto-accessors in `.js` files with the expectation that it will be a part of JavaScript soon. However, esbuild may change or remove this feature in the future if JavaScript ends up changing or removing this feature. Use this feature with caution for now. - Pass through JavaScript decorators ([#104](https://togithub.com/evanw/esbuild/issues/104)) In this release, esbuild now parses decorators from the upcoming [JavaScript decorators proposal](https://togithub.com/tc39/proposal-decorators) and passes them through to the output unmodified (as long as the language target is set to `esnext`). Transforming JavaScript decorators to environments that don't support them has not been implemented yet. The only decorator transform that esbuild currently implements is still the TypeScript experimental decorator transform, which only works in `.ts` files and which requires `"experimentalDecorators": true` in your `tsconfig.json` file. - Static fields with assign semantics now use static blocks if possible Setting `useDefineForClassFields` to false in TypeScript requires rewriting class fields to assignment statements. Previously this was done by removing the field from the class body and adding an assignment statement after the class declaration. However, this also caused any private fields to also be lowered by necessity (in case a field initializer uses a private symbol, either directly or indirectly). This release changes this transform to use an inline static block if it's supported, which avoids needing to lower private fields in this scenario: ```js // Original code class Test { static #foo = 123 static bar = this.#foo } // Old output (with useDefineForClassFields=false) var _foo; const _Test = class _Test { }; _foo = new WeakMap(); __privateAdd(_Test, _foo, 123); _Test.bar = __privateGet(_Test, _foo); let Test = _Test; // New output (with useDefineForClassFields=false) class Test { static #foo = 123; static { this.bar = this.#foo; } } ``` - Fix TypeScript experimental decorators combined with `--mangle-props` ([#3177](https://togithub.com/evanw/esbuild/issues/3177)) Previously using TypeScript experimental decorators combined with the `--mangle-props` setting could result in a crash, as the experimental decorator transform was not expecting a mangled property as a class member. This release fixes the crash so you can now combine both of these features together safely. ### [`v0.18.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0184) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.3...v0.18.4) - Bundling no longer unnecessarily transforms class syntax ([#1360](https://togithub.com/evanw/esbuild/issues/1360), [#1328](https://togithub.com/evanw/esbuild/issues/1328), [#1524](https://togithub.com/evanw/esbuild/issues/1524), [#2416](https://togithub.com/evanw/esbuild/issues/2416)) When bundling, esbuild automatically converts top-level class statements to class expressions. Previously this conversion had the unfortunate side-effect of also transforming certain other class-related syntax features to avoid correctness issues when the references to the class name within the class body. This conversion has been reworked to avoid doing this: ```js // Original code export class Foo { static foo = () => Foo } // Old output (with --bundle) var _Foo = class { }; var Foo = _Foo; __publicField(Foo, "foo", () => _Foo); // New output (with --bundle) var Foo = class _Foo { static foo = () => _Foo; }; ``` This conversion process is very complicated and has many edge cases (including interactions with static fields, static blocks, private class properties, and TypeScript experimental decorators). It should already be pretty robust but a change like this may introduce new unintentional behavior. Please report any issues with this upgrade on the esbuild bug tracker. You may be wondering why esbuild needs to do this at all. One reason to do this is that esbuild's bundler sometimes needs to lazily-evaluate a module. For example, a module may end up being both the target of a dynamic `import()` call and a static `import` statement. Lazy module evaluation is done by wrapping the top-level module code in a closure. To avoid a performance hit for static `import` statements, esbuild stores top-level exported symbols outside of the closure and references them directly instead of indirectly. Another reason to do this is that multiple JavaScript VMs have had and continue to have performance issues with TDZ (i.e. "temporal dead zone") checks. These checks validate that a let, or const, or class symbol isn't used before it's initialized. Here are two issues with well-known VMs: - V8: https://bugs.chromium.org/p/v8/issues/detail?id=13723 (10% slowdown) - JavaScriptCore: https://bugs.webkit.org/show_bug.cgi?id=199866 (1,000% slowdown!) JavaScriptCore had a severe performance issue as their TDZ implementation had time complexity that was quadratic in the number of variables needing TDZ checks in the same scope (with the top-level scope typically being the worst offender). V8 has ongoing issues with TDZ checks being present throughout the code their JIT generates even when they have already been checked earlier in the same function or when the function in question has already been run (so the checks have already happened). Due to esbuild's parallel architecture, esbuild both a) needs to convert class statements into class expressions during parsing and b) doesn't yet know whether this module will need to be lazily-evaluated or not in the parser. So esbuild always does this conversion during bundling in case it's needed for correctness (and also to avoid potentially catastrophic performance issues due to bundling creating a large scope with many TDZ variables). - Enforce TDZ errors in computed class property keys ([#2045](https://togithub.com/evanw/esbuild/issues/2045)) JavaScript allows class property keys to be generated at run-time using code, like this: ```js class Foo { static foo = 'foo' static [Foo.foo + '2'] = 2 } ``` Previously esbuild treated references to the containing class name within computed property keys as a reference to the partially-initialized class object. That meant code that attempted to reference properties of the class object (such as the code above) would get back `undefined` instead of throwing an error. This release rewrites references to the containing class name within computed property keys into code that always throws an error at run-time, which is how this JavaScript code is supposed to work. Code that does this will now also generate a warning. You should never write code like this, but it now should be more obvious when incorrect code like this is written. - Fix an issue with experimental decorators and static fields ([#2629](https://togithub.com/evanw/esbuild/issues/2629)) This release also fixes a bug regarding TypeScript experimental decorators and static class fields which reference the enclosing class name in their initializer. This affected top-level classes when bundling was enabled. Previously code that does this could crash because the class name wasn't initialized yet. This case should now be handled correctly: ```ts // Original code class Foo { @someDecorator static foo = 'foo' static bar = Foo.foo.length } // Old output const _Foo = class { static foo = "foo"; static bar = _Foo.foo.length; }; let Foo = _Foo; __decorateClass([ someDecorator ], Foo, "foo", 2); // New output const _Foo = class _Foo { static foo = "foo"; static bar = _Foo.foo.length; }; __decorateClass([ someDecorator ], _Foo, "foo", 2); let Foo = _Foo; ``` - Fix a minification regression with negative numeric properties ([#3169](https://togithub.com/evanw/esbuild/issues/3169)) Version 0.18.0 introduced a regression where computed properties with negative numbers were incorrectly shortened into a non-computed property when minification was enabled. This regression has been fixed: ```js // Original code x = { [1]: 1, [-1]: -1, [NaN]: NaN, [Infinity]: Infinity, [-Infinity]: -Infinity, } // Old output (with --minify) x={1:1,-1:-1,NaN:NaN,1/0:1/0,-1/0:-1/0}; // New output (with --minify) x={1:1,[-1]:-1,NaN:NaN,[1/0]:1/0,[-1/0]:-1/0}; ``` ### [`v0.18.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0183) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.2...v0.18.3) - Fix a panic due to empty static class blocks ([#3161](https://togithub.com/evanw/esbuild/issues/3161)) This release fixes a bug where an internal invariant that was introduced in the previous release was sometimes violated, which then caused a panic. It happened when bundling code containing an empty static class block with both minification and bundling enabled. ### [`v0.18.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0182) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.1...v0.18.2) - Lower static blocks when static fields are lowered ([#2800](https://togithub.com/evanw/esbuild/issues/2800), [#2950](https://togithub.com/evanw/esbuild/issues/2950), [#3025](https://togithub.com/evanw/esbuild/issues/3025)) This release fixes a bug where esbuild incorrectly did not lower static class blocks when static class fields needed to be lowered. For example, the following code should print `1 2 3` but previously printed `2 1 3` instead due to this bug: ```js // Original code class Foo { static x = console.log(1) static { console.log(2) } static y = console.log(3) } // Old output (with --supported:class-static-field=false) class Foo { static { console.log(2); } } __publicField(Foo, "x", console.log(1)); __publicField(Foo, "y", console.log(3)); // New output (with --supported:class-static-field=false) class Foo { } __publicField(Foo, "x", console.log(1)); console.log(2); __publicField(Foo, "y", console.log(3)); ``` - Use static blocks to implement `--keep-names` on classes ([#2389](https://togithub.com/evanw/esbuild/issues/2389)) This change fixes a bug where the `name` property could previously be incorrect within a class static context when using `--keep-names`. The problem was that the `name` property was being initialized after static blocks were run instead of before. This has been fixed by moving the `name` property initializer into a static block at the top of the class body: ```js // Original code if (typeof Foo === 'undefined') { let Foo = class { static test = this.name } console.log(Foo.test) } // Old output (with --keep-names) if (typeof Foo === "undefined") { let Foo2 = /* @__PURE__ */ __name(class { static test = this.name; }, "Foo"); console.log(Foo2.test); } // New output (with --keep-names) if (typeof Foo === "undefined") { let Foo2 = class { static { __name(this, "Foo"); } static test = this.name; }; console.log(Foo2.test); } ``` This change was somewhat involved, especially regarding what esbuild considers to be side-effect free. Some unused classes that weren't removed by tree shaking in previous versions of esbuild may now be tree-shaken. One example is classes with static private fields that are transformed by esbuild into code that doesn't use JavaScript's private field syntax. Previously esbuild's tree shaking analysis ran on the class after syntax lowering, but with this release it will run on the class before syntax lowering, meaning it should no longer be confused by class mutations resulting from automatically-generated syntax lowering code. ### [`v0.18.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01811) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.18.0...v0.18.1) - Fix a TypeScript code generation edge case ([#3199](https://togithub.com/evanw/esbuild/issues/3199)) This release fixes a regression in version 0.18.4 where using a TypeScript `namespace` that exports a `class` declaration combined with `--keep-names` and a `--target` of `es2021` or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to `X2._Y` vs. `X2.Y`): ```ts // Original code // Old output (with --keep-names --target=es2021) var X; ((X2) => { const _Y = class _Y { }; __name(_Y, "Y"); let Y = _Y; X2._Y = _Y; })(X || (X = {})); // New output (with --keep-names --target=es2021) var X; ((X2) => { const _Y = class _Y { }; __name(_Y, "Y"); let Y = _Y; X2.Y = _Y; })(X || (X = {})); ``` ### [`v0.18.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0180) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.19...v0.18.0) **This release deliberately contains backwards-incompatible changes.** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.17.0` or `~0.17.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. The breaking changes in this release mainly focus on fixing some long-standing issues with esbuild's handling of `tsconfig.json` files. Here are all the changes in this release, in detail: - Add a way to try esbuild online ([#797](https://togithub.com/evanw/esbuild/issues/797)) There is now a way to try esbuild live on esbuild's website without installing it: https://esbuild.github.io/try/. In addition to being able to more easily evaluate esbuild, this should also make it more efficient to generate esbuild bug reports. For example, you can use it to compare the behavior of different versions of esbuild on the same input. The state of the page is stored in the URL for easy sharing. Many thanks to [@hyrious](https://togithub.com/hyrious) for creating https://hyrious.me/esbuild-repl/, which was the main inspiration for this addition to esbuild's website. Two forms of build options are supported: either CLI-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AC0tbG9hZGVyPXRzeCAtLW1pbmlmeSAtLXNvdXJjZW1hcABsZXQgZWw6IEpTWC5FbGVtZW50ID0gPGRpdiAvPg)) or JS-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AHsKICBsb2FkZXI6ICd0c3gnLAogIG1pbmlmeTogdHJ1ZSwKICBzb3VyY2VtYXA6IHRydWUsCn0AbGV0IGVsOiBKU1guRWxlbWVudCA9IDxkaXYgLz4)). Both are converted into a JS object that's passed to esbuild's WebAssembly API. The CLI-style argument parser is a custom one that simulates shell quoting rules, and the JS-style argument parser is also custom and parses a superset of JSON (basically JSON5 + regular expressions). So argument parsing is an approximate simulation of what happens for real but hopefully it should be close enough. - Changes to esbuild's `tsconfig.json` support ([#3019](https://togithub.com/evanw/esbuild/issues/3019)): This release makes the following changes to esbuild's `tsconfig.json` support: - Using experimental decorators now requires `"experimentalDecorators": true` ([#104](https://togithub.com/evanw/esbuild/issues/104)) Previously esbuild would always compile decorators in TypeScript code using TypeScript's experimental decorator transform. Now that standard JavaScript decorators are close to being finalized, esbuild will now require you to use `"experimentalDecorators": true` to do this. This new requirement makes it possible for esbuild to introduce a transform for standard JavaScript decorators in TypeScript code in the future. Such a transform has not been implemented yet, however. - TypeScript's `target` no longer affects esbuild's `target` ([#2628](https://togithub.com/evanw/esbuild/issues/2628)) Some people requested that esbuild support TypeScript's `target` setting, so support for it was added (in [version 0.12.4](https://togithub.com/evanw/esbuild/releases/v0.12.4)). However, esbuild supports reading from multiple `tsconfig.json` files within a single build, which opens up the possibility that different files in the build have different language targets configured. There isn't really any reason to do this and it can lead to unexpected results. So with this release, the `target` setting in `tsconfig.json` will no longer affect esbuild's own `target` setting. You will have to use esbuild's own target setting instead (which is a single, global value). - TypeScript's `jsx` setting no longer causes esbuild to preserve JSX syntax ([#2634](https://togithub.com/evanw/esbuild/issues/2634)) TypeScript has a setting called [`jsx`](https://www.typescriptlang.org/tsconfig#jsx) that controls how to transform JSX into JS. The tool-agnostic transform is called `react`, and the React-specific transform is called `react-jsx` (or `react-jsxdev`). There is also a setting called `preserve` which indicates JSX should be passed through untransformed. Previously people would run esbuild with `"jsx": "preserve"` in their `tsconfig.json` files and then be surprised when esbuild preserved their JSX. So with this release, esbuild will now ignore `"jsx": "preserve"` in `tsconfig.json` files. If you want to preserve JSX syntax with esbuild, you now have to use `--jsx=preserve`. Note: Some people have suggested that esbuild's equivalent `jsx` setting override the one in `tsconfig.json`. However, some projects need to legitimately have different files within the same build use different transforms (i.e. `react` vs. `react-jsx`) and having esbuild's global `jsx` setting override `tsconfig.json` would prevent this from working. This release ignores `"jsx": "preserve"` but still allows other `jsx` values in `tsconfig.json` files to override esbuild's global `jsx` setting to keep the ability for multiple files within the same build to use different transforms. - `useDefineForClassFields` behavior has changed ([#2584](https://togithub.com/evanw/esbuild/issues/2584), [#2993](https://togithub.com/evanw/esbuild/issues/2993)) Class fields in TypeScript look like this (`x` is a class field): ```js class Foo { x = 123 } ``` TypeScript has legacy behavior that uses assignment semantics instead of define semantics for class fields when [`useDefineForClassFields`](https://www.typescriptlang.org/tsconfig#useDefineForClassFields) is enabled (in which case class fields in TypeScript behave differently than they do in JavaScript, which is arguably "wrong"). This legacy behavior exists because TypeScript added class fields to TypeScript before they were added to JavaScript. The TypeScript team decided to go with assignment semantics and shipped their implementation. Much later on TC39 decided to go with define semantics for class fields in JavaScript instead. This behaves differently if the base class has a setter with the same name: ```js class Base { set x(_) { console.log('x:', _) } } // useDefineForClassFields: false class AssignSemantics extends Base { constructor() { super() this.x = 123 } } // useDefineForClassFields: true class DefineSemantics extends Base { constructor() { super() Object.defineProperty(this, 'x', { value: 123 }) } } console.log( new AssignSemantics().x, // Calls the setter new DefineSemantics().x // Doesn't call the setter ) ``` When you run `tsc`, the value of `useDefineForClassFields` defaults to `false` when it's not specified and the `target` in `tsconfig.json` is present but earlier than `ES2022`. This sort of makes sense because the class field language feature was added in ES2022, so before ES2022 class fields didn't exist (and thus TypeScript's legacy behavior is active). However, TypeScript's `target` setting currently defaults to `ES3` which unfortunately means that the `useDefineForClassFields` setting currently defaults to false (i.e. to "wrong"). In other words if you run `tsc` with all default settings, class fields will behave incorrectly. Previously esbuild tried to do what `tsc` did. That meant esbuild's version of `useDefineForClassFields` was `false` by default, and was also `false` if esbuild's `--target=` was present but earlier than `es2022`. However, TypeScript's legacy class field behavior is becoming increasingly irrelevant and people who expect class fields in TypeScript to work like they do in JavaScript are confused when they use esbuild with default settings. It's also confusing that the behavior of class fields would change if you changed the language target (even though that's exactly how TypeScript works). So with this release, esbuild will now only use the information in `tsconfig.json` to determine whether `useDefineForClassFields` is true or not. Specifically `useDefineForClassFields` will be respected if present, otherwise it will be `false` if `target` is present in `tsconfig.json` and is `ES2021` or earlier, otherwise it will be `true`. Targets passed to esbuild's `--target=` setting will no longer affect `usConfiguration
📅 Schedule: Branch creation - "on the first day of the month" (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.
This PR has been generated by Mend Renovate. View repository job log here.