typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5130-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5121v5130-2022-02-28)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.1...v5.13.0)
##### Bug Fixes
- **eslint-plugin:** \[sort-type-union-intersection-members] Wrap the constructorType in parentheses ([#4590](https://togithub.com/typescript-eslint/typescript-eslint/issues/4590)) ([851bb90](https://togithub.com/typescript-eslint/typescript-eslint/commit/851bb90216e20b7679efc891dc445e6152d4837f))
##### Features
- **eslint-plugin:** \[no-misused-promises] check more places for checksVoidReturn ([#4541](https://togithub.com/typescript-eslint/typescript-eslint/issues/4541)) ([052cf51](https://togithub.com/typescript-eslint/typescript-eslint/commit/052cf51fe663283afe89dc7bf97c947e750df095))
- **eslint-plugin:** add `no-redundant-type-constituents` rule ([#4378](https://togithub.com/typescript-eslint/typescript-eslint/issues/4378)) ([63d051e](https://togithub.com/typescript-eslint/typescript-eslint/commit/63d051eed29dcf71015a23992feac0a8f92717a0))
- **eslint-plugin:** add `no-useless-empty-export` rule ([#4380](https://togithub.com/typescript-eslint/typescript-eslint/issues/4380)) ([823b945](https://togithub.com/typescript-eslint/typescript-eslint/commit/823b945c8f9e83d0246a2a5d07519f01e1a64518))
- **eslint-plugin:** add extension rule `space-before-blocks` ([#1606](https://togithub.com/typescript-eslint/typescript-eslint/issues/1606)) ([#4184](https://togithub.com/typescript-eslint/typescript-eslint/issues/4184)) ([208b6d0](https://togithub.com/typescript-eslint/typescript-eslint/commit/208b6d02252dff2bf272329d3e4a4a82e56c52c0))
- **eslint-plugin:** added member group support to member-ordering rule ([#4538](https://togithub.com/typescript-eslint/typescript-eslint/issues/4538)) ([6afcaea](https://togithub.com/typescript-eslint/typescript-eslint/commit/6afcaea0160a1ccd1c6483ca677c544ca1b8cb4f))
#### [5.12.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) (2022-02-21)
##### Bug Fixes
- **eslint-plugin:** \[no-unnecessary-type-arguments] fix comparison of types ([#4555](https://togithub.com/typescript-eslint/typescript-eslint/issues/4555)) ([fc3936e](https://togithub.com/typescript-eslint/typescript-eslint/commit/fc3936e99712374a707ce9e0101bc641807b9ea6))
### [`v5.12.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5121-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5120v5121-2022-02-21)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1)
##### Bug Fixes
- **eslint-plugin:** \[no-unnecessary-type-arguments] fix comparison of types ([#4555](https://togithub.com/typescript-eslint/typescript-eslint/issues/4555)) ([fc3936e](https://togithub.com/typescript-eslint/typescript-eslint/commit/fc3936e99712374a707ce9e0101bc641807b9ea6))
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5130-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5121v5130-2022-02-28)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.1...v5.13.0)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
#### [5.12.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) (2022-02-21)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
### [`v5.12.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5121-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5120v5121-2022-02-21)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1)
**Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
evanw/esbuild
### [`v0.14.25`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01425)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.24...v0.14.25)
- Reduce minification of CSS transforms to avoid Safari bugs ([#2057](https://togithub.com/evanw/esbuild/issues/2057))
In Safari, applying a 3D CSS transform to an element can cause it to render in a different order than applying a 2D CSS transform even if the transformation matrix is identical. I believe this is a bug in Safari because the [CSS `transform` specification](https://drafts.csswg.org/css-transforms-1/#transform-rendering) doesn't seem to distinguish between 2D and 3D transforms as far as rendering order:
> For elements whose layout is governed by the CSS box model, any value other than `none` for the `transform` property results in the creation of a stacking context.
This bug means that minifying a 3D transform into a 2D transform must be avoided even though it's a valid transformation because it can cause rendering differences in Safari. Previously esbuild sometimes minified 3D CSS transforms into 2D CSS transforms but with this release, esbuild will no longer do that:
```css
/* Original code */
div { transform: matrix3d(2, 0, 0, 0, 0, 2, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1) }
/* Old output (with --minify) */
div{transform:scale(2)}
/* New output (with --minify) */
div{transform:scale3d(2,2,1)}
```
- Minification now takes advantage of the `?.` operator
This adds new code minification rules that shorten code with the `?.` optional chaining operator when the result is equivalent:
```ts
// Original code
let foo = (x) => {
if (x !== null && x !== undefined) x.y()
return x === null || x === undefined ? undefined : x.z
}
// Old output (with --minify)
let foo=n=>(n!=null&&n.y(),n==null?void 0:n.z);
// New output (with --minify)
let foo=n=>(n?.y(),n?.z);
```
This only takes effect when minification is enabled and when the configured target environment is known to support the optional chaining operator. As always, make sure to set `--target=` to the appropriate language target if you are running the minified code in an environment that doesn't support the latest JavaScript features.
- Add source mapping information for some non-executable tokens ([#1448](https://togithub.com/evanw/esbuild/issues/1448))
Code coverage tools can generate reports that tell you if any code exists that has not been run (or "covered") during your tests. You can use this information to add additional tests for code that isn't currently covered.
Some popular JavaScript code coverage tools have bugs where they incorrectly consider lines without any executable code as uncovered, even though there's no test you could possibly write that would cause those lines to be executed. For example, they apparently complain about the lines that only contain the trailing `}` token of an object literal.
With this release, esbuild now generates source mappings for some of these trailing non-executable tokens. This may not successfully work around bugs in code coverage tools because there are many non-executable tokens in JavaScript and esbuild doesn't map them all (the drawback of mapping these extra tokens is that esbuild will use more memory, build more slowly, and output a bigger source map). The true solution is to fix the bugs in the code coverage tools in the first place.
- Fall back to WebAssembly on Android x64 ([#2068](https://togithub.com/evanw/esbuild/issues/2068))
Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android x64 without installing the Android build tools. So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the `esbuild-wasm` package but it's installed automatically when you install the `esbuild` package on Android x64. So packages that depend on the `esbuild` package should now work on Android x64. If you want to use a native binary executable of esbuild on Android x64, you may be able to build it yourself from source after installing the Android build tools.
- Update to Go 1.17.8
The version of the Go compiler used to compile esbuild has been upgraded from Go 1.17.7 to Go 1.17.8, which fixes the RISC-V 64-bit build. Compiler optimizations for the RISC-V 64-bit build have now been re-enabled.
### [`v0.14.24`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01424)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.23...v0.14.24)
- Allow `es2022` as a target environment ([#2012](https://togithub.com/evanw/esbuild/issues/2012))
TypeScript recently [added support for `es2022`](https://devblogs.microsoft.com/typescript/announcing-typescript-4-6/#target-es2022) as a compilation target so esbuild now supports this too. Support for this is preliminary as there is no published ES2022 specification yet (i.e. https://tc39.es/ecma262/2021/ exists but https://tc39.es/ecma262/2022/ is a 404 error). The meaning of esbuild's `es2022` target may change in the future when the specification is finalized. Right now I have made the `es2022` target enable support for the syntax-related [finished proposals](https://togithub.com/tc39/proposals/blob/main/finished-proposals.md) that are marked as `2022`:
- Class fields
- Class private members
- Class static blocks
- Ergonomic class private member checks
- Top-level await
I have also included the "arbitrary module namespace names" feature since I'm guessing it will end up in the ES2022 specification (this syntax feature was added to the specification without a proposal). TypeScript has [not added support for this yet](https://togithub.com/microsoft/TypeScript/issues/40594).
- Match `define` to strings in index expressions ([#2050](https://togithub.com/evanw/esbuild/issues/2050))
With this release, configuring `--define:foo.bar=baz` now matches and replaces both `foo.bar` and `foo['bar']` expressions in the original source code. This is necessary for people who have enabled TypeScript's [`noPropertyAccessFromIndexSignature` feature](https://www.typescriptlang.org/tsconfig#noPropertyAccessFromIndexSignature), which prevents you from using normal property access syntax on a type with an index signature such as in the following code:
```ts
declare let foo: { [key: string]: any }
foo.bar // This is a type error if noPropertyAccessFromIndexSignature is enabled
foo['bar']
```
Previously esbuild would generate the following output with `--define:foo.bar=baz`:
```js
baz;
foo["bar"];
```
Now esbuild will generate the following output instead:
```js
baz;
baz;
```
- Add `--mangle-quoted` to mangle quoted properties ([#218](https://togithub.com/evanw/esbuild/issues/218))
The `--mangle-props=` flag tells esbuild to automatically rename all properties matching the provided regular expression to shorter names to save space. Previously esbuild never modified the contents of string literals. In particular, `--mangle-props=_` would mangle `foo._bar` but not `foo['_bar']`. There are some coding patterns where renaming quoted property names is desirable, such as when using TypeScript's [`noPropertyAccessFromIndexSignature` feature](https://www.typescriptlang.org/tsconfig#noPropertyAccessFromIndexSignature) or when using TypeScript's [discriminated union narrowing behavior](https://www.typescriptlang.org/docs/handbook/2/narrowing.html#discriminated-unions):
```ts
interface Foo { _foo: string }
interface Bar { _bar: number }
declare const value: Foo | Bar
console.log('_foo' in value ? value._foo : value._bar)
```
The `'_foo' in value` check tells TypeScript to narrow the type of `value` to `Foo` in the true branch and to `Bar` in the false branch. Previously esbuild didn't mangle the property name `'_foo'` because it was inside a string literal. With this release, you can now use `--mangle-quoted` to also rename property names inside string literals:
```js
// Old output (with --mangle-props=_)
console.log("_foo" in value ? value.a : value.b);
// New output (with --mangle-props=_ --mangle-quoted)
console.log("a" in value ? value.a : value.b);
```
- Parse and discard TypeScript `export as namespace` statements ([#2070](https://togithub.com/evanw/esbuild/issues/2070))
TypeScript `.d.ts` type declaration files can sometimes contain statements of the form `export as namespace foo;`. I believe these serve to declare that the module adds a property of that name to the global object. You aren't supposed to feed `.d.ts` files to esbuild so this normally doesn't matter, but sometimes esbuild can end up having to parse them. One such case is if you import a type-only package who's `main` field in `package.json` is a `.d.ts` file.
Previously esbuild only allowed `export as namespace` statements inside a `declare` context:
```ts
declare module Foo {
export as namespace foo;
}
```
Now esbuild will also allow these statements outside of a `declare` context:
```ts
export as namespace foo;
```
These statements are still just ignored and discarded.
- Strip import assertions from unrecognized `import()` expressions ([#2036](https://togithub.com/evanw/esbuild/issues/2036))
The new "import assertions" JavaScript language feature adds an optional second argument to dynamic `import()` expressions, which esbuild does support. However, this optional argument must be stripped when targeting older JavaScript environments for which this second argument would be a syntax error. Previously esbuild failed to strip this second argument in cases when the first argument to `import()` wasn't a string literal. This problem is now fixed:
```js
// Original code
console.log(import(foo, { assert: { type: 'json' } }))
// Old output (with --target=es6)
console.log(import(foo, { assert: { type: "json" } }));
// New output (with --target=es6)
console.log(import(foo));
```
- Remove simplified statement-level literal expressions ([#2063](https://togithub.com/evanw/esbuild/issues/2063))
With this release, esbuild now removes simplified statement-level expressions if the simplified result is a literal expression even when minification is disabled. Previously this was only done when minification is enabled. This change was only made because some people are bothered by seeing top-level literal expressions. This change has no effect on code behavior.
- Ignore `.d.ts` rules in `paths` in `tsconfig.json` files ([#2074](https://togithub.com/evanw/esbuild/issues/2074), [#2075](https://togithub.com/evanw/esbuild/pull/2075))
TypeScript's `tsconfig.json` configuration file has a `paths` field that lets you remap import paths to alternative files on the file system. This field is interpreted by esbuild during bundling so that esbuild's behavior matches that of the TypeScript type checker. However, people sometimes override import paths to JavaScript files to instead point to a `.d.ts` TypeScript type declaration file for that JavaScript file. The intent of this is to just use the remapping for type information and not to actually import the `.d.ts` file during the build.
With this release, esbuild will now ignore rules in `paths` that result in a `.d.ts` file during path resolution. This means code that does this should now be able to be bundled without modifying its `tsconfig.json` file to remove the `.d.ts` rule. This change was contributed by [@magic-akari](https://togithub.com/magic-akari).
- Disable Go compiler optimizations for the Linux RISC-V 64bit build ([#2035](https://togithub.com/evanw/esbuild/pull/2035))
Go's RISC-V 64bit compiler target has a fatal compiler optimization bug that causes esbuild to crash when it's run: [https://github.com/golang/go/issues/51101](https://togithub.com/golang/go/issues/51101). As a temporary workaround until a version of the Go compiler with the fix is published, Go compiler optimizations have been disabled for RISC-V. The 7.7mb esbuild binary executable for RISC-V is now 8.7mb instead. This workaround was contributed by [@piggynl](https://togithub.com/piggynl).
### [`v0.14.23`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01423)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.22...v0.14.23)
- Update feature database to indicate that node 16.14+ supports import assertions ([#2030](https://togithub.com/evanw/esbuild/issues/2030))
Node versions 16.14 and above now support import assertions according to [these release notes](https://togithub.com/nodejs/node/blob/6db686710ee1579452b2908a7a41b91cb729b944/doc/changelogs/CHANGELOG_V16.md#16.14.0). This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with `--target=node16.14`:
```js
// Original code
import data from './package.json' assert { type: 'json' }
console.log(data)
// Old output (with --target=node16.14)
import data from "./package.json";
console.log(data);
// New output (with --target=node16.14)
import data from "./package.json" assert { type: "json" };
console.log(data);
```
- Basic support for CSS `@layer` rules ([#2027](https://togithub.com/evanw/esbuild/issues/2027))
This adds basic parsing support for a new CSS feature called `@layer` that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of `@layer` rules:
```css
/* Original code */
@layer a {
@layer b {
div {
color: yellow;
margin: 0.0px;
}
}
}
/* Old output (with --minify) */
@layer a{@layer b {div {color: yellow; margin: 0px;}}}
/* New output (with --minify) */
@layer a.b{div{color:#ff0;margin:0}}
```
You can read more about `@layer` here:
- Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/[@layer](https://togithub.com/layer)
- Motivation: https://developer.chrome.com/blog/cascade-layers/
Note that the support added in this release is only for parsing and printing `@layer` rules. The bundler does not yet know about these rules and bundling with `@layer` may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the *first* instance while with every other CSS rule, the order is derived from the *last* instance.
### [`v0.14.22`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01422)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.21...v0.14.22)
- Preserve whitespace for token lists that look like CSS variable declarations ([#2020](https://togithub.com/evanw/esbuild/issues/2020))
Previously esbuild removed the whitespace after the CSS variable declaration in the following CSS:
```css
/* Original input */
@supports (--foo: ){html{background:green}}
/* Previous output */
@supports (--foo:){html{background:green}}
```
However, that broke rendering in Chrome as it caused Chrome to ignore the entire rule. This did not break rendering in Firefox and Safari, so there's a browser bug either with Chrome or with both Firefox and Safari. In any case, esbuild now preserves whitespace after the CSS variable declaration in this case.
- Ignore legal comments when merging adjacent duplicate CSS rules ([#2016](https://togithub.com/evanw/esbuild/issues/2016))
This release now generates more compact minified CSS when there are legal comments in between two adjacent rules with identical content:
```css
/* Original code */
a { color: red }
/* @preserve */
b { color: red }
/* Old output (with --minify) */
a{color:red}/* @preserve */b{color:red}
/* New output (with --minify) */
a,b{color:red}/* @preserve */
```
- Block `onResolve` and `onLoad` until `onStart` ends ([#1967](https://togithub.com/evanw/esbuild/issues/1967))
This release changes the semantics of the `onStart` callback. All `onStart` callbacks from all plugins are run concurrently so that a slow plugin doesn't hold up the entire build. That's still the case. However, previously the only thing waiting for the `onStart` callbacks to finish was the end of the build. This meant that `onResolve` and/or `onLoad` callbacks could sometimes run before `onStart` had finished. This was by design but violated user expectations. With this release, all `onStart` callbacks must finish before any `onResolve` and/or `onLoad` callbacks are run.
- Add a self-referential `default` export to the JS API ([#1897](https://togithub.com/evanw/esbuild/issues/1897))
Some people try to use esbuild's API using `import esbuild from 'esbuild'` instead of `import * as esbuild from 'esbuild'` (i.e. using a default import instead of a namespace import). There is no `default` export so that wasn't ever intended to work. But it would work sometimes depending on which tools you used and how they were configured so some people still wrote code this way. This release tries to make that work by adding a self-referential `default` export that is equal to esbuild's module namespace object.
More detail: The published package for esbuild's JS API is in CommonJS format, although the source code for esbuild's JS API is in ESM format. The original ESM code for esbuild's JS API has no export named `default` so using a default import like this doesn't work with Babel-compatible toolchains (since they respect the semantics of the original ESM code). However, it happens to work with node-compatible toolchains because node's implementation of importing CommonJS from ESM broke compatibility with existing conventions and automatically creates a `default` export which is set to `module.exports`. This is an unfortunate compatibility headache because it means the `default` import only works sometimes. This release tries to fix this by explicitly creating a self-referential `default` export. It now doesn't matter if you do `esbuild.build()`, `esbuild.default.build()`, or `esbuild.default.default.build()` because they should all do the same thing. Hopefully this means people don't have to deal with this problem anymore.
- Handle `write` errors when esbuild's child process is killed ([#2007](https://togithub.com/evanw/esbuild/issues/2007))
If you type Ctrl+C in a terminal when a script that uses esbuild's JS library is running, esbuild's child process may be killed before the parent process. In that case calls to the `write()` syscall may fail with an `EPIPE` error. Previously this resulted in an uncaught exception because esbuild didn't handle this case. Starting with this release, esbuild should now catch these errors and redirect them into a general `The service was stopped` error which should be returned from whatever top-level API calls were in progress.
- Better error message when browser WASM bugs are present ([#1863](https://togithub.com/evanw/esbuild/issues/1863))
Safari's WebAssembly implementation appears to be broken somehow, at least when running esbuild. Sometimes this manifests as a stack overflow and sometimes as a Go panic. Previously a Go panic resulted in the error message `Can't find variable: fs` but this should now result in the Go panic being printed to the console. Using esbuild's WebAssembly library in Safari is still broken but now there's a more helpful error message.
More detail: When Go panics, it prints a stack trace to stderr (i.e. file descriptor 2). Go's WebAssembly shim calls out to node's `fs.writeSync()` function to do this, and it converts calls to `fs.writeSync()` into calls to `console.log()` in the browser by providing a shim for `fs`. However, Go's shim code stores the shim on `window.fs` in the browser. This is undesirable because it pollutes the global scope and leads to brittle code that can break if other code also uses `window.fs`. To avoid this, esbuild shadows the global object by wrapping Go's shim. But that broke bare references to `fs` since the shim is no longer stored on `window.fs`. This release now stores the shim in a local variable named `fs` so that bare references to `fs` work correctly.
- Undo incorrect dead-code elimination with destructuring ([#1183](https://togithub.com/evanw/esbuild/issues/1183))
Previously esbuild eliminated these statements as dead code if tree-shaking was enabled:
```js
let [a] = {}
let { b } = null
```
This is incorrect because both of these lines will throw an error when evaluated. With this release, esbuild now preserves these statements even when tree shaking is enabled.
- Update to Go 1.17.7
The version of the Go compiler used to compile esbuild has been upgraded from Go 1.17.6 to Go 1.17.7, which contains a few [compiler and security bug fixes](https://togithub.com/golang/go/issues?q=milestone%3AGo1.17.7+label%3ACherryPickApproved).
eslint/eslint
### [`v8.10.0`](https://togithub.com/eslint/eslint/releases/v8.10.0)
[Compare Source](https://togithub.com/eslint/eslint/compare/v8.9.0...v8.10.0)
#### Features
- [`6e2c325`](https://togithub.com/eslint/eslint/commit/6e2c325324479df1b3f868cf00a529b67d2c3d82) feat: Add `ignoreOnInitialization` option to no-shadow rule ([#14963](https://togithub.com/eslint/eslint/issues/14963)) (Soufiane Boutahlil)
- [`115cae5`](https://togithub.com/eslint/eslint/commit/115cae54125b9ef509af90620f51d4a692b51ab7) feat: `--debug` prints time it takes to parse a file ([#15609](https://togithub.com/eslint/eslint/issues/15609)) (Bartek Iwańczuk)
- [`345e70d`](https://togithub.com/eslint/eslint/commit/345e70d9d6490fb12b18953f56f3cea28fd61d83) feat: Add `onlyOneSimpleParam` option to no-confusing-arrow rule ([#15566](https://togithub.com/eslint/eslint/issues/15566)) (Gautam Arora)
#### Bug Fixes
- [`cdc5802`](https://togithub.com/eslint/eslint/commit/cdc58025d9a8b522f516c3665d225b69a76c4ee1) fix: Avoid `__dirname` for built-in configs ([#15616](https://togithub.com/eslint/eslint/issues/15616)) (DoZerg)
- [`ee7c5d1`](https://togithub.com/eslint/eslint/commit/ee7c5d14a2cb5ce352d1851cec858b942572d2cc) fix: false positive in `camelcase` with combined properties ([#15581](https://togithub.com/eslint/eslint/issues/15581)) (Nitin Kumar)
#### Documentation
- [`1005bd5`](https://togithub.com/eslint/eslint/commit/1005bd525a08208fee124149a6ad4cf9da20d7d5) docs: update CLA information ([#15630](https://togithub.com/eslint/eslint/issues/15630)) (Nitin Kumar)
- [`5d65c3b`](https://togithub.com/eslint/eslint/commit/5d65c3bc1e514ed07406c502437a1642913b27ed) docs: Fix typo in `no-irregular-whitespace` ([#15634](https://togithub.com/eslint/eslint/issues/15634)) (Ryota Sekiya)
- [`b93af98`](https://togithub.com/eslint/eslint/commit/b93af98b3c417225a027cabc964c38e779adb945) docs: add links between rules about whitespace around block curly braces ([#15625](https://togithub.com/eslint/eslint/issues/15625)) (Milos Djermanovic)
- [`ebc0460`](https://togithub.com/eslint/eslint/commit/ebc0460c411ea608ba5bab05829a1fd122fe21e8) docs: update babel links ([#15624](https://togithub.com/eslint/eslint/issues/15624)) (Milos Djermanovic)
#### Chores
- [`7cec74e`](https://togithub.com/eslint/eslint/commit/7cec74e842b6e51da1b00a9e9b2c9da97dd17362) chore: upgrade [@eslint/eslintrc](https://togithub.com/eslint/eslintrc)[@1](https://togithub.com/1).2.0 ([#15648](https://togithub.com/eslint/eslint/issues/15648)) (Milos Djermanovic)
- [`11c8580`](https://togithub.com/eslint/eslint/commit/11c8580de0dcedd5577cffe2b23d23a322cc97df) chore: read `ESLINT_MOCHA_TIMEOUT` env var in Makefile.js ([#15626](https://togithub.com/eslint/eslint/issues/15626)) (Piggy)
- [`bfaa548`](https://togithub.com/eslint/eslint/commit/bfaa5488bbc794c0d160fb55bd277a2c618953b2) test: add integration tests with built-in configs ([#15612](https://togithub.com/eslint/eslint/issues/15612)) (Milos Djermanovic)
- [`39a2fb3`](https://togithub.com/eslint/eslint/commit/39a2fb3f448a7096bfb2fc172fef6cc3f6a7ed3b) perf: fix lazy loading of core rules ([#15606](https://togithub.com/eslint/eslint/issues/15606)) (Milos Djermanovic)
- [`3fc9196`](https://togithub.com/eslint/eslint/commit/3fc919626ef6a00e35bb6b559b60a1e89cf6ca1a) chore: include `tests/conf` in test runs ([#15610](https://togithub.com/eslint/eslint/issues/15610)) (Milos Djermanovic)
prettier/eslint-config-prettier
### [`v8.5.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-850-2022-03-02)
[Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v8.4.0...v8.5.0)
- Added: \[[@typescript-eslint/space-before-blocks](https://togithub.com/typescript-eslint/space-before-blocks)]. Thanks to Masafumi Koba ([@ybiquitous](https://togithub.com/ybiquitous))!
### [`v8.4.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-840-2022-02-19)
[Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v8.3.0...v8.4.0)
- Added: \[vue/quote-props]. Thanks to [@xcatliu](https://togithub.com/xcatliu)!
wix/eslint-plugin-lodash
### [`v7.4.0`](https://togithub.com/wix/eslint-plugin-lodash/blob/HEAD/CHANGELOG.md#v740-httpsgithubcomwixeslint-plugin-lodashcomparev740v740)
[Compare Source](https://togithub.com/wix/eslint-plugin-lodash/compare/v7.3.0...v7.4.0)
jprichardson/node-fs-extra
### [`v10.0.1`](https://togithub.com/jprichardson/node-fs-extra/blob/HEAD/CHANGELOG.md#1001--2022-02-22)
[Compare Source](https://togithub.com/jprichardson/node-fs-extra/compare/10.0.0...10.0.1)
- Add `sideEffects: false` to `package.json` ([#941](https://togithub.com/jprichardson/node-fs-extra/pull/941))
okonet/lint-staged
### [`v12.3.5`](https://togithub.com/okonet/lint-staged/releases/v12.3.5)
[Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.3.4...v12.3.5)
##### Bug Fixes
- search all configs regardless of staged files ([4b605cd](https://togithub.com/okonet/lint-staged/commit/4b605cd3694cc5bfcf6c5a1a2e75c80ef234ab1a))
mochajs/mocha
### [`v9.2.1`](https://togithub.com/mochajs/mocha/blob/HEAD/CHANGELOG.md#921--2022-02-19)
[Compare Source](https://togithub.com/mochajs/mocha/compare/v9.2.0...v9.2.1)
#### :bug: Fixes
- [#4832](https://togithub.com/mochajs/mocha/issues/4832): Loading of config files throws wrong error ([**@juergba**](https://togithub.com/juergba))
- [#4799](https://togithub.com/mochajs/mocha/issues/4799): Reporter: configurable `maxDiffSize` reporter-option ([**@norla**](https://togithub.com/norla))
Microsoft/TypeScript
### [`v4.6.2`](https://togithub.com/Microsoft/TypeScript/releases/v4.6.2)
[Compare Source](https://togithub.com/Microsoft/TypeScript/compare/v4.5.5...v4.6.2)
For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-4-6/).
For the complete list of fixed issues, check out the
- [fixed issues query for Typescript 4.6.0 (Beta)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.0%22+).
- [fixed issues query for Typescript 4.6.1 (RC)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.1%22+).
- [fixed issues query for Typescript 4.6.2 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.2%22+).
Downloads are available on:
- [npm](https://www.npmjs.com/package/typescript)
- [Visual Studio 2022/2019](https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-46) ([Select new version in project options](https://togithub.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017))
- [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild)
webpack/webpack
### [`v5.70.0`](https://togithub.com/webpack/webpack/releases/v5.70.0)
[Compare Source](https://togithub.com/webpack/webpack/compare/v5.69.1...v5.70.0)
### Features
- update node.js version constraints for ESM support
- add `baseUri` to `entry` options to configure a static base uri (the base of `new URL()`)
- alphabetically sort exports in namespace objects when possible
- add `__webpack_exports_info__.name.canMangle`
- add proxy support to `experiments.buildHttp`
- `import.meta.webpackContext` as ESM alternative to `require.context`
- handle multiple alternative directories (e. g. due to resolve.alias or resolve.modules) when creating an context module
### Bugfixes
- fix problem when assigning `global` to a variable
- fix crash when using `experiments.outputModule` and `loaderContext.importModule` with multiple chunks
- avoid generating progress output before the compilation has started (ProgressPlugin)
- fix handling of non-static-ESM dependencies with using TLA and HMR in the same module
- include the asset module filename in hashing
- `output.clean` will keep HMR assets for at least 10s to allow HMR to access them even when compilation is faster then the browser
### Performance
- fix asset caching when using the BannerPlugin
### Developer Experience
- improve typings
### Contributing
- capture caching errors when running the test suite
### [`v5.69.1`](https://togithub.com/webpack/webpack/releases/v5.69.1)
[Compare Source](https://togithub.com/webpack/webpack/compare/v5.69.0...v5.69.1)
### Revert
- revert "handle multiple alternative directories (e. g. due to resolve.alias or resolve.modules) when creating an context module"
### [`v5.69.0`](https://togithub.com/webpack/webpack/releases/v5.69.0)
[Compare Source](https://togithub.com/webpack/webpack/compare/v5.68.0...v5.69.0)
##### Features
- automatically switch to an ESM compatible environment when enabling ESM output mode
- handle multiple alternative directories (e. g. due to `resolve.alias` or `resolve.modules`) when creating an context module
- add `util/types` to node.js built-in modules
- add `__webpack_exports_info__..canMangle` api
##### Bugfixes
- fix bug in chunk graph generation which leads to modules being included in chunk desprite them being already included in parent chunks
- avoid writing more than 2GB at once during cache serialization (as workaround for node.js/libuv bug on MacOS)
- fix handling of whitespaces in semver ranges when using Module Federation
- avoid generating hashes which contain only numbers as they likely conflict with module ids
- fix resource name based placeholders for data uris
- fix cache serialization for context elements
- fix passing of `stage` option when instrumenting plugins for the ProfilingPlugin
- fix tracking of declarations in concatenated modules to avoid conflicts
- fix unstable mangling of exports
- fix handling of `#` in paths of loaders
- avoid unnecessary cache update when using `experiments.buildHttp`
##### Contributing
- update typescript and jest
##### Developer Experience
- expose some additional typings for usage in webpack-cli
Configuration
📅 Schedule: 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 contains the following updates:
4.14.178->4.14.1795.12.0->5.13.05.12.0->5.13.00.14.21->0.14.258.9.0->8.10.08.3.0->8.5.07.3.0->7.4.010.0.0->10.0.112.3.4->12.3.59.2.0->9.2.14.5.5->4.6.25.68.0->5.70.0Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v5.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5130-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5121v5130-2022-02-28) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.1...v5.13.0) ##### Bug Fixes - **eslint-plugin:** \[sort-type-union-intersection-members] Wrap the constructorType in parentheses ([#4590](https://togithub.com/typescript-eslint/typescript-eslint/issues/4590)) ([851bb90](https://togithub.com/typescript-eslint/typescript-eslint/commit/851bb90216e20b7679efc891dc445e6152d4837f)) ##### Features - **eslint-plugin:** \[no-misused-promises] check more places for checksVoidReturn ([#4541](https://togithub.com/typescript-eslint/typescript-eslint/issues/4541)) ([052cf51](https://togithub.com/typescript-eslint/typescript-eslint/commit/052cf51fe663283afe89dc7bf97c947e750df095)) - **eslint-plugin:** add `no-redundant-type-constituents` rule ([#4378](https://togithub.com/typescript-eslint/typescript-eslint/issues/4378)) ([63d051e](https://togithub.com/typescript-eslint/typescript-eslint/commit/63d051eed29dcf71015a23992feac0a8f92717a0)) - **eslint-plugin:** add `no-useless-empty-export` rule ([#4380](https://togithub.com/typescript-eslint/typescript-eslint/issues/4380)) ([823b945](https://togithub.com/typescript-eslint/typescript-eslint/commit/823b945c8f9e83d0246a2a5d07519f01e1a64518)) - **eslint-plugin:** add extension rule `space-before-blocks` ([#1606](https://togithub.com/typescript-eslint/typescript-eslint/issues/1606)) ([#4184](https://togithub.com/typescript-eslint/typescript-eslint/issues/4184)) ([208b6d0](https://togithub.com/typescript-eslint/typescript-eslint/commit/208b6d02252dff2bf272329d3e4a4a82e56c52c0)) - **eslint-plugin:** added member group support to member-ordering rule ([#4538](https://togithub.com/typescript-eslint/typescript-eslint/issues/4538)) ([6afcaea](https://togithub.com/typescript-eslint/typescript-eslint/commit/6afcaea0160a1ccd1c6483ca677c544ca1b8cb4f)) #### [5.12.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) (2022-02-21) ##### Bug Fixes - **eslint-plugin:** \[no-unnecessary-type-arguments] fix comparison of types ([#4555](https://togithub.com/typescript-eslint/typescript-eslint/issues/4555)) ([fc3936e](https://togithub.com/typescript-eslint/typescript-eslint/commit/fc3936e99712374a707ce9e0101bc641807b9ea6)) ### [`v5.12.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#5121-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5120v5121-2022-02-21) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) ##### Bug Fixes - **eslint-plugin:** \[no-unnecessary-type-arguments] fix comparison of types ([#4555](https://togithub.com/typescript-eslint/typescript-eslint/issues/4555)) ([fc3936e](https://togithub.com/typescript-eslint/typescript-eslint/commit/fc3936e99712374a707ce9e0101bc641807b9ea6))typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.13.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5130-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5121v5130-2022-02-28) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.1...v5.13.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) #### [5.12.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) (2022-02-21) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.12.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5121-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5120v5121-2022-02-21) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.12.0...v5.12.1) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)evanw/esbuild
### [`v0.14.25`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01425) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.24...v0.14.25) - Reduce minification of CSS transforms to avoid Safari bugs ([#2057](https://togithub.com/evanw/esbuild/issues/2057)) In Safari, applying a 3D CSS transform to an element can cause it to render in a different order than applying a 2D CSS transform even if the transformation matrix is identical. I believe this is a bug in Safari because the [CSS `transform` specification](https://drafts.csswg.org/css-transforms-1/#transform-rendering) doesn't seem to distinguish between 2D and 3D transforms as far as rendering order: > For elements whose layout is governed by the CSS box model, any value other than `none` for the `transform` property results in the creation of a stacking context. This bug means that minifying a 3D transform into a 2D transform must be avoided even though it's a valid transformation because it can cause rendering differences in Safari. Previously esbuild sometimes minified 3D CSS transforms into 2D CSS transforms but with this release, esbuild will no longer do that: ```css /* Original code */ div { transform: matrix3d(2, 0, 0, 0, 0, 2, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1) } /* Old output (with --minify) */ div{transform:scale(2)} /* New output (with --minify) */ div{transform:scale3d(2,2,1)} ``` - Minification now takes advantage of the `?.` operator This adds new code minification rules that shorten code with the `?.` optional chaining operator when the result is equivalent: ```ts // Original code let foo = (x) => { if (x !== null && x !== undefined) x.y() return x === null || x === undefined ? undefined : x.z } // Old output (with --minify) let foo=n=>(n!=null&&n.y(),n==null?void 0:n.z); // New output (with --minify) let foo=n=>(n?.y(),n?.z); ``` This only takes effect when minification is enabled and when the configured target environment is known to support the optional chaining operator. As always, make sure to set `--target=` to the appropriate language target if you are running the minified code in an environment that doesn't support the latest JavaScript features. - Add source mapping information for some non-executable tokens ([#1448](https://togithub.com/evanw/esbuild/issues/1448)) Code coverage tools can generate reports that tell you if any code exists that has not been run (or "covered") during your tests. You can use this information to add additional tests for code that isn't currently covered. Some popular JavaScript code coverage tools have bugs where they incorrectly consider lines without any executable code as uncovered, even though there's no test you could possibly write that would cause those lines to be executed. For example, they apparently complain about the lines that only contain the trailing `}` token of an object literal. With this release, esbuild now generates source mappings for some of these trailing non-executable tokens. This may not successfully work around bugs in code coverage tools because there are many non-executable tokens in JavaScript and esbuild doesn't map them all (the drawback of mapping these extra tokens is that esbuild will use more memory, build more slowly, and output a bigger source map). The true solution is to fix the bugs in the code coverage tools in the first place. - Fall back to WebAssembly on Android x64 ([#2068](https://togithub.com/evanw/esbuild/issues/2068)) Go's compiler supports trivial cross-compiling to almost all platforms without installing any additional software other than the Go compiler itself. This has made it very easy for esbuild to publish native binary executables for many platforms. However, it strangely doesn't support cross-compiling to Android x64 without installing the Android build tools. So instead of publishing a native esbuild binary executable to npm, this release publishes a WebAssembly fallback build. This is essentially the same as the `esbuild-wasm` package but it's installed automatically when you install the `esbuild` package on Android x64. So packages that depend on the `esbuild` package should now work on Android x64. If you want to use a native binary executable of esbuild on Android x64, you may be able to build it yourself from source after installing the Android build tools. - Update to Go 1.17.8 The version of the Go compiler used to compile esbuild has been upgraded from Go 1.17.7 to Go 1.17.8, which fixes the RISC-V 64-bit build. Compiler optimizations for the RISC-V 64-bit build have now been re-enabled. ### [`v0.14.24`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01424) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.23...v0.14.24) - Allow `es2022` as a target environment ([#2012](https://togithub.com/evanw/esbuild/issues/2012)) TypeScript recently [added support for `es2022`](https://devblogs.microsoft.com/typescript/announcing-typescript-4-6/#target-es2022) as a compilation target so esbuild now supports this too. Support for this is preliminary as there is no published ES2022 specification yet (i.e. https://tc39.es/ecma262/2021/ exists but https://tc39.es/ecma262/2022/ is a 404 error). The meaning of esbuild's `es2022` target may change in the future when the specification is finalized. Right now I have made the `es2022` target enable support for the syntax-related [finished proposals](https://togithub.com/tc39/proposals/blob/main/finished-proposals.md) that are marked as `2022`: - Class fields - Class private members - Class static blocks - Ergonomic class private member checks - Top-level await I have also included the "arbitrary module namespace names" feature since I'm guessing it will end up in the ES2022 specification (this syntax feature was added to the specification without a proposal). TypeScript has [not added support for this yet](https://togithub.com/microsoft/TypeScript/issues/40594). - Match `define` to strings in index expressions ([#2050](https://togithub.com/evanw/esbuild/issues/2050)) With this release, configuring `--define:foo.bar=baz` now matches and replaces both `foo.bar` and `foo['bar']` expressions in the original source code. This is necessary for people who have enabled TypeScript's [`noPropertyAccessFromIndexSignature` feature](https://www.typescriptlang.org/tsconfig#noPropertyAccessFromIndexSignature), which prevents you from using normal property access syntax on a type with an index signature such as in the following code: ```ts declare let foo: { [key: string]: any } foo.bar // This is a type error if noPropertyAccessFromIndexSignature is enabled foo['bar'] ``` Previously esbuild would generate the following output with `--define:foo.bar=baz`: ```js baz; foo["bar"]; ``` Now esbuild will generate the following output instead: ```js baz; baz; ``` - Add `--mangle-quoted` to mangle quoted properties ([#218](https://togithub.com/evanw/esbuild/issues/218)) The `--mangle-props=` flag tells esbuild to automatically rename all properties matching the provided regular expression to shorter names to save space. Previously esbuild never modified the contents of string literals. In particular, `--mangle-props=_` would mangle `foo._bar` but not `foo['_bar']`. There are some coding patterns where renaming quoted property names is desirable, such as when using TypeScript's [`noPropertyAccessFromIndexSignature` feature](https://www.typescriptlang.org/tsconfig#noPropertyAccessFromIndexSignature) or when using TypeScript's [discriminated union narrowing behavior](https://www.typescriptlang.org/docs/handbook/2/narrowing.html#discriminated-unions): ```ts interface Foo { _foo: string } interface Bar { _bar: number } declare const value: Foo | Bar console.log('_foo' in value ? value._foo : value._bar) ``` The `'_foo' in value` check tells TypeScript to narrow the type of `value` to `Foo` in the true branch and to `Bar` in the false branch. Previously esbuild didn't mangle the property name `'_foo'` because it was inside a string literal. With this release, you can now use `--mangle-quoted` to also rename property names inside string literals: ```js // Old output (with --mangle-props=_) console.log("_foo" in value ? value.a : value.b); // New output (with --mangle-props=_ --mangle-quoted) console.log("a" in value ? value.a : value.b); ``` - Parse and discard TypeScript `export as namespace` statements ([#2070](https://togithub.com/evanw/esbuild/issues/2070)) TypeScript `.d.ts` type declaration files can sometimes contain statements of the form `export as namespace foo;`. I believe these serve to declare that the module adds a property of that name to the global object. You aren't supposed to feed `.d.ts` files to esbuild so this normally doesn't matter, but sometimes esbuild can end up having to parse them. One such case is if you import a type-only package who's `main` field in `package.json` is a `.d.ts` file. Previously esbuild only allowed `export as namespace` statements inside a `declare` context: ```ts declare module Foo { export as namespace foo; } ``` Now esbuild will also allow these statements outside of a `declare` context: ```ts export as namespace foo; ``` These statements are still just ignored and discarded. - Strip import assertions from unrecognized `import()` expressions ([#2036](https://togithub.com/evanw/esbuild/issues/2036)) The new "import assertions" JavaScript language feature adds an optional second argument to dynamic `import()` expressions, which esbuild does support. However, this optional argument must be stripped when targeting older JavaScript environments for which this second argument would be a syntax error. Previously esbuild failed to strip this second argument in cases when the first argument to `import()` wasn't a string literal. This problem is now fixed: ```js // Original code console.log(import(foo, { assert: { type: 'json' } })) // Old output (with --target=es6) console.log(import(foo, { assert: { type: "json" } })); // New output (with --target=es6) console.log(import(foo)); ``` - Remove simplified statement-level literal expressions ([#2063](https://togithub.com/evanw/esbuild/issues/2063)) With this release, esbuild now removes simplified statement-level expressions if the simplified result is a literal expression even when minification is disabled. Previously this was only done when minification is enabled. This change was only made because some people are bothered by seeing top-level literal expressions. This change has no effect on code behavior. - Ignore `.d.ts` rules in `paths` in `tsconfig.json` files ([#2074](https://togithub.com/evanw/esbuild/issues/2074), [#2075](https://togithub.com/evanw/esbuild/pull/2075)) TypeScript's `tsconfig.json` configuration file has a `paths` field that lets you remap import paths to alternative files on the file system. This field is interpreted by esbuild during bundling so that esbuild's behavior matches that of the TypeScript type checker. However, people sometimes override import paths to JavaScript files to instead point to a `.d.ts` TypeScript type declaration file for that JavaScript file. The intent of this is to just use the remapping for type information and not to actually import the `.d.ts` file during the build. With this release, esbuild will now ignore rules in `paths` that result in a `.d.ts` file during path resolution. This means code that does this should now be able to be bundled without modifying its `tsconfig.json` file to remove the `.d.ts` rule. This change was contributed by [@magic-akari](https://togithub.com/magic-akari). - Disable Go compiler optimizations for the Linux RISC-V 64bit build ([#2035](https://togithub.com/evanw/esbuild/pull/2035)) Go's RISC-V 64bit compiler target has a fatal compiler optimization bug that causes esbuild to crash when it's run: [https://github.com/golang/go/issues/51101](https://togithub.com/golang/go/issues/51101). As a temporary workaround until a version of the Go compiler with the fix is published, Go compiler optimizations have been disabled for RISC-V. The 7.7mb esbuild binary executable for RISC-V is now 8.7mb instead. This workaround was contributed by [@piggynl](https://togithub.com/piggynl). ### [`v0.14.23`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01423) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.22...v0.14.23) - Update feature database to indicate that node 16.14+ supports import assertions ([#2030](https://togithub.com/evanw/esbuild/issues/2030)) Node versions 16.14 and above now support import assertions according to [these release notes](https://togithub.com/nodejs/node/blob/6db686710ee1579452b2908a7a41b91cb729b944/doc/changelogs/CHANGELOG_V16.md#16.14.0). This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with `--target=node16.14`: ```js // Original code import data from './package.json' assert { type: 'json' } console.log(data) // Old output (with --target=node16.14) import data from "./package.json"; console.log(data); // New output (with --target=node16.14) import data from "./package.json" assert { type: "json" }; console.log(data); ``` - Basic support for CSS `@layer` rules ([#2027](https://togithub.com/evanw/esbuild/issues/2027)) This adds basic parsing support for a new CSS feature called `@layer` that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of `@layer` rules: ```css /* Original code */ @layer a { @layer b { div { color: yellow; margin: 0.0px; } } } /* Old output (with --minify) */ @layer a{@layer b {div {color: yellow; margin: 0px;}}} /* New output (with --minify) */ @layer a.b{div{color:#ff0;margin:0}} ``` You can read more about `@layer` here: - Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/[@layer](https://togithub.com/layer) - Motivation: https://developer.chrome.com/blog/cascade-layers/ Note that the support added in this release is only for parsing and printing `@layer` rules. The bundler does not yet know about these rules and bundling with `@layer` may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the *first* instance while with every other CSS rule, the order is derived from the *last* instance. ### [`v0.14.22`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01422) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.21...v0.14.22) - Preserve whitespace for token lists that look like CSS variable declarations ([#2020](https://togithub.com/evanw/esbuild/issues/2020)) Previously esbuild removed the whitespace after the CSS variable declaration in the following CSS: ```css /* Original input */ @supports (--foo: ){html{background:green}} /* Previous output */ @supports (--foo:){html{background:green}} ``` However, that broke rendering in Chrome as it caused Chrome to ignore the entire rule. This did not break rendering in Firefox and Safari, so there's a browser bug either with Chrome or with both Firefox and Safari. In any case, esbuild now preserves whitespace after the CSS variable declaration in this case. - Ignore legal comments when merging adjacent duplicate CSS rules ([#2016](https://togithub.com/evanw/esbuild/issues/2016)) This release now generates more compact minified CSS when there are legal comments in between two adjacent rules with identical content: ```css /* Original code */ a { color: red } /* @preserve */ b { color: red } /* Old output (with --minify) */ a{color:red}/* @preserve */b{color:red} /* New output (with --minify) */ a,b{color:red}/* @preserve */ ``` - Block `onResolve` and `onLoad` until `onStart` ends ([#1967](https://togithub.com/evanw/esbuild/issues/1967)) This release changes the semantics of the `onStart` callback. All `onStart` callbacks from all plugins are run concurrently so that a slow plugin doesn't hold up the entire build. That's still the case. However, previously the only thing waiting for the `onStart` callbacks to finish was the end of the build. This meant that `onResolve` and/or `onLoad` callbacks could sometimes run before `onStart` had finished. This was by design but violated user expectations. With this release, all `onStart` callbacks must finish before any `onResolve` and/or `onLoad` callbacks are run. - Add a self-referential `default` export to the JS API ([#1897](https://togithub.com/evanw/esbuild/issues/1897)) Some people try to use esbuild's API using `import esbuild from 'esbuild'` instead of `import * as esbuild from 'esbuild'` (i.e. using a default import instead of a namespace import). There is no `default` export so that wasn't ever intended to work. But it would work sometimes depending on which tools you used and how they were configured so some people still wrote code this way. This release tries to make that work by adding a self-referential `default` export that is equal to esbuild's module namespace object. More detail: The published package for esbuild's JS API is in CommonJS format, although the source code for esbuild's JS API is in ESM format. The original ESM code for esbuild's JS API has no export named `default` so using a default import like this doesn't work with Babel-compatible toolchains (since they respect the semantics of the original ESM code). However, it happens to work with node-compatible toolchains because node's implementation of importing CommonJS from ESM broke compatibility with existing conventions and automatically creates a `default` export which is set to `module.exports`. This is an unfortunate compatibility headache because it means the `default` import only works sometimes. This release tries to fix this by explicitly creating a self-referential `default` export. It now doesn't matter if you do `esbuild.build()`, `esbuild.default.build()`, or `esbuild.default.default.build()` because they should all do the same thing. Hopefully this means people don't have to deal with this problem anymore. - Handle `write` errors when esbuild's child process is killed ([#2007](https://togithub.com/evanw/esbuild/issues/2007)) If you type Ctrl+C in a terminal when a script that uses esbuild's JS library is running, esbuild's child process may be killed before the parent process. In that case calls to the `write()` syscall may fail with an `EPIPE` error. Previously this resulted in an uncaught exception because esbuild didn't handle this case. Starting with this release, esbuild should now catch these errors and redirect them into a general `The service was stopped` error which should be returned from whatever top-level API calls were in progress. - Better error message when browser WASM bugs are present ([#1863](https://togithub.com/evanw/esbuild/issues/1863)) Safari's WebAssembly implementation appears to be broken somehow, at least when running esbuild. Sometimes this manifests as a stack overflow and sometimes as a Go panic. Previously a Go panic resulted in the error message `Can't find variable: fs` but this should now result in the Go panic being printed to the console. Using esbuild's WebAssembly library in Safari is still broken but now there's a more helpful error message. More detail: When Go panics, it prints a stack trace to stderr (i.e. file descriptor 2). Go's WebAssembly shim calls out to node's `fs.writeSync()` function to do this, and it converts calls to `fs.writeSync()` into calls to `console.log()` in the browser by providing a shim for `fs`. However, Go's shim code stores the shim on `window.fs` in the browser. This is undesirable because it pollutes the global scope and leads to brittle code that can break if other code also uses `window.fs`. To avoid this, esbuild shadows the global object by wrapping Go's shim. But that broke bare references to `fs` since the shim is no longer stored on `window.fs`. This release now stores the shim in a local variable named `fs` so that bare references to `fs` work correctly. - Undo incorrect dead-code elimination with destructuring ([#1183](https://togithub.com/evanw/esbuild/issues/1183)) Previously esbuild eliminated these statements as dead code if tree-shaking was enabled: ```js let [a] = {} let { b } = null ``` This is incorrect because both of these lines will throw an error when evaluated. With this release, esbuild now preserves these statements even when tree shaking is enabled. - Update to Go 1.17.7 The version of the Go compiler used to compile esbuild has been upgraded from Go 1.17.6 to Go 1.17.7, which contains a few [compiler and security bug fixes](https://togithub.com/golang/go/issues?q=milestone%3AGo1.17.7+label%3ACherryPickApproved).eslint/eslint
### [`v8.10.0`](https://togithub.com/eslint/eslint/releases/v8.10.0) [Compare Source](https://togithub.com/eslint/eslint/compare/v8.9.0...v8.10.0) #### Features - [`6e2c325`](https://togithub.com/eslint/eslint/commit/6e2c325324479df1b3f868cf00a529b67d2c3d82) feat: Add `ignoreOnInitialization` option to no-shadow rule ([#14963](https://togithub.com/eslint/eslint/issues/14963)) (Soufiane Boutahlil) - [`115cae5`](https://togithub.com/eslint/eslint/commit/115cae54125b9ef509af90620f51d4a692b51ab7) feat: `--debug` prints time it takes to parse a file ([#15609](https://togithub.com/eslint/eslint/issues/15609)) (Bartek Iwańczuk) - [`345e70d`](https://togithub.com/eslint/eslint/commit/345e70d9d6490fb12b18953f56f3cea28fd61d83) feat: Add `onlyOneSimpleParam` option to no-confusing-arrow rule ([#15566](https://togithub.com/eslint/eslint/issues/15566)) (Gautam Arora) #### Bug Fixes - [`cdc5802`](https://togithub.com/eslint/eslint/commit/cdc58025d9a8b522f516c3665d225b69a76c4ee1) fix: Avoid `__dirname` for built-in configs ([#15616](https://togithub.com/eslint/eslint/issues/15616)) (DoZerg) - [`ee7c5d1`](https://togithub.com/eslint/eslint/commit/ee7c5d14a2cb5ce352d1851cec858b942572d2cc) fix: false positive in `camelcase` with combined properties ([#15581](https://togithub.com/eslint/eslint/issues/15581)) (Nitin Kumar) #### Documentation - [`1005bd5`](https://togithub.com/eslint/eslint/commit/1005bd525a08208fee124149a6ad4cf9da20d7d5) docs: update CLA information ([#15630](https://togithub.com/eslint/eslint/issues/15630)) (Nitin Kumar) - [`5d65c3b`](https://togithub.com/eslint/eslint/commit/5d65c3bc1e514ed07406c502437a1642913b27ed) docs: Fix typo in `no-irregular-whitespace` ([#15634](https://togithub.com/eslint/eslint/issues/15634)) (Ryota Sekiya) - [`b93af98`](https://togithub.com/eslint/eslint/commit/b93af98b3c417225a027cabc964c38e779adb945) docs: add links between rules about whitespace around block curly braces ([#15625](https://togithub.com/eslint/eslint/issues/15625)) (Milos Djermanovic) - [`ebc0460`](https://togithub.com/eslint/eslint/commit/ebc0460c411ea608ba5bab05829a1fd122fe21e8) docs: update babel links ([#15624](https://togithub.com/eslint/eslint/issues/15624)) (Milos Djermanovic) #### Chores - [`7cec74e`](https://togithub.com/eslint/eslint/commit/7cec74e842b6e51da1b00a9e9b2c9da97dd17362) chore: upgrade [@eslint/eslintrc](https://togithub.com/eslint/eslintrc)[@1](https://togithub.com/1).2.0 ([#15648](https://togithub.com/eslint/eslint/issues/15648)) (Milos Djermanovic) - [`11c8580`](https://togithub.com/eslint/eslint/commit/11c8580de0dcedd5577cffe2b23d23a322cc97df) chore: read `ESLINT_MOCHA_TIMEOUT` env var in Makefile.js ([#15626](https://togithub.com/eslint/eslint/issues/15626)) (Piggy) - [`bfaa548`](https://togithub.com/eslint/eslint/commit/bfaa5488bbc794c0d160fb55bd277a2c618953b2) test: add integration tests with built-in configs ([#15612](https://togithub.com/eslint/eslint/issues/15612)) (Milos Djermanovic) - [`39a2fb3`](https://togithub.com/eslint/eslint/commit/39a2fb3f448a7096bfb2fc172fef6cc3f6a7ed3b) perf: fix lazy loading of core rules ([#15606](https://togithub.com/eslint/eslint/issues/15606)) (Milos Djermanovic) - [`3fc9196`](https://togithub.com/eslint/eslint/commit/3fc919626ef6a00e35bb6b559b60a1e89cf6ca1a) chore: include `tests/conf` in test runs ([#15610](https://togithub.com/eslint/eslint/issues/15610)) (Milos Djermanovic)prettier/eslint-config-prettier
### [`v8.5.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-850-2022-03-02) [Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v8.4.0...v8.5.0) - Added: \[[@typescript-eslint/space-before-blocks](https://togithub.com/typescript-eslint/space-before-blocks)]. Thanks to Masafumi Koba ([@ybiquitous](https://togithub.com/ybiquitous))! ### [`v8.4.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-840-2022-02-19) [Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v8.3.0...v8.4.0) - Added: \[vue/quote-props]. Thanks to [@xcatliu](https://togithub.com/xcatliu)!wix/eslint-plugin-lodash
### [`v7.4.0`](https://togithub.com/wix/eslint-plugin-lodash/blob/HEAD/CHANGELOG.md#v740-httpsgithubcomwixeslint-plugin-lodashcomparev740v740) [Compare Source](https://togithub.com/wix/eslint-plugin-lodash/compare/v7.3.0...v7.4.0)jprichardson/node-fs-extra
### [`v10.0.1`](https://togithub.com/jprichardson/node-fs-extra/blob/HEAD/CHANGELOG.md#1001--2022-02-22) [Compare Source](https://togithub.com/jprichardson/node-fs-extra/compare/10.0.0...10.0.1) - Add `sideEffects: false` to `package.json` ([#941](https://togithub.com/jprichardson/node-fs-extra/pull/941))okonet/lint-staged
### [`v12.3.5`](https://togithub.com/okonet/lint-staged/releases/v12.3.5) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.3.4...v12.3.5) ##### Bug Fixes - search all configs regardless of staged files ([4b605cd](https://togithub.com/okonet/lint-staged/commit/4b605cd3694cc5bfcf6c5a1a2e75c80ef234ab1a))mochajs/mocha
### [`v9.2.1`](https://togithub.com/mochajs/mocha/blob/HEAD/CHANGELOG.md#921--2022-02-19) [Compare Source](https://togithub.com/mochajs/mocha/compare/v9.2.0...v9.2.1) #### :bug: Fixes - [#4832](https://togithub.com/mochajs/mocha/issues/4832): Loading of config files throws wrong error ([**@juergba**](https://togithub.com/juergba)) - [#4799](https://togithub.com/mochajs/mocha/issues/4799): Reporter: configurable `maxDiffSize` reporter-option ([**@norla**](https://togithub.com/norla))Microsoft/TypeScript
### [`v4.6.2`](https://togithub.com/Microsoft/TypeScript/releases/v4.6.2) [Compare Source](https://togithub.com/Microsoft/TypeScript/compare/v4.5.5...v4.6.2) For release notes, check out the [release announcement](https://devblogs.microsoft.com/typescript/announcing-typescript-4-6/). For the complete list of fixed issues, check out the - [fixed issues query for Typescript 4.6.0 (Beta)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.0%22+). - [fixed issues query for Typescript 4.6.1 (RC)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.1%22+). - [fixed issues query for Typescript 4.6.2 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.6.2%22+). Downloads are available on: - [npm](https://www.npmjs.com/package/typescript) - [Visual Studio 2022/2019](https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-46) ([Select new version in project options](https://togithub.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017)) - [NuGet package](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild)webpack/webpack
### [`v5.70.0`](https://togithub.com/webpack/webpack/releases/v5.70.0) [Compare Source](https://togithub.com/webpack/webpack/compare/v5.69.1...v5.70.0) ### Features - update node.js version constraints for ESM support - add `baseUri` to `entry` options to configure a static base uri (the base of `new URL()`) - alphabetically sort exports in namespace objects when possible - add `__webpack_exports_info__.name.canMangle` - add proxy support to `experiments.buildHttp` - `import.meta.webpackContext` as ESM alternative to `require.context` - handle multiple alternative directories (e. g. due to resolve.alias or resolve.modules) when creating an context module ### Bugfixes - fix problem when assigning `global` to a variable - fix crash when using `experiments.outputModule` and `loaderContext.importModule` with multiple chunks - avoid generating progress output before the compilation has started (ProgressPlugin) - fix handling of non-static-ESM dependencies with using TLA and HMR in the same module - include the asset module filename in hashing - `output.clean` will keep HMR assets for at least 10s to allow HMR to access them even when compilation is faster then the browser ### Performance - fix asset caching when using the BannerPlugin ### Developer Experience - improve typings ### Contributing - capture caching errors when running the test suite ### [`v5.69.1`](https://togithub.com/webpack/webpack/releases/v5.69.1) [Compare Source](https://togithub.com/webpack/webpack/compare/v5.69.0...v5.69.1) ### Revert - revert "handle multiple alternative directories (e. g. due to resolve.alias or resolve.modules) when creating an context module" ### [`v5.69.0`](https://togithub.com/webpack/webpack/releases/v5.69.0) [Compare Source](https://togithub.com/webpack/webpack/compare/v5.68.0...v5.69.0) ##### Features - automatically switch to an ESM compatible environment when enabling ESM output mode - handle multiple alternative directories (e. g. due to `resolve.alias` or `resolve.modules`) when creating an context module - add `util/types` to node.js built-in modules - add `__webpack_exports_info__.Configuration
📅 Schedule: 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 WhiteSource Renovate. View repository job log here.