typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.33.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5331-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5330v5331-2022-08-15)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.33.0...v5.33.1)
##### Bug Fixes
- missing placeholders in violation messages for `no-unnecessary-type-constraint` and `no-unsafe-argument` (and enable `eslint-plugin/recommended` rules internally) ([#5453](https://togithub.com/typescript-eslint/typescript-eslint/issues/5453)) ([d023910](https://togithub.com/typescript-eslint/typescript-eslint/commit/d0239104f4dbffd2b5ecdb19e520c7d4b71962e0))
### [`v5.33.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5330-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5320v5330-2022-08-08)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.32.0...v5.33.0)
##### Bug Fixes
- **eslint-plugin:** \[no-extra-parens] handle await with type assertion ([#5428](https://togithub.com/typescript-eslint/typescript-eslint/issues/5428)) ([e03826f](https://togithub.com/typescript-eslint/typescript-eslint/commit/e03826f08ce8bfdd6d6702025d975cfb7d867097))
- **website:** add explicit frontmatter description to rule docs ([#5429](https://togithub.com/typescript-eslint/typescript-eslint/issues/5429)) ([63cba5f](https://togithub.com/typescript-eslint/typescript-eslint/commit/63cba5f4c1884e102927b3b14b18a00e96ac63a1))
##### Features
- **eslint-plugin:** \[member-ordering] support static blocks ([#5417](https://togithub.com/typescript-eslint/typescript-eslint/issues/5417)) ([5983e5a](https://togithub.com/typescript-eslint/typescript-eslint/commit/5983e5ab3bfb94fec782bea54a37457fe31db545))
- **eslint-plugin:** \[prefer-as-const] adds support for class properties ([#5413](https://togithub.com/typescript-eslint/typescript-eslint/issues/5413)) ([d2394f8](https://togithub.com/typescript-eslint/typescript-eslint/commit/d2394f810960fda07b9c8affd47b769d16f4b8cb))
### [`v5.32.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5320-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5310v5320-2022-08-01)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.31.0...v5.32.0)
##### Features
- **eslint-plugin:** \[no-use-before-define] add "allowNamedExports" option ([#5397](https://togithub.com/typescript-eslint/typescript-eslint/issues/5397)) ([ad412cd](https://togithub.com/typescript-eslint/typescript-eslint/commit/ad412cdd74dc5619fbe4bf27c0a5eb5c5a4b65ca))
### [`v5.31.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5310-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5307v5310-2022-07-25)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.7...v5.31.0)
##### Bug Fixes
- **eslint-plugin:** \[typedef] Support nested array destructuring with type annotation ([#5311](https://togithub.com/typescript-eslint/typescript-eslint/issues/5311)) ([6d19efe](https://togithub.com/typescript-eslint/typescript-eslint/commit/6d19efed16d1cf0357ad363b6373d2021c49a8c8))
- **scope-manager:** handle typeParameters of TSInstantiationExpression ([#5355](https://togithub.com/typescript-eslint/typescript-eslint/issues/5355)) ([2595ccf](https://togithub.com/typescript-eslint/typescript-eslint/commit/2595ccf67cd5158edbd6bebd9ac2dbd8bbd8b99c))
##### Features
- **eslint-plugin:** \[consistent-generic-ctors] check class field declaration ([#5288](https://togithub.com/typescript-eslint/typescript-eslint/issues/5288)) ([48f996e](https://togithub.com/typescript-eslint/typescript-eslint/commit/48f996e8dda79c9c865e8ca6552069902836648b))
- **eslint-plugin:** \[prefer-nullish-coalescing] add ignoreTernaryTests option ([#4965](https://togithub.com/typescript-eslint/typescript-eslint/issues/4965)) ([f82727f](https://togithub.com/typescript-eslint/typescript-eslint/commit/f82727ffeb97475c07773ca1d1e5b9609fcc5e68))
#### [5.30.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) (2022-07-18)
##### Bug Fixes
- **eslint-plugin:** \[no-inferrable] fix optional param to valid code ([#5342](https://togithub.com/typescript-eslint/typescript-eslint/issues/5342)) ([98f6d5e](https://togithub.com/typescript-eslint/typescript-eslint/commit/98f6d5e6d08d1eb9789da52a15f337f5f53438bd))
- **eslint-plugin:** \[no-unused-vars] highlight last write reference ([#5267](https://togithub.com/typescript-eslint/typescript-eslint/issues/5267)) ([c3f199a](https://togithub.com/typescript-eslint/typescript-eslint/commit/c3f199a65a16aa72f5bb83e81a1ce0ffb5f69772))
#### [5.30.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) (2022-07-11)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.30.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) (2022-07-04)
##### Bug Fixes
- **eslint-plugin:** \[consistent-indexed-object-style] fix record mode fixer for generics with a default value ([#5280](https://togithub.com/typescript-eslint/typescript-eslint/issues/5280)) ([57f032c](https://togithub.com/typescript-eslint/typescript-eslint/commit/57f032c2e6a822c049177713778d0077ee138d9a))
#### [5.30.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.3...v5.30.4) (2022-07-03)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.30.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.2...v5.30.3) (2022-07-01)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.30.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.1...v5.30.2) (2022-07-01)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
#### [5.30.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.0...v5.30.1) (2022-07-01)
##### Bug Fixes
- **eslint-plugin:** \[no-base-to-string] add missing apostrophe to message ([#5270](https://togithub.com/typescript-eslint/typescript-eslint/issues/5270)) ([d320174](https://togithub.com/typescript-eslint/typescript-eslint/commit/58034e343a167ca7751b54d2b2a0e7d3852aabec))
### [`v5.30.7`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5307-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5306v5307-2022-07-18)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7)
##### Bug Fixes
- **eslint-plugin:** \[no-inferrable] fix optional param to valid code ([#5342](https://togithub.com/typescript-eslint/typescript-eslint/issues/5342)) ([98f6d5e](https://togithub.com/typescript-eslint/typescript-eslint/commit/98f6d5e6d08d1eb9789da52a15f337f5f53438bd))
- **eslint-plugin:** \[no-unused-vars] highlight last write reference ([#5267](https://togithub.com/typescript-eslint/typescript-eslint/issues/5267)) ([c3f199a](https://togithub.com/typescript-eslint/typescript-eslint/commit/c3f199a65a16aa72f5bb83e81a1ce0ffb5f69772))
### [`v5.30.6`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5306-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5305v5306-2022-07-11)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6)
**Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
### [`v5.30.5`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5305-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5304v5305-2022-07-04)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5)
##### Bug Fixes
- **eslint-plugin:** \[consistent-indexed-object-style] fix record mode fixer for generics with a default value ([#5280](https://togithub.com/typescript-eslint/typescript-eslint/issues/5280)) ([57f032c](https://togithub.com/typescript-eslint/typescript-eslint/commit/57f032c2e6a822c049177713778d0077ee138d9a))
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.33.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5331-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5330v5331-2022-08-15)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.33.0...v5.33.1)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.33.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5330-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5320v5330-2022-08-08)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.32.0...v5.33.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.32.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5320-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5310v5320-2022-08-01)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.31.0...v5.32.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.31.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5310-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5307v5310-2022-07-25)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.7...v5.31.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.30.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) (2022-07-18)
##### Bug Fixes
- expose types supporting old versions of typescript ([#5339](https://togithub.com/typescript-eslint/typescript-eslint/issues/5339)) ([4ba9bdb](https://togithub.com/typescript-eslint/typescript-eslint/commit/4ba9bdb93f87e6bc370f13aa1de48f435abe3f88))
#### [5.30.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) (2022-07-11)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.30.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) (2022-07-04)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.30.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.3...v5.30.4) (2022-07-03)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.30.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.2...v5.30.3) (2022-07-01)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.30.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.1...v5.30.2) (2022-07-01)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### 5.30.1 (2022-07-01)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.30.7`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5307-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5306v5307-2022-07-18)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7)
##### Bug Fixes
- expose types supporting old versions of typescript ([#5339](https://togithub.com/typescript-eslint/typescript-eslint/issues/5339)) ([4ba9bdb](https://togithub.com/typescript-eslint/typescript-eslint/commit/4ba9bdb93f87e6bc370f13aa1de48f435abe3f88))
### [`v5.30.6`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5306-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5305v5306-2022-07-11)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.30.5`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5305-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5304v5305-2022-07-04)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
evanw/esbuild
### [`v0.15.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0155)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.4...v0.15.5)
- Fix issues with Yarn PnP and Yarn's workspaces feature ([#2476](https://togithub.com/evanw/esbuild/issues/2476))
This release makes sure esbuild works with a Yarn feature called [workspaces](https://yarnpkg.com/features/workspaces/). Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix `exports` map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working.
### [`v0.15.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0154)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.3...v0.15.4)
- Consider TypeScript import assignments to be side-effect free ([#2468](https://togithub.com/evanw/esbuild/issues/2468))
TypeScript has a [legacy import syntax](https://www.typescriptlang.org/docs/handbook/namespaces.html#aliases) for working with TypeScript namespaces that looks like this:
```ts
import { someNamespace } from './some-file'
import bar = someNamespace.foo;
// some-file.ts
export namespace someNamespace {
export let foo = 123
}
```
Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if `bar` is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps `bar` in the output, which is done because `someNamespace.foo` is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case).
With this release, esbuild will now consider `someNamespace.foo` to have no side effects. This means `bar` will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of `bar`, so it would be incorrect to remove it. If you want `bar` to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output).
- Change the order of the banner and the `"use strict"` directive ([#2467](https://togithub.com/evanw/esbuild/issues/2467))
Previously the top of the file contained the following things in order:
1. The hashbang comment (see below) from the source code, if present
2. The `"use strict"` directive from the source code, if present
3. The content of esbuild's `banner` API option, if specified
This was problematic for people that used the `banner` API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to:
1. The hashbang comment (see below) from the source code, if present
2. The content of esbuild's `banner` API option, if specified
3. The `"use strict"` directive from the source code, if present
I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the `banner` API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the `"use strict"` directive.
For context: JavaScript files recently allowed using a [hashbang comment](https://togithub.com/tc39/proposal-hashbang), which starts with `#!` and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the `node` command. This comment typically has the value `#!/usr/bin/env node`. Hashbang comments will be a part of ES2023 when it's released next year.
- Fix `exports` maps with Yarn PnP path resolution ([#2473](https://togithub.com/evanw/esbuild/issues/2473))
The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that `exports` in `package.json` is not respected because node's module resolution algorithm doesn't interpret `exports` for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP.
### [`v0.15.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0153)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.2...v0.15.3)
- Change the Yarn PnP manifest to a singleton ([#2463](https://togithub.com/evanw/esbuild/issues/2463))
Previously esbuild searched for the Yarn PnP manifest in the parent directories of each file. But with Yarn's `enableGlobalCache` setting it's possible to configure Yarn PnP's implementation to reach outside of the directory subtree containing the Yarn PnP manifest. This was causing esbuild to fail to bundle projects with the `enableGlobalCache` setting enabled.
To handle this case, *esbuild will now only search for the Yarn PnP manifest in the current working directory of the esbuild process*. If you're using esbuild's CLI, this means you will now have to `cd` into the appropriate directory first. If you're using esbuild's API, you can override esbuild's value for the current working directory with the `absWorkingDir` API option.
- Fix Yarn PnP resolution failures due to backslashes in paths on Windows ([#2462](https://togithub.com/evanw/esbuild/issues/2462))
Previously dependencies of a Yarn PnP virtual dependency failed to resolve on Windows. This was because Windows uses `\` instead of `/` as a path separator, and the path manipulation algorithms used for Yarn PnP expected `/`. This release converts `\` into `/` in Windows paths, which fixes this issue.
- Fix `sideEffects` patterns containing slashes on Windows ([#2465](https://togithub.com/evanw/esbuild/issues/2465))
The `sideEffects` field in `package.json` lets you specify an array of patterns to mark which files have side effects (which causes all other files to be considered to not have side effects by exclusion). That looks like this:
```json
"sideEffects": [
"**/index.js",
"**/index.prod.js"
]
```
However, the presence of the `/` character in the pattern meant that the pattern failed to match Windows-style paths, which broke `sideEffects` on Windows in this case. This release fixes this problem by adding additional code to handle Windows-style paths.
### [`v0.15.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0152)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.1...v0.15.2)
- Fix Yarn PnP issue with packages containing `index.js` ([#2455](https://togithub.com/evanw/esbuild/issues/2455), [#2461](https://togithub.com/evanw/esbuild/issues/2461))
Yarn PnP's tests require the resolved paths to end in `/`. That's not how the rest of esbuild's internals work, however, and doing this messed up esbuild's node module path resolution regarding automatically-detected `index.js` files. Previously packages that relied on implicit `index.js` resolution rules didn't work with esbuild under Yarn PnP. Removing this slash has fixed esbuild's path resolution behavior regarding `index.js`, which should now the same both with and without Yarn PnP.
- Fix Yarn PnP support for `extends` in `tsconfig.json` ([#2456](https://togithub.com/evanw/esbuild/issues/2456))
Previously using `extends` in `tsconfig.json` with a path in a Yarn PnP package didn't work. This is because the process of setting up package path resolution rules requires parsing `tsconfig.json` files (due to the `baseUrl` and `paths` features) and resolving `extends` to a package path requires package path resolution rules to already be set up, which is a circular dependency. This cycle is broken by using special rules for `extends` in `tsconfig.json` that bypasses esbuild's normal package path resolution process. This is why using `extends` with a Yarn PnP package didn't automatically work. With this release, these special rules have been modified to check for a Yarn PnP manifest so this case should work now.
- Fix Yarn PnP support in `esbuild-wasm` ([#2458](https://togithub.com/evanw/esbuild/issues/2458))
When running esbuild via WebAssembly, Yarn PnP support previously failed because Go's file system internals return `EINVAL` when trying to read a `.zip` file as a directory when run with WebAssembly. This was unexpected because Go's file system internals return `ENOTDIR` for this case on native. This release updates esbuild to treat `EINVAL` like `ENOTDIR` in this case, which fixes using `esbuild-wasm` to bundle a Yarn PnP project.
Note that to be able to use `esbuild-wasm` for Yarn PnP successfully, you currently have to run it using `node` instead of `yarn node`. This is because the file system shim that Yarn overwrites node's native file system API with currently generates invalid file descriptors with negative values when inside a `.zip` file. This prevents esbuild from working correctly because Go's file system internals don't expect syscalls that succeed without an error to return an invalid file descriptor. Yarn is working on fixing their use of invalid file descriptors.
### [`v0.15.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0151)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.0...v0.15.1)
- Update esbuild's Yarn Plug'n'Play implementation to match the latest specification changes ([#2452](https://togithub.com/evanw/esbuild/issues/2452), [#2453](https://togithub.com/evanw/esbuild/pull/2453))
This release updates esbuild's implementation of Yarn Plug'n'Play to match some changes to Yarn's specification that just landed. The changes are as follows:
- Check for platform-specific absolute paths instead of always for the `/` prefix
The specification previously said that Yarn Plug'n'Play path resolution rules should not apply for paths that start with `/`. The intent was to avoid accidentally processing absolute paths. However, absolute paths on Windows such as `C:\project` start with drive letters instead of with `/`. So the specification was changed to instead explicitly avoid processing absolute paths.
- Make `$$virtual` an alias for `__virtual__`
Supporting Yarn-style path resolution requires implementing a custom Yarn-specific path traversal scheme where certain path segments are considered no-ops. Specifically any path containing segments of the form `__virtual__//` where `` is an integer must be treated as if they were `n` times the `..` operator instead (the `` path segment is ignored). So `/path/to/project/__virtual__/xyz/2/foo.js` maps to the underlying file `/path/to/project/../../foo.js`. This scheme makes it possible for Yarn to get node (and esbuild) to load the same file multiple times (which is sometimes required for correctness) without actually duplicating the file on the file system.
However, old versions of Yarn used to use `$$virtual` instead of `__virtual__`. This was changed because `$$virtual` was error-prone due to the use of the `$` character, which can cause bugs when it's not correctly escaped within regular expressions. Now that esbuild makes `$$virtual` an alias for `__virtual__`, esbuild should now work with manifests from these old Yarn versions.
- Ignore PnP manifests in virtual directories
The specification describes the algorithm for how to find the Plug'n'Play manifest when starting from a certain point in the file system: search through all parent directories in reverse order until the manifest is found. However, this interacts poorly with virtual paths since it can end up finding a virtual copy of the manifest instead of the original. To avoid this, esbuild now ignores manifests in virtual directories so that the search for the manifest will continue and find the original manifest in another parent directory later on.
These fixes mean that esbuild's implementation of Plug'n'Play now matches Yarn's implementation more closely, and esbuild can now correctly build more projects that use Plug'n'Play.
### [`v0.15.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0150)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.54...v0.15.0)
**This release contains backwards-incompatible changes.** Since esbuild is before version 1.0.0, these changes have been released as a new minor version to reflect this (as [recommended by npm](https://docs.npmjs.com/cli/v6/using-npm/semver/)). You should either be pinning the exact version of `esbuild` in your `package.json` file or be using a version range syntax that only accepts patch upgrades such as `~0.14.0`. See the documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.
- Implement the Yarn Plug'n'Play module resolution algorithm ([#154](https://togithub.com/evanw/esbuild/issues/154), [#237](https://togithub.com/evanw/esbuild/issues/237), [#1263](https://togithub.com/evanw/esbuild/issues/1263), [#2451](https://togithub.com/evanw/esbuild/pull/2451))
[Node](https://nodejs.org/) comes with a package manager called [npm](https://www.npmjs.com/), which installs packages into a `node_modules` folder. Node and esbuild both come with built-in rules for resolving import paths to packages within `node_modules`, so packages installed via npm work automatically without any configuration. However, many people use an alternative package manager called [Yarn](https://yarnpkg.com/). While Yarn can install packages using `node_modules`, it also offers a different package installation strategy called [Plug'n'Play](https://yarnpkg.com/features/pnp/), which is often shortened to "PnP" (not to be confused with [pnpm](https://pnpm.io/), which is an entirely different unrelated package manager).
Plug'n'Play installs packages as `.zip` files on your file system. The packages are never actually unzipped. Since Node doesn't know anything about Yarn's package installation strategy, this means you can no longer run your code with Node as it won't be able to find your packages. Instead, you need to run your code with Yarn, which applies patches to Node's file system APIs before running your code. These patches attempt to make zip files seem like normal directories. When running under Yarn, using Node's file system API to read `./some.zip/lib/file.js` actually automatically extracts `lib/file.js` from `./some.zip` at run-time as if it was a normal file. Other file system APIs behave similarly. However, these patches don't work with esbuild because esbuild is not written in JavaScript; it's a native binary executable that interacts with the file system directly through the operating system.
Previously the workaround for using esbuild with Plug'n'Play was to use the [`@yarnpkg/esbuild-plugin-pnp`](https://www.npmjs.com/package/@yarnpkg/esbuild-plugin-pnp) plugin with esbuild's JavaScript API. However, this wasn't great because the plugin needed to potentially intercept every single import path and file load to check whether it was a Plug'n'Play package, which has an unusually high performance cost. It also meant that certain subtleties of path resolution rules within a `.zip` file could differ slightly from the way esbuild normally works since path resolution inside `.zip` files was implemented by Yarn, not by esbuild (which is due to a limitation of esbuild's plugin API).
With this release, esbuild now contains an independent implementation of Yarn's Plug'n'Play algorithm (which is used when esbuild finds a `.pnp.js`, `.pnp.cjs`, or `.pnp.data.json` file in the directory tree). Creating additional implementations of this algorithm recently became possible because Yarn's package manifest format was recently documented: https://yarnpkg.com/advanced/pnp-spec/. This should mean that you can now use esbuild to bundle Plug'n'Play projects without any additional configuration (so you shouldn't need `@yarnpkg/esbuild-plugin-pnp` anymore). Bundling these projects should now happen much faster as Yarn no longer even needs to be run at all. Bundling the Yarn codebase itself with esbuild before and after this change seems to demonstrate over a 10x speedup (3.4s to 0.24s). And path resolution rules within Yarn packages should now be consistent with how esbuild handles regular Node packages. For example, fields such as `module` and `browser` in `package.json` files within `.zip` files should now be respected.
Keep in mind that this is brand new code and there may be some initial issues to work through before esbuild's implementation is solid. Yarn's Plug'n'Play specification is also brand new and may need some follow-up edits to guide new implementations to match Yarn's exact behavior. If you try this out, make sure to test it before committing to using it, and let me know if anything isn't working as expected. Should you need to debug esbuild's path resolution, you may find `--log-level=verbose` helpful.
### [`v0.14.54`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01454)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.53...v0.14.54)
- Fix optimizations for calls containing spread arguments ([#2445](https://togithub.com/evanw/esbuild/issues/2445))
This release fixes the handling of spread arguments in the optimization of `/* @__PURE__ */` comments, empty functions, and identity functions:
```js
// Original code
function empty() {}
function identity(x) { return x }
/* @__PURE__ */ a(...x)
/* @__PURE__ */ new b(...x)
empty(...x)
identity(...x)
// Old output (with --minify --tree-shaking=true)
...x;...x;...x;...x;
// New output (with --minify --tree-shaking=true)
function identity(n){return n}[...x];[...x];[...x];identity(...x);
```
Previously esbuild assumed arguments with side effects could be directly inlined. This is almost always true except for spread arguments, which are not syntactically valid on their own and which have the side effect of causing iteration, which might have further side effects. Now esbuild will wrap these elements in an unused array so that they are syntactically valid and so that the iteration side effects are preserved.
### [`v0.14.53`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01453)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.52...v0.14.53)
This release fixes a minor issue with the previous release: I had to rename the package `esbuild-linux-loong64` to `@esbuild/linux-loong64` in the contributed PR because someone registered the package name before I could claim it, and I missed a spot. Hopefully everything is working after this release. I plan to change all platform-specific package names to use the `@esbuild/` scope at some point to avoid this problem in the future.
### [`v0.14.52`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01452)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.51...v0.14.52)
- Allow binary data as input to the JS `transform` and `build` APIs ([#2424](https://togithub.com/evanw/esbuild/issues/2424))
Previously esbuild's `transform` and `build` APIs could only take a string. However, some people want to use esbuild to convert binary data to base64 text. This is problematic because JavaScript strings represent UTF-16 text and esbuild internally operates on arrays of bytes, so all strings coming from JavaScript undergo UTF-16 to UTF-8 conversion before use. This meant that using esbuild in this way was doing base64 encoding of the UTF-8 encoding of the text, which was undesired.
With this release, esbuild now accepts `Uint8Array` in addition to string as an input format for the `transform` and `build` APIs. Now you can use esbuild to convert binary data to base64 text:
```js
// Original code
import esbuild from 'esbuild'
console.log([
(await esbuild.transform('\xFF', { loader: 'base64' })).code,
(await esbuild.build({ stdin: { contents: '\xFF', loader: 'base64' }, write: false })).outputFiles[0].text,
])
console.log([
(await esbuild.transform(new Uint8Array([0xFF]), { loader: 'base64' })).code,
(await esbuild.build({ stdin: { contents: new Uint8Array([0xFF]), loader: 'base64' }, write: false })).outputFiles[0].text,
])
// Old output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
/* ERROR: The input to "transform" must be a string */
// New output
[ 'module.exports = "w78=";\n', 'module.exports = "w78=";\n' ]
[ 'module.exports = "/w==";\n', 'module.exports = "/w==";\n' ]
```
- Update the getter for `text` in build results ([#2423](https://togithub.com/evanw/esbuild/issues/2423))
Output files in build results returned from esbuild's JavaScript API have both a `contents` and a `text` property to return the contents of the output file. The `contents` property is a binary UTF-8 Uint8Array and the `text` property is a JavaScript UTF-16 string. The `text` property is a getter that does the UTF-8 to UTF-16 conversion only if it's needed for better performance.
Previously if you mutate the build results object, you had to overwrite both `contents` and `text` since the value returned from the `text` getter is the original text returned by esbuild. Some people find this confusing so with this release, the getter for `text` has been updated to do the UTF-8 to UTF-16 conversion on the current value of the `contents` property instead of the original value.
- Publish builds for Linux LoongArch 64-bit ([#1804](https://togithub.com/evanw/esbuild/issues/1804), [#2373](https://togithub.com/evanw/esbuild/pull/2373))
This release upgrades to [Go 1.19](https://go.dev/doc/go1.19), which now includes support for LoongArch 64-bit processors. LoongArch 64-bit builds of esbuild will now be published to npm, which means that in theory they can now be installed with `npm install esbuild`. This was contributed by [@beyond-1234](https://togithub.com/beyond-1234).
### [`v0.14.51`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01451)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.50...v0.14.51)
- Add support for React 17's `automatic` JSX transform ([#334](https://togithub.com/evanw/esbuild/issues/334), [#718](https://togithub.com/evanw/esbuild/issues/718), [#1172](https://togithub.com/evanw/esbuild/issues/1172), [#2318](https://togithub.com/evanw/esbuild/issues/2318), [#2349](https://togithub.com/evanw/esbuild/pull/2349))
This adds support for the [new "automatic" JSX runtime from React 17+](https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html) to esbuild for both the build and transform APIs.
**New CLI flags and API options:**
- `--jsx`, `jsx` — Set this to `"automatic"` to opt in to this new transform
- `--jsx-dev`, `jsxDev` — Toggles development mode for the automatic runtime
- `--jsx-import-source`, `jsxImportSource` — Overrides the root import for runtime functions (default `"react"`)
**New JSX pragma comments:**
- `@jsxRuntime` — Sets the runtime (`automatic` or `classic`)
- `@jsxImportSource` — Sets the import source (only valid with automatic runtime)
The existing `@jsxFragment` and `@jsxFactory` pragma comments are only valid with "classic" runtime.
**TSConfig resolving:**
Along with accepting the new options directly via CLI or API, option inference from `tsconfig.json` compiler options was also implemented:
- `"jsx": "preserve"` or `"jsx": "react-native"` → Same as `--jsx=preserve` in esbuild
- `"jsx": "react"` → Same as `--jsx=transform` in esbuild (which is the default behavior)
- `"jsx": "react-jsx"` → Same as `--jsx=automatic` in esbuild
- `"jsx": "react-jsxdev"` → Same as `--jsx=automatic --jsx-dev` in esbuild
It also reads the value of `"jsxImportSource"` from `tsconfig.json` if specified.
For `react-jsx` it's important to note that it doesn't implicitly disable `--jsx-dev`. This is to support the case where a user sets `"react-jsx"` in their `tsconfig.json` but then toggles development mode directly in esbuild.
**esbuild vs Babel vs TS vs...**
There are a few differences between the various technologies that implement automatic JSX runtimes. The JSX transform in esbuild follows a mix of Babel's and TypeScript's behavior:
- When an element has `__source` or `__self` props:
- Babel: Print an error about a deprecated transform plugin
- TypeScript: Allow the props
- swc: Hard crash
- **esbuild**: Print an error — Following Babel was chosen for this one because this might help people catch configuration issues where JSX files are being parsed by multiple tools
- Element has an "implicit true" key prop, e.g. ``:
- Babel: Print an error indicating that "key" props require an explicit value
- TypeScript: Silently omit the "key" prop
- swc: Hard crash
- **esbuild**: Print an error like Babel — This might help catch legitimate programming mistakes
- Element has spread children, e.g. `{...children}`
- Babel: Print an error stating that React doesn't support spread children
- TypeScript: Use static jsx function and pass children as-is, including spread operator
- swc: same as Babel
- **esbuild**: Same as TypeScript
Also note that TypeScript has some bugs regarding JSX development mode and the generation of `lineNumber` and `columnNumber` values. Babel's values are accurate though, so esbuild's line and column numbers match Babel. Both numbers are 1-based and columns are counted in terms of UTF-16 code units.
This feature was contributed by [@jgoz](https://togithub.com/jgoz).
### [`v0.14.50`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01450)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.49...v0.14.50)
- Emit `names` in source maps ([#1296](https://togithub.com/evanw/esbuild/issues/1296))
The [source map specification](https://sourcemaps.info/spec.html) includes an optional `names` field that can associate an identifier with a mapping entry. This can be used to record the original name for an identifier, which is useful if the identifier was renamed to something else in the generated code. When esbuild was originally written, this field wasn't widely used, but now there are some debuggers that make use of it to provide better debugging of minified code. With this release, esbuild now includes a `names` field in the source maps that it generates. To save space, the original name is only recorded when it's different from the final name.
- Update parser for arrow functions with initial default type parameters in `.tsx` files ([#2410](https://togithub.com/evanw/esbuild/issues/2410))
TypeScript 4.6 introduced a [change to the parsing of JSX syntax in `.tsx` files](https://togithub.com/microsoft/TypeScript/issues/47062). Now a `<` token followed by an identifier and then a `=` token is parsed as an arrow function with a default type parameter instead of as a JSX element. This release updates esbuild's parser to match TypeScript's parser.
- Fix an accidental infinite loop with `--define` substitution ([#2407](https://togithub.com/evanw/esbuild/issues/2407))
This is a fix for a regression that was introduced in esbuild version 0.14.44 where certain `--define` substitutions could result in esbuild crashing with a stack overflow. The problem was an incorrect fix for [#2292](https://togithub.com/evanw/esbuild/issues/2292). The fix merged the code paths for `--define` and `--jsx-factory` rewriting since the value substitution is now the same for both. However, doing this accidentally made `--define` substitution recursive since the JSX factory needs to be able to match against `--define` substitutions to integrate with the `--inject` feature. The fix is to only do one additional level of matching against define substitutions, and to only do this for JSX factories. Now these cases are able to build successfully without a stack overflow.
- Include the "public path" value in hashes ([#2403](https://togithub.com/evanw/esbuild/issues/2403))
The `--public-path=` configuration value affects the paths that esbuild uses to reference files from other files and is used in various situations such as cross-chunk imports in JS and references to asset files from CSS files. However, it wasn't included in the hash calculations used for file names due to an oversight. This meant that changing the public path setting incorrectly didn't result in the hashes in file names changing even though the contents of the files changed. This release fixes the issue by including a hash of the public path in all non-asset output files.
- Fix a cross-platform consistency bug ([#2383](https://togithub.com/evanw/esbuild/issues/2383))
Previously esbuild would minify `0xFFFF_FFFF_FFFF_FFFF` as `0xffffffffffffffff` (18 bytes) on arm64 chips and as `18446744073709552e3` (19 bytes) on x86\_64 chips. The reason was that the number was converted to a 64-bit unsigned integer internally for printing as hexadecimal, the 64-bit floating-point number `0xFFFF_FFFF_FFFF_FFFF` is actually `0x1_0000_0000_0000_0180` (i.e. it's rounded up, not down), and converting `float64` to `uint64` is implementation-dependent in Go when the input is out of bounds. This was fixed by changing the upper limit for which esbuild uses hexadecimal numbers during minification to `0xFFFF_FFFF_FFFF_F800`, which is the next representable 64-bit floating-point number below `0x1_0000_0000_0000_0180`, and which fits in a `uint64`. As a result, esbuild will now consistently never minify `0xFFFF_FFFF_FFFF_FFFF` as `0xffffffffffffffff` anymore, which means the output should now be consistent across platforms.
- Fix a hang with the synchronous API when the package is corrupted ([#2396](https://togithub.com/evanw/esbuild/issues/2396))
An error message is already thrown when the esbuild package is corrupted and esbuild can't be run. However, if you are using a synchronous call in the JavaScript API in worker mode, esbuild will use a child worker to initialize esbuild once so that the overhead of initializing esbuild can be amortized across multiple synchronous API calls. However, errors thrown during initialization weren't being propagated correctly which resulted in a hang while the main thread waited forever for the child worker to finish initializing. With this release, initialization errors are now propagated correctly so calling a synchronous API call when the package is corrupted should now result in an error instead of a hang.
- Fix `tsconfig.json` files that collide with directory names ([#2411](https://togithub.com/evanw/esbuild/issues/2411))
TypeScript lets you write `tsconfig.json` files with `extends` clauses that refer to another config file using an implicit `.json` file extension. However, if the config file without the `.json` extension existed as a directory name, esbuild and TypeScript had different behavior. TypeScript ignores the directory and continues looking for the config file by adding the `.json` extension while esbuild previously terminated the search and then failed to load the config file (because it's a directory). With this release, esbuild will now ignore exact matches when resolving `extends` fields in `tsconfig.json` files if the exact match results in a directory.
- Add `platform` to the transform API ([#2362](https://togithub.com/evanw/esbuild/issues/2362))
The `platform` option is mainly relevant for bundling because it mostly affects path resolution (e.g. activating the `"browser"` field in `package.json` files), so it was previously only available for the build API. With this release, it has additionally be made available for the transform API for a single reason: you can now set `--platform=node` when transforming a string so that esbuild will add export annotations for node, which is only relevant when `--format=cjs` is also present.
This has to do with an implementation detail of node that parses the AST of CommonJS files to discover named exports when importing CommonJS from ESM. However, this new addition to esbuild's API is of questionable usefulness. Node's loader API (the main use case for using esbuild's transform API like this) actually bypasses the content returned from the loader and parses the AST that's present on the file system, so you won't actually be able to use esbuild's API for this. See the linked issue for more information.
### [`v0.14.49`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01449)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.48...v0.14.49)
- Keep inlined constants when direct `eval` is present ([#2361](https://togithub.com/evanw/esbuild/issues/2361))
Version 0.14.19 of esbuild added inlining of certain `const` variables during minification, which replaces all references to the variable with the initializer and then removes the variable declaration. However, this could generate incorrect code when direct `eval` is present because the direct `eval` could reference the constant by name. This release fixes the problem by preserving the `const` variable declaration in this case:
```js
// Original code
console.log((() => { const x = 123; return x + eval('x') }))
// Old output (with --minify)
console.log(()=>123+eval("x"));
// New output (with --minify)
console.log(()=>{const x=123;return 123+eval("x")});
```
- Fix an incorrect error in TypeScript when targeting ES5 ([#2375](https://togithub.com/evanw/esbuild/issues/2375))
Previously when compiling TypeScript code to ES5, esbuild could incorrectly consider the following syntax forms as a transformation error:
```ts
0 ? ([]) : 1 ? ({}) : 2;
```
The error messages looked like this:
✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet
example.ts:1:5:
1 │ 0 ? ([]) : 1 ? ({}) : 2;
╵ ^
✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet
example.ts:1:16:
1 │ 0 ? ([]) : 1 ? ({}) : 2;
╵ ^
These parenthesized literals followed by a colon look like the start of an arrow function expression followed by a TypeScript return type (e.g. `([]) : 1` could be the start of the TypeScript arrow function `([]): 1 => 1`). Unlike in JavaScript, parsing arrow functions in TypeScript requires backtracking. In this case esbuild correctly determined that this expression wasn't an arrow function after all but the check for destructuring was incorrectly not covered under the backtracking process. With this release, the error message is now only reported if the parser successfully parses an arrow function without backtracking.
- Fix generated TypeScript `enum` comments containing `*/` ([#2369](https://togithub.com/evanw/esbuild/issues/2369), [#2371](https://togithub.com/evanw/esbuild/pull/2371))
TypeScript `enum` values that are equal to a number or string literal are inlined (references to the enum are replaced with the literal value) and have a `/* ... */` comment after them with the original enum name to improve readability. However, this comment is omitted if the enum name contains the character sequence `*/` because that would end the comment early and cause a syntax error:
```ts
// Original TypeScript
enum Foo { '/*' = 1, '*/' = 2 }
console.log(Foo['/*'], Foo['*/'])
// Generated JavaScript
console.log
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
[ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
4.3.1->4.3.34.14.182->4.14.18414.18.21->14.18.2410.0.12->10.0.135.30.4->5.33.15.30.4->5.33.10.14.48->0.15.58.19.0->8.22.05.1.6->5.4.35.73.0->5.74.0Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.33.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5331-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5330v5331-2022-08-15) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.33.0...v5.33.1) ##### Bug Fixes - missing placeholders in violation messages for `no-unnecessary-type-constraint` and `no-unsafe-argument` (and enable `eslint-plugin/recommended` rules internally) ([#5453](https://togithub.com/typescript-eslint/typescript-eslint/issues/5453)) ([d023910](https://togithub.com/typescript-eslint/typescript-eslint/commit/d0239104f4dbffd2b5ecdb19e520c7d4b71962e0)) ### [`v5.33.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5330-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5320v5330-2022-08-08) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.32.0...v5.33.0) ##### Bug Fixes - **eslint-plugin:** \[no-extra-parens] handle await with type assertion ([#5428](https://togithub.com/typescript-eslint/typescript-eslint/issues/5428)) ([e03826f](https://togithub.com/typescript-eslint/typescript-eslint/commit/e03826f08ce8bfdd6d6702025d975cfb7d867097)) - **website:** add explicit frontmatter description to rule docs ([#5429](https://togithub.com/typescript-eslint/typescript-eslint/issues/5429)) ([63cba5f](https://togithub.com/typescript-eslint/typescript-eslint/commit/63cba5f4c1884e102927b3b14b18a00e96ac63a1)) ##### Features - **eslint-plugin:** \[member-ordering] support static blocks ([#5417](https://togithub.com/typescript-eslint/typescript-eslint/issues/5417)) ([5983e5a](https://togithub.com/typescript-eslint/typescript-eslint/commit/5983e5ab3bfb94fec782bea54a37457fe31db545)) - **eslint-plugin:** \[prefer-as-const] adds support for class properties ([#5413](https://togithub.com/typescript-eslint/typescript-eslint/issues/5413)) ([d2394f8](https://togithub.com/typescript-eslint/typescript-eslint/commit/d2394f810960fda07b9c8affd47b769d16f4b8cb)) ### [`v5.32.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5320-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5310v5320-2022-08-01) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.31.0...v5.32.0) ##### Features - **eslint-plugin:** \[no-use-before-define] add "allowNamedExports" option ([#5397](https://togithub.com/typescript-eslint/typescript-eslint/issues/5397)) ([ad412cd](https://togithub.com/typescript-eslint/typescript-eslint/commit/ad412cdd74dc5619fbe4bf27c0a5eb5c5a4b65ca)) ### [`v5.31.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5310-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5307v5310-2022-07-25) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.7...v5.31.0) ##### Bug Fixes - **eslint-plugin:** \[typedef] Support nested array destructuring with type annotation ([#5311](https://togithub.com/typescript-eslint/typescript-eslint/issues/5311)) ([6d19efe](https://togithub.com/typescript-eslint/typescript-eslint/commit/6d19efed16d1cf0357ad363b6373d2021c49a8c8)) - **scope-manager:** handle typeParameters of TSInstantiationExpression ([#5355](https://togithub.com/typescript-eslint/typescript-eslint/issues/5355)) ([2595ccf](https://togithub.com/typescript-eslint/typescript-eslint/commit/2595ccf67cd5158edbd6bebd9ac2dbd8bbd8b99c)) ##### Features - **eslint-plugin:** \[consistent-generic-ctors] check class field declaration ([#5288](https://togithub.com/typescript-eslint/typescript-eslint/issues/5288)) ([48f996e](https://togithub.com/typescript-eslint/typescript-eslint/commit/48f996e8dda79c9c865e8ca6552069902836648b)) - **eslint-plugin:** \[prefer-nullish-coalescing] add ignoreTernaryTests option ([#4965](https://togithub.com/typescript-eslint/typescript-eslint/issues/4965)) ([f82727f](https://togithub.com/typescript-eslint/typescript-eslint/commit/f82727ffeb97475c07773ca1d1e5b9609fcc5e68)) #### [5.30.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) (2022-07-18) ##### Bug Fixes - **eslint-plugin:** \[no-inferrable] fix optional param to valid code ([#5342](https://togithub.com/typescript-eslint/typescript-eslint/issues/5342)) ([98f6d5e](https://togithub.com/typescript-eslint/typescript-eslint/commit/98f6d5e6d08d1eb9789da52a15f337f5f53438bd)) - **eslint-plugin:** \[no-unused-vars] highlight last write reference ([#5267](https://togithub.com/typescript-eslint/typescript-eslint/issues/5267)) ([c3f199a](https://togithub.com/typescript-eslint/typescript-eslint/commit/c3f199a65a16aa72f5bb83e81a1ce0ffb5f69772)) #### [5.30.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) (2022-07-11) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.30.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) (2022-07-04) ##### Bug Fixes - **eslint-plugin:** \[consistent-indexed-object-style] fix record mode fixer for generics with a default value ([#5280](https://togithub.com/typescript-eslint/typescript-eslint/issues/5280)) ([57f032c](https://togithub.com/typescript-eslint/typescript-eslint/commit/57f032c2e6a822c049177713778d0077ee138d9a)) #### [5.30.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.3...v5.30.4) (2022-07-03) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.30.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.2...v5.30.3) (2022-07-01) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.30.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.1...v5.30.2) (2022-07-01) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) #### [5.30.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.0...v5.30.1) (2022-07-01) ##### Bug Fixes - **eslint-plugin:** \[no-base-to-string] add missing apostrophe to message ([#5270](https://togithub.com/typescript-eslint/typescript-eslint/issues/5270)) ([d320174](https://togithub.com/typescript-eslint/typescript-eslint/commit/58034e343a167ca7751b54d2b2a0e7d3852aabec)) ### [`v5.30.7`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5307-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5306v5307-2022-07-18) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) ##### Bug Fixes - **eslint-plugin:** \[no-inferrable] fix optional param to valid code ([#5342](https://togithub.com/typescript-eslint/typescript-eslint/issues/5342)) ([98f6d5e](https://togithub.com/typescript-eslint/typescript-eslint/commit/98f6d5e6d08d1eb9789da52a15f337f5f53438bd)) - **eslint-plugin:** \[no-unused-vars] highlight last write reference ([#5267](https://togithub.com/typescript-eslint/typescript-eslint/issues/5267)) ([c3f199a](https://togithub.com/typescript-eslint/typescript-eslint/commit/c3f199a65a16aa72f5bb83e81a1ce0ffb5f69772)) ### [`v5.30.6`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5306-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5305v5306-2022-07-11) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) **Note:** Version bump only for package [@typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) ### [`v5.30.5`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5305-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5304v5305-2022-07-04) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) ##### Bug Fixes - **eslint-plugin:** \[consistent-indexed-object-style] fix record mode fixer for generics with a default value ([#5280](https://togithub.com/typescript-eslint/typescript-eslint/issues/5280)) ([57f032c](https://togithub.com/typescript-eslint/typescript-eslint/commit/57f032c2e6a822c049177713778d0077ee138d9a))typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.33.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5331-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5330v5331-2022-08-15) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.33.0...v5.33.1) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.33.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5330-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5320v5330-2022-08-08) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.32.0...v5.33.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.32.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5320-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5310v5320-2022-08-01) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.31.0...v5.32.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.31.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5310-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5307v5310-2022-07-25) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.7...v5.31.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.30.7](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) (2022-07-18) ##### Bug Fixes - expose types supporting old versions of typescript ([#5339](https://togithub.com/typescript-eslint/typescript-eslint/issues/5339)) ([4ba9bdb](https://togithub.com/typescript-eslint/typescript-eslint/commit/4ba9bdb93f87e6bc370f13aa1de48f435abe3f88)) #### [5.30.6](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) (2022-07-11) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.30.5](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) (2022-07-04) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.30.4](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.3...v5.30.4) (2022-07-03) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.30.3](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.2...v5.30.3) (2022-07-01) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.30.2](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.1...v5.30.2) (2022-07-01) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### 5.30.1 (2022-07-01) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.30.7`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5307-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5306v5307-2022-07-18) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.6...v5.30.7) ##### Bug Fixes - expose types supporting old versions of typescript ([#5339](https://togithub.com/typescript-eslint/typescript-eslint/issues/5339)) ([4ba9bdb](https://togithub.com/typescript-eslint/typescript-eslint/commit/4ba9bdb93f87e6bc370f13aa1de48f435abe3f88)) ### [`v5.30.6`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5306-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5305v5306-2022-07-11) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.5...v5.30.6) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.30.5`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5305-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5304v5305-2022-07-04) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.30.4...v5.30.5) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)evanw/esbuild
### [`v0.15.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0155) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.4...v0.15.5) - Fix issues with Yarn PnP and Yarn's workspaces feature ([#2476](https://togithub.com/evanw/esbuild/issues/2476)) This release makes sure esbuild works with a Yarn feature called [workspaces](https://yarnpkg.com/features/workspaces/). Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix `exports` map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working. ### [`v0.15.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0154) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.3...v0.15.4) - Consider TypeScript import assignments to be side-effect free ([#2468](https://togithub.com/evanw/esbuild/issues/2468)) TypeScript has a [legacy import syntax](https://www.typescriptlang.org/docs/handbook/namespaces.html#aliases) for working with TypeScript namespaces that looks like this: ```ts import { someNamespace } from './some-file' import bar = someNamespace.foo; // some-file.ts export namespace someNamespace { export let foo = 123 } ``` Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if `bar` is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps `bar` in the output, which is done because `someNamespace.foo` is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case). With this release, esbuild will now consider `someNamespace.foo` to have no side effects. This means `bar` will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of `bar`, so it would be incorrect to remove it. If you want `bar` to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output). - Change the order of the banner and the `"use strict"` directive ([#2467](https://togithub.com/evanw/esbuild/issues/2467)) Previously the top of the file contained the following things in order: 1. The hashbang comment (see below) from the source code, if present 2. The `"use strict"` directive from the source code, if present 3. The content of esbuild's `banner` API option, if specified This was problematic for people that used the `banner` API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to: 1. The hashbang comment (see below) from the source code, if present 2. The content of esbuild's `banner` API option, if specified 3. The `"use strict"` directive from the source code, if present I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the `banner` API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the `"use strict"` directive. For context: JavaScript files recently allowed using a [hashbang comment](https://togithub.com/tc39/proposal-hashbang), which starts with `#!` and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the `node` command. This comment typically has the value `#!/usr/bin/env node`. Hashbang comments will be a part of ES2023 when it's released next year. - Fix `exports` maps with Yarn PnP path resolution ([#2473](https://togithub.com/evanw/esbuild/issues/2473)) The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that `exports` in `package.json` is not respected because node's module resolution algorithm doesn't interpret `exports` for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP. ### [`v0.15.3`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0153) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.2...v0.15.3) - Change the Yarn PnP manifest to a singleton ([#2463](https://togithub.com/evanw/esbuild/issues/2463)) Previously esbuild searched for the Yarn PnP manifest in the parent directories of each file. But with Yarn's `enableGlobalCache` setting it's possible to configure Yarn PnP's implementation to reach outside of the directory subtree containing the Yarn PnP manifest. This was causing esbuild to fail to bundle projects with the `enableGlobalCache` setting enabled. To handle this case, *esbuild will now only search for the Yarn PnP manifest in the current working directory of the esbuild process*. If you're using esbuild's CLI, this means you will now have to `cd` into the appropriate directory first. If you're using esbuild's API, you can override esbuild's value for the current working directory with the `absWorkingDir` API option. - Fix Yarn PnP resolution failures due to backslashes in paths on Windows ([#2462](https://togithub.com/evanw/esbuild/issues/2462)) Previously dependencies of a Yarn PnP virtual dependency failed to resolve on Windows. This was because Windows uses `\` instead of `/` as a path separator, and the path manipulation algorithms used for Yarn PnP expected `/`. This release converts `\` into `/` in Windows paths, which fixes this issue. - Fix `sideEffects` patterns containing slashes on Windows ([#2465](https://togithub.com/evanw/esbuild/issues/2465)) The `sideEffects` field in `package.json` lets you specify an array of patterns to mark which files have side effects (which causes all other files to be considered to not have side effects by exclusion). That looks like this: ```json "sideEffects": [ "**/index.js", "**/index.prod.js" ] ``` However, the presence of the `/` character in the pattern meant that the pattern failed to match Windows-style paths, which broke `sideEffects` on Windows in this case. This release fixes this problem by adding additional code to handle Windows-style paths. ### [`v0.15.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0152) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.1...v0.15.2) - Fix Yarn PnP issue with packages containing `index.js` ([#2455](https://togithub.com/evanw/esbuild/issues/2455), [#2461](https://togithub.com/evanw/esbuild/issues/2461)) Yarn PnP's tests require the resolved paths to end in `/`. That's not how the rest of esbuild's internals work, however, and doing this messed up esbuild's node module path resolution regarding automatically-detected `index.js` files. Previously packages that relied on implicit `index.js` resolution rules didn't work with esbuild under Yarn PnP. Removing this slash has fixed esbuild's path resolution behavior regarding `index.js`, which should now the same both with and without Yarn PnP. - Fix Yarn PnP support for `extends` in `tsconfig.json` ([#2456](https://togithub.com/evanw/esbuild/issues/2456)) Previously using `extends` in `tsconfig.json` with a path in a Yarn PnP package didn't work. This is because the process of setting up package path resolution rules requires parsing `tsconfig.json` files (due to the `baseUrl` and `paths` features) and resolving `extends` to a package path requires package path resolution rules to already be set up, which is a circular dependency. This cycle is broken by using special rules for `extends` in `tsconfig.json` that bypasses esbuild's normal package path resolution process. This is why using `extends` with a Yarn PnP package didn't automatically work. With this release, these special rules have been modified to check for a Yarn PnP manifest so this case should work now. - Fix Yarn PnP support in `esbuild-wasm` ([#2458](https://togithub.com/evanw/esbuild/issues/2458)) When running esbuild via WebAssembly, Yarn PnP support previously failed because Go's file system internals return `EINVAL` when trying to read a `.zip` file as a directory when run with WebAssembly. This was unexpected because Go's file system internals return `ENOTDIR` for this case on native. This release updates esbuild to treat `EINVAL` like `ENOTDIR` in this case, which fixes using `esbuild-wasm` to bundle a Yarn PnP project. Note that to be able to use `esbuild-wasm` for Yarn PnP successfully, you currently have to run it using `node` instead of `yarn node`. This is because the file system shim that Yarn overwrites node's native file system API with currently generates invalid file descriptors with negative values when inside a `.zip` file. This prevents esbuild from working correctly because Go's file system internals don't expect syscalls that succeed without an error to return an invalid file descriptor. Yarn is working on fixing their use of invalid file descriptors. ### [`v0.15.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0151) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.15.0...v0.15.1) - Update esbuild's Yarn Plug'n'Play implementation to match the latest specification changes ([#2452](https://togithub.com/evanw/esbuild/issues/2452), [#2453](https://togithub.com/evanw/esbuild/pull/2453)) This release updates esbuild's implementation of Yarn Plug'n'Play to match some changes to Yarn's specification that just landed. The changes are as follows: - Check for platform-specific absolute paths instead of always for the `/` prefix The specification previously said that Yarn Plug'n'Play path resolution rules should not apply for paths that start with `/`. The intent was to avoid accidentally processing absolute paths. However, absolute paths on Windows such as `C:\project` start with drive letters instead of with `/`. So the specification was changed to instead explicitly avoid processing absolute paths. - Make `$$virtual` an alias for `__virtual__` Supporting Yarn-style path resolution requires implementing a custom Yarn-specific path traversal scheme where certain path segments are considered no-ops. Specifically any path containing segments of the form `__virtual__/Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 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.