Sourced from esbuild's releases.

v0.16.1

This is a hotfix for the previous release.

• Re-allow importing JSON with the copy loader using an import assertion

  The previous release made it so when assert { type: 'json' } is present on an import statement, esbuild validated that the json loader was used. This is what an import assertion is supposed to do. However, I forgot about the relatively new copy loader, which sort of behaves as if the import path was marked as external (and thus not loaded at all) except that the file is copied to the output directory and the import path is rewritten to point to the copy. In this case whatever JavaScript runtime ends up running the code is the one to evaluate the import assertion. So esbuild should really allow this case as well. With this release, esbuild now allows both the json and copy loaders when an assert { type: 'json' } import assertion is present.

v0.16.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ~0.15.0. See npm's documentation about semver for more information.

• Move all binary executable packages to the @esbuild/ scope

  Binary package executables for esbuild are published as individual packages separate from the main esbuild package so you only have to download the relevant one for the current platform when you install esbuild. This release moves all of these packages under the @esbuild/ scope to avoid collisions with 3rd-party packages. It also changes them to a consistent naming scheme that uses the os and cpu names from node.

  The package name changes are as follows:

  • @esbuild/linux-loong64 => @esbuild/linux-loong64 (no change)
  • esbuild-android-64 => @esbuild/android-x64
  • esbuild-android-arm64 => @esbuild/android-arm64
  • esbuild-darwin-64 => @esbuild/darwin-x64
  • esbuild-darwin-arm64 => @esbuild/darwin-arm64
  • esbuild-freebsd-64 => @esbuild/freebsd-x64
  • esbuild-freebsd-arm64 => @esbuild/freebsd-arm64
  • esbuild-linux-32 => @esbuild/linux-ia32
  • esbuild-linux-64 => @esbuild/linux-x64
  • esbuild-linux-arm => @esbuild/linux-arm
  • esbuild-linux-arm64 => @esbuild/linux-arm64
  • esbuild-linux-mips64le => @esbuild/linux-mips64el
  • esbuild-linux-ppc64le => @esbuild/linux-ppc64
  • esbuild-linux-riscv64 => @esbuild/linux-riscv64
  • esbuild-linux-s390x => @esbuild/linux-s390x
  • esbuild-netbsd-64 => @esbuild/netbsd-x64
  • esbuild-openbsd-64 => @esbuild/openbsd-x64
  • esbuild-sunos-64 => @esbuild/sunos-x64
  • esbuild-wasm => esbuild-wasm (no change)
  • esbuild-windows-32 => @esbuild/win32-ia32
  • esbuild-windows-64 => @esbuild/win32-x64
  • esbuild-windows-arm64 => @esbuild/win32-arm64
  • esbuild => esbuild (no change)

  Normal usage of the esbuild and esbuild-wasm packages should not be affected. These name changes should only affect tools that hard-coded the individual binary executable package names into custom esbuild downloader scripts.

  This change was not made with performance in mind. But as a bonus, installing esbuild with npm may potentially happen faster now. This is because npm's package installation protocol is inefficient: it always downloads metadata for all past versions of each package even when it only needs metadata about a single version. This makes npm package downloads O(n) in the number of published versions, which penalizes packages like esbuild that are updated regularly. Since most of esbuild's package names have now changed, npm will now need to download much less data when installing esbuild (8.72mb of package manifests before this change → 0.06mb of package manifests after this change). However, this is only a temporary improvement. Installing esbuild will gradually get slower again as further versions of esbuild are published.

• Publish a shell script that downloads esbuild directly

  In addition to all of the existing ways to install esbuild, you can now also download esbuild directly like this:

  curl -fsSL https://esbuild.github.io/dl/latest | sh
  

... (truncated)

Sourced from esbuild's changelog.

0.16.1

This is a hotfix for the previous release.

• Re-allow importing JSON with the copy loader using an import assertion

  The previous release made it so when assert { type: 'json' } is present on an import statement, esbuild validated that the json loader was used. This is what an import assertion is supposed to do. However, I forgot about the relatively new copy loader, which sort of behaves as if the import path was marked as external (and thus not loaded at all) except that the file is copied to the output directory and the import path is rewritten to point to the copy. In this case whatever JavaScript runtime ends up running the code is the one to evaluate the import assertion. So esbuild should really allow this case as well. With this release, esbuild now allows both the json and copy loaders when an assert { type: 'json' } import assertion is present.

0.16.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ~0.15.0. See npm's documentation about semver for more information.

• Move all binary executable packages to the @esbuild/ scope

  Binary package executables for esbuild are published as individual packages separate from the main esbuild package so you only have to download the relevant one for the current platform when you install esbuild. This release moves all of these packages under the @esbuild/ scope to avoid collisions with 3rd-party packages. It also changes them to a consistent naming scheme that uses the os and cpu names from node.

  The package name changes are as follows:

  • @esbuild/linux-loong64 => @esbuild/linux-loong64 (no change)
  • esbuild-android-64 => @esbuild/android-x64
  • esbuild-android-arm64 => @esbuild/android-arm64
  • esbuild-darwin-64 => @esbuild/darwin-x64
  • esbuild-darwin-arm64 => @esbuild/darwin-arm64
  • esbuild-freebsd-64 => @esbuild/freebsd-x64
  • esbuild-freebsd-arm64 => @esbuild/freebsd-arm64
  • esbuild-linux-32 => @esbuild/linux-ia32
  • esbuild-linux-64 => @esbuild/linux-x64
  • esbuild-linux-arm => @esbuild/linux-arm
  • esbuild-linux-arm64 => @esbuild/linux-arm64
  • esbuild-linux-mips64le => @esbuild/linux-mips64el
  • esbuild-linux-ppc64le => @esbuild/linux-ppc64
  • esbuild-linux-riscv64 => @esbuild/linux-riscv64
  • esbuild-linux-s390x => @esbuild/linux-s390x
  • esbuild-netbsd-64 => @esbuild/netbsd-x64
  • esbuild-openbsd-64 => @esbuild/openbsd-x64
  • esbuild-sunos-64 => @esbuild/sunos-x64
  • esbuild-wasm => esbuild-wasm (no change)
  • esbuild-windows-32 => @esbuild/win32-ia32
  • esbuild-windows-64 => @esbuild/win32-x64
  • esbuild-windows-arm64 => @esbuild/win32-arm64
  • esbuild => esbuild (no change)

  Normal usage of the esbuild and esbuild-wasm packages should not be affected. These name changes should only affect tools that hard-coded the individual binary executable package names into custom esbuild downloader scripts.

  This change was not made with performance in mind. But as a bonus, installing esbuild with npm may potentially happen faster now. This is because npm's package installation protocol is inefficient: it always downloads metadata for all past versions of each package even when it only needs metadata about a single version. This makes npm package downloads O(n) in the number of published versions, which penalizes packages like esbuild that are updated regularly. Since most of esbuild's package names have now changed, npm will now need to download much less data when installing esbuild (8.72mb of package manifests before this change → 0.06mb of package manifests after this change). However, this is only a temporary improvement. Installing esbuild will gradually get slower again as further versions of esbuild are published.

• Publish a shell script that downloads esbuild directly

  In addition to all of the existing ways to install esbuild, you can now also download esbuild directly like this:

... (truncated)

• 3b62a36 publish 0.16.1 to npm
• 07f8eeb hotfix: re-allow copy with json import assertion
• 219ffc6 fix JSXMode => JSX for the Go transform API
• 6c8d15d publish 0.16.0 to npm
• 895f50c fix #1843: generate shorter data urls if possible
• 5abe071 fix #2417: add the module condition by default
• 328ce12 fix #2649: allow disabling escaping of \</script>
• 0228284 discard legal comments by default
• c3b0890 fix #714: remove the webassembly _exit(0) hack
• 055f9e3 add a shell script that downloads esbuild directly
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.18

• Performance improvements for both JS and CSS

  This release brings noticeable performance improvements for JS parsing and for CSS parsing and printing. Here's an example benchmark for using esbuild to pretty-print a single large minified CSS file and JS file:

  Test case	Previous release	This release
  4.8mb CSS file	19ms	11ms (1.7x faster)
  5.8mb JS file	36ms	32ms (1.1x faster)

  The performance improvements were very straightforward:

  • Identifiers were being scanned using a generic character advancement function instead of using custom inline code. Advancing past each character involved UTF-8 decoding as well as updating multiple member variables. This was sped up using loop that skips UTF-8 decoding entirely and that only updates member variables once at the end. This is faster because identifiers are plain ASCII in the vast majority of cases, so Unicode decoding is almost always unnecessary.

  • CSS identifiers and CSS strings were still being printed one character at a time. Apparently I forgot to move this part of esbuild's CSS infrastructure beyond the proof-of-concept stage. These were both very obvious in the profiler, so I think maybe I have just never profiled esbuild's CSS printing before?

  • There was unnecessary work being done that was related to source maps when source map output was disabled. I likely haven't observed this before because esbuild's benchmarks always have source maps enabled. This work is now disabled when it's not going to be used.

  I definitely should have caught these performance issues earlier. Better late than never I suppose.

v0.15.17

• Search for missing source map code on the file system (#2711)

  Source maps are JSON files that map from compiled code back to the original code. They provide the original source code using two arrays: sources (required) and sourcesContent (optional). When bundling is enabled, esbuild is able to bundle code with source maps that was compiled by other tools (e.g. with Webpack) and emit source maps that map all the way back to the original code (e.g. before Webpack compiled it).

  Previously if the input source maps omitted the optional sourcesContent array, esbuild would use null for the source content in the source map that it generates (since the source content isn't available). However, sometimes the original source code is actually still present on the file system. With this release, esbuild will now try to find the original source code using the path in the sources array and will use that instead of null if it was found.

• Fix parsing bug with TypeScript infer and extends (#2712)

  This release fixes a bug where esbuild incorrectly failed to parse valid TypeScript code that nests extends inside infer inside extends, such as in the example below:

  type A<T> = {};
  type B = {} extends infer T extends {} ? A<T> : never;
  

  TypeScript code that does this should now be parsed correctly.

• Use WebAssembly.instantiateStreaming if available (#1036, #1900)

  Currently the WebAssembly version of esbuild uses fetch to download esbuild.wasm and then WebAssembly.instantiate to compile it. There is a newer API called WebAssembly.instantiateStreaming that both downloads and compiles at the same time, which can be a performance improvement if both downloading and compiling are slow. With this release, esbuild now attempts to use WebAssembly.instantiateStreaming and falls back to the original approach if that fails.

  The implementation for this builds on a PR by @​lbwa.

• Preserve Webpack comments inside constructor calls (#2439)

  This improves the use of esbuild as a faster TypeScript-to-JavaScript frontend for Webpack, which has special magic comments inside new Worker() expressions that affect Webpack's behavior.

v0.15.16

• Add a package alias feature (#2191)

... (truncated)

Sourced from esbuild's changelog.

0.15.18

• Performance improvements for both JS and CSS

  This release brings noticeable performance improvements for JS parsing and for CSS parsing and printing. Here's an example benchmark for using esbuild to pretty-print a single large minified CSS file and JS file:

  Test case	Previous release	This release
  4.8mb CSS file	19ms	11ms (1.7x faster)
  5.8mb JS file	36ms	32ms (1.1x faster)

  The performance improvements were very straightforward:

  • Identifiers were being scanned using a generic character advancement function instead of using custom inline code. Advancing past each character involved UTF-8 decoding as well as updating multiple member variables. This was sped up using loop that skips UTF-8 decoding entirely and that only updates member variables once at the end. This is faster because identifiers are plain ASCII in the vast majority of cases, so Unicode decoding is almost always unnecessary.

  • CSS identifiers and CSS strings were still being printed one character at a time. Apparently I forgot to move this part of esbuild's CSS infrastructure beyond the proof-of-concept stage. These were both very obvious in the profiler, so I think maybe I have just never profiled esbuild's CSS printing before?

  • There was unnecessary work being done that was related to source maps when source map output was disabled. I likely haven't observed this before because esbuild's benchmarks always have source maps enabled. This work is now disabled when it's not going to be used.

  I definitely should have caught these performance issues earlier. Better late than never I suppose.

0.15.17

• Search for missing source map code on the file system (#2711)

  Source maps are JSON files that map from compiled code back to the original code. They provide the original source code using two arrays: sources (required) and sourcesContent (optional). When bundling is enabled, esbuild is able to bundle code with source maps that was compiled by other tools (e.g. with Webpack) and emit source maps that map all the way back to the original code (e.g. before Webpack compiled it).

  Previously if the input source maps omitted the optional sourcesContent array, esbuild would use null for the source content in the source map that it generates (since the source content isn't available). However, sometimes the original source code is actually still present on the file system. With this release, esbuild will now try to find the original source code using the path in the sources array and will use that instead of null if it was found.

• Fix parsing bug with TypeScript infer and extends (#2712)

  This release fixes a bug where esbuild incorrectly failed to parse valid TypeScript code that nests extends inside infer inside extends, such as in the example below:

  type A<T> = {};
  type B = {} extends infer T extends {} ? A<T> : never;
  

  TypeScript code that does this should now be parsed correctly.

• Use WebAssembly.instantiateStreaming if available (#1036, #1900)

  Currently the WebAssembly version of esbuild uses fetch to download esbuild.wasm and then WebAssembly.instantiate to compile it. There is a newer API called WebAssembly.instantiateStreaming that both downloads and compiles at the same time, which can be a performance improvement if both downloading and compiling are slow. With this release, esbuild now attempts to use WebAssembly.instantiateStreaming and falls back to the original approach if that fails.

  The implementation for this builds on a PR by @​lbwa.

• Preserve Webpack comments inside constructor calls (#2439)

  This improves the use of esbuild as a faster TypeScript-to-JavaScript frontend for Webpack, which has special magic comments inside new Worker() expressions that affect Webpack's behavior.

... (truncated)

• 2953831 publish 0.15.18 to npm
• a3ba2b2 perf release notes
• f0d8fdd oops: skip source maps for improved performance
• e49e093 css: optimize printing quoted unescaped strings
• a193324 css: improve identifier printing performance
• 83b5580 css: pretty-print test failures
• 2b8883c css: improve lexer identifier parsing performance
• f6f8b27 js: improve lexer identifier parsing performance
• decf208 restrict gc disable to not serve or watch mode
• 2030df1 don't disable the gc with multiple entry points
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.16

• Add a package alias feature (#2191)

  With this release, you can now easily substitute one package for another at build time with the new alias feature. For example, --alias:oldpkg=newpkg replaces all imports of oldpkg with newpkg. One use case for this is easily replacing a node-only package with a browser-friendly package in 3rd-party code that you don't control. These new substitutions happen first before all of esbuild's existing path resolution logic.

  Note that when an import path is substituted using an alias, the resulting import path is resolved in the working directory instead of in the directory containing the source file with the import path. If needed, the working directory can be set with the cd command when using the CLI or with the absWorkingDir setting when using the JS or Go APIs.

• Fix crash when pretty-printing minified JSX with object spread of object literal with computed property (#2697)

  JSX elements are translated to JavaScript function calls and JSX element attributes are translated to properties on a JavaScript object literal. These properties are always either strings (e.g. in <x y />, y is a string) or an object spread (e.g. in <x {...y} />, y is an object spread) because JSX doesn't provide syntax for directly passing a computed property as a JSX attribute. However, esbuild's minifier has a rule that tries to inline object spread with an inline object literal in JavaScript. For example, x = { ...{ y } } is minified to x={y} when minification is enabled. This means that there is a way to generate a non-string non-spread JSX attribute in esbuild's internal representation. One example is with <x {...{ [y]: z }} />. When minification is enabled, esbuild's internal representation of this is something like <x [y]={z} /> due to object spread inlining, which is not valid JSX syntax. If this internal representation is then pretty-printed as JSX using --minify --jsx=preserve, esbuild previously crashed when trying to print this invalid syntax. With this release, esbuild will now print <x {...{[y]:z}}/> in this scenario instead of crashing.

v0.15.15

• Remove duplicate CSS rules across files (#2688)

  When two or more CSS rules are exactly the same (even if they are not adjacent), all but the last one can safely be removed:

  /* Before */
  a { color: red; }
  span { font-weight: bold; }
  a { color: red; }
  /* After */
  span { font-weight: bold; }
  a { color: red; }
  

  Previously esbuild only did this transformation within a single source file. But with this release, esbuild will now do this transformation across source files, which may lead to smaller CSS output if the same rules are repeated across multiple CSS source files in the same bundle. This transformation is only enabled when minifying (specifically when syntax minification is enabled).

• Add deno as a valid value for target (#2686)

  The target setting in esbuild allows you to enable or disable JavaScript syntax features for a given version of a set of target JavaScript VMs. Previously Deno was not one of the JavaScript VMs that esbuild supported with target, but it will now be supported starting from this release. For example, versions of Deno older than v1.2 don't support the new ||= operator, so adding e.g. --target=deno1.0 to esbuild now lets you tell esbuild to transpile ||= to older JavaScript.

• Fix the esbuild-wasm package in Node v19 (#2683)

  A recent change to Node v19 added a non-writable crypto property to the global object: nodejs/node#44897. This conflicts with Go's WebAssembly shim code, which overwrites the global crypto property. As a result, all Go-based WebAssembly code that uses the built-in shim (including esbuild) is now broken on Node v19. This release of esbuild fixes the issue by reconfiguring the global crypto property to be writable before invoking Go's WebAssembly shim code.

• Fix CSS dimension printing exponent confusion edge case (#2677)

  In CSS, a dimension token has a numeric "value" part and an identifier "unit" part. For example, the dimension token 32px has a value of 32 and a unit of px. The unit can be any valid CSS identifier. The value can be any number in floating-point format including an optional exponent (e.g. -3.14e-0 has an exponent of e-0). The full details of this syntax are here: https://www.w3.org/TR/css-syntax-3/.

  To maintain the integrity of the dimension token through the printing process, esbuild must handle the edge case where the unit looks like an exponent. One such case is the dimension 1e\32 which has the value 1 and the unit e2. It would be bad if this dimension token was printed such that a CSS parser would parse it as a number token with the value 1e2 instead of a dimension token. The way esbuild currently does this is to escape the leading e in the dimension unit, so esbuild would parse 1e\32 but print 1\65 2 (both 1e\32 and 1\65 2 represent a dimension token with a value of 1 and a unit of e2).

  However, there is an even narrower edge case regarding this edge case. If the value part of the dimension token itself has an e, then it's not necessary to escape the e in the dimension unit because a CSS parser won't confuse the unit with the exponent even though it looks like one (since a number can only have at most one exponent). This came up because the grammar for the CSS unicode-range property uses a hack that lets you specify a hexadecimal range without quotes even though CSS has no token for a hexadecimal range. The hack is to allow the hexadecimal range to be parsed as a dimension token and optionally also a number token. Here is the grammar for unicode-range:

  unicode-range =
    <urange>#
  <urange> =
  

... (truncated)

Sourced from esbuild's changelog.

0.15.16

• Add a package alias feature (#2191)

  With this release, you can now easily substitute one package for another at build time with the new alias feature. For example, --alias:oldpkg=newpkg replaces all imports of oldpkg with newpkg. One use case for this is easily replacing a node-only package with a browser-friendly package in 3rd-party code that you don't control. These new substitutions happen first before all of esbuild's existing path resolution logic.

  Note that when an import path is substituted using an alias, the resulting import path is resolved in the working directory instead of in the directory containing the source file with the import path. If needed, the working directory can be set with the cd command when using the CLI or with the absWorkingDir setting when using the JS or Go APIs.

• Fix crash when pretty-printing minified JSX with object spread of object literal with computed property (#2697)

  JSX elements are translated to JavaScript function calls and JSX element attributes are translated to properties on a JavaScript object literal. These properties are always either strings (e.g. in <x y />, y is a string) or an object spread (e.g. in <x {...y} />, y is an object spread) because JSX doesn't provide syntax for directly passing a computed property as a JSX attribute. However, esbuild's minifier has a rule that tries to inline object spread with an inline object literal in JavaScript. For example, x = { ...{ y } } is minified to x={y} when minification is enabled. This means that there is a way to generate a non-string non-spread JSX attribute in esbuild's internal representation. One example is with <x {...{ [y]: z }} />. When minification is enabled, esbuild's internal representation of this is something like <x [y]={z} /> due to object spread inlining, which is not valid JSX syntax. If this internal representation is then pretty-printed as JSX using --minify --jsx=preserve, esbuild previously crashed when trying to print this invalid syntax. With this release, esbuild will now print <x {...{[y]:z}}/> in this scenario instead of crashing.

0.15.15

• Remove duplicate CSS rules across files (#2688)

  When two or more CSS rules are exactly the same (even if they are not adjacent), all but the last one can safely be removed:

  /* Before */
  a { color: red; }
  span { font-weight: bold; }
  a { color: red; }
  /* After */
  span { font-weight: bold; }
  a { color: red; }
  

  Previously esbuild only did this transformation within a single source file. But with this release, esbuild will now do this transformation across source files, which may lead to smaller CSS output if the same rules are repeated across multiple CSS source files in the same bundle. This transformation is only enabled when minifying (specifically when syntax minification is enabled).

• Add deno as a valid value for target (#2686)

  The target setting in esbuild allows you to enable or disable JavaScript syntax features for a given version of a set of target JavaScript VMs. Previously Deno was not one of the JavaScript VMs that esbuild supported with target, but it will now be supported starting from this release. For example, versions of Deno older than v1.2 don't support the new ||= operator, so adding e.g. --target=deno1.0 to esbuild now lets you tell esbuild to transpile ||= to older JavaScript.

• Fix the esbuild-wasm package in Node v19 (#2683)

  A recent change to Node v19 added a non-writable crypto property to the global object: nodejs/node#44897. This conflicts with Go's WebAssembly shim code, which overwrites the global crypto property. As a result, all Go-based WebAssembly code that uses the built-in shim (including esbuild) is now broken on Node v19. This release of esbuild fixes the issue by reconfiguring the global crypto property to be writable before invoking Go's WebAssembly shim code.

• Fix CSS dimension printing exponent confusion edge case (#2677)

  In CSS, a dimension token has a numeric "value" part and an identifier "unit" part. For example, the dimension token 32px has a value of 32 and a unit of px. The unit can be any valid CSS identifier. The value can be any number in floating-point format including an optional exponent (e.g. -3.14e-0 has an exponent of e-0). The full details of this syntax are here: https://www.w3.org/TR/css-syntax-3/.

  To maintain the integrity of the dimension token through the printing process, esbuild must handle the edge case where the unit looks like an exponent. One such case is the dimension 1e\32 which has the value 1 and the unit e2. It would be bad if this dimension token was printed such that a CSS parser would parse it as a number token with the value 1e2 instead of a dimension token. The way esbuild currently does this is to escape the leading e in the dimension unit, so esbuild would parse 1e\32 but print 1\65 2 (both 1e\32 and 1\65 2 represent a dimension token with a value of 1 and a unit of e2).

  However, there is an even narrower edge case regarding this edge case. If the value part of the dimension token itself has an e, then it's not necessary to escape the e in the dimension unit because a CSS parser won't confuse the unit with the exponent even though it looks like one (since a number can only have at most one exponent). This came up because the grammar for the CSS unicode-range property uses a hack that lets you specify a hexadecimal range without quotes even though CSS has no token for a hexadecimal range. The hack is to allow the hexadecimal range to be parsed as a dimension token and optionally also a number token. Here is the grammar for unicode-range:

  unicode-range =
    <urange>#
  

... (truncated)

• 50ae05b publish 0.15.16 to npm
• d8d7362 alias: more tests, allow relative substitutions
• a7eb789 fix #2191: add a path alias feature
• 4e9f9c1 fix indentation for some tests
• 89e4520 fix #2697: jsx + spread + computed property crash
• ef348a3 jsx: pretty-print single-line JSX elements
• 478062d publish 0.15.15 to npm
• e7ad5fb remove duplicate css rules across files (#2688)
• 6664172 test duplicate rule merging after bundling
• a73c4e9 css: merge adjacent selectors forward not backward
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.15

• Remove duplicate CSS rules across files (#2688)

  When two or more CSS rules are exactly the same (even if they are not adjacent), all but the last one can safely be removed:

  /* Before */
  a { color: red; }
  span { font-weight: bold; }
  a { color: red; }
  /* After */
  span { font-weight: bold; }
  a { color: red; }
  

  Previously esbuild only did this transformation within a single source file. But with this release, esbuild will now do this transformation across source files, which may lead to smaller CSS output if the same rules are repeated across multiple CSS source files in the same bundle. This transformation is only enabled when minifying (specifically when syntax minification is enabled).

• Add deno as a valid value for target (#2686)

  The target setting in esbuild allows you to enable or disable JavaScript syntax features for a given version of a set of target JavaScript VMs. Previously Deno was not one of the JavaScript VMs that esbuild supported with target, but it will now be supported starting from this release. For example, versions of Deno older than v1.2 don't support the new ||= operator, so adding e.g. --target=deno1.0 to esbuild now lets you tell esbuild to transpile ||= to older JavaScript.

• Fix the esbuild-wasm package in Node v19 (#2683)

  A recent change to Node v19 added a non-writable crypto property to the global object: nodejs/node#44897. This conflicts with Go's WebAssembly shim code, which overwrites the global crypto property. As a result, all Go-based WebAssembly code that uses the built-in shim (including esbuild) is now broken on Node v19. This release of esbuild fixes the issue by reconfiguring the global crypto property to be writable before invoking Go's WebAssembly shim code.

• Fix CSS dimension printing exponent confusion edge case (#2677)

  In CSS, a dimension token has a numeric "value" part and an identifier "unit" part. For example, the dimension token 32px has a value of 32 and a unit of px. The unit can be any valid CSS identifier. The value can be any number in floating-point format including an optional exponent (e.g. -3.14e-0 has an exponent of e-0). The full details of this syntax are here: https://www.w3.org/TR/css-syntax-3/.

  To maintain the integrity of the dimension token through the printing process, esbuild must handle the edge case where the unit looks like an exponent. One such case is the dimension 1e\32 which has the value 1 and the unit e2. It would be bad if this dimension token was printed such that a CSS parser would parse it as a number token with the value 1e2 instead of a dimension token. The way esbuild currently does this is to escape the leading e in the dimension unit, so esbuild would parse 1e\32 but print 1\65 2 (both 1e\32 and 1\65 2 represent a dimension token with a value of 1 and a unit of e2).

  However, there is an even narrower edge case regarding this edge case. If the value part of the dimension token itself has an e, then it's not necessary to escape the e in the dimension unit because a CSS parser won't confuse the unit with the exponent even though it looks like one (since a number can only have at most one exponent). This came up because the grammar for the CSS unicode-range property uses a hack that lets you specify a hexadecimal range without quotes even though CSS has no token for a hexadecimal range. The hack is to allow the hexadecimal range to be parsed as a dimension token and optionally also a number token. Here is the grammar for unicode-range:

  unicode-range =
    <urange>#
  <urange> =
  u '+' <ident-token> '?'*            |
  u <dimension-token> '?'*            |
  u <number-token> '?'*               |
  u <number-token> <dimension-token>  |
  u <number-token> <number-token>     |
  u '+' '?'+
  

  and here is an example unicode-range declaration that was problematic for esbuild:

... (truncated)

Sourced from esbuild's changelog.

0.15.15

• Remove duplicate CSS rules across files (#2688)

  When two or more CSS rules are exactly the same (even if they are not adjacent), all but the last one can safely be removed:

  /* Before */
  a { color: red; }
  span { font-weight: bold; }
  a { color: red; }
  /* After */
  span { font-weight: bold; }
  a { color: red; }
  

  Previously esbuild only did this transformation within a single source file. But with this release, esbuild will now do this transformation across source files, which may lead to smaller CSS output if the same rules are repeated across multiple CSS source files in the same bundle. This transformation is only enabled when minifying (specifically when syntax minification is enabled).

• Add deno as a valid value for target (#2686)

  The target setting in esbuild allows you to enable or disable JavaScript syntax features for a given version of a set of target JavaScript VMs. Previously Deno was not one of the JavaScript VMs that esbuild supported with target, but it will now be supported starting from this release. For example, versions of Deno older than v1.2 don't support the new ||= operator, so adding e.g. --target=deno1.0 to esbuild now lets you tell esbuild to transpile ||= to older JavaScript.

• Fix the esbuild-wasm package in Node v19 (#2683)

  A recent change to Node v19 added a non-writable crypto property to the global object: nodejs/node#44897. This conflicts with Go's WebAssembly shim code, which overwrites the global crypto property. As a result, all Go-based WebAssembly code that uses the built-in shim (including esbuild) is now broken on Node v19. This release of esbuild fixes the issue by reconfiguring the global crypto property to be writable before invoking Go's WebAssembly shim code.

• Fix CSS dimension printing exponent confusion edge case (#2677)

  In CSS, a dimension token has a numeric "value" part and an identifier "unit" part. For example, the dimension token 32px has a value of 32 and a unit of px. The unit can be any valid CSS identifier. The value can be any number in floating-point format including an optional exponent (e.g. -3.14e-0 has an exponent of e-0). The full details of this syntax are here: https://www.w3.org/TR/css-syntax-3/.

  To maintain the integrity of the dimension token through the printing process, esbuild must handle the edge case where the unit looks like an exponent. One such case is the dimension 1e\32 which has the value 1 and the unit e2. It would be bad if this dimension token was printed such that a CSS parser would parse it as a number token with the value 1e2 instead of a dimension token. The way esbuild currently does this is to escape the leading e in the dimension unit, so esbuild would parse 1e\32 but print 1\65 2 (both 1e\32 and 1\65 2 represent a dimension token with a value of 1 and a unit of e2).

  However, there is an even narrower edge case regarding this edge case. If the value part of the dimension token itself has an e, then it's not necessary to escape the e in the dimension unit because a CSS parser won't confuse the unit with the exponent even though it looks like one (since a number can only have at most one exponent). This came up because the grammar for the CSS unicode-range property uses a hack that lets you specify a hexadecimal range without quotes even though CSS has no token for a hexadecimal range. The hack is to allow the hexadecimal range to be parsed as a dimension token and optionally also a number token. Here is the grammar for unicode-range:

  unicode-range =
    <urange>#
  <urange> =
  u '+' <ident-token> '?'*            |
  u <dimension-token> '?'*            |
  u <number-token> '?'*               |
  u <number-token> <dimension-token>  |
  u <number-token> <number-token>     |
  u '+' '?'+
  

  and here is an example unicode-range declaration that was problematic for esbuild:

... (truncated)

• 478062d publish 0.15.15 to npm
• e7ad5fb remove duplicate css rules across files (#2688)
• 6664172 test duplicate rule merging after bundling
• a73c4e9 css: merge adjacent selectors forward not backward
• 4b1200f fix #2685: preferUnplugged: true in all packages
• ec9c3cf fix #2686: make deno a valid value for target
• 38c9c1f rewrite browser tests to work without runner
• d0fd268 upgrade puppeteer 5.5.0 => 19.2.2
• daccf02 fix #2683: esbuild-wasm broken in node v19
• ecc9eeb fix #2677: token unit escaping and unicode-range
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from eslint's releases.

v8.28.0

Features

• 63bce44 feat: add ignoreClassFieldInitialValues option to no-magic-numbers (#16539) (Milos Djermanovic)
• 8385ecd feat: multiline properties in rule key-spacing with option align (#16532) (Francesco Trotta)
• a4e89db feat: no-obj-calls support Intl (#16543) (Sosuke Suzuki)

Bug Fixes

• c50ae4f fix: Ensure that dot files are found with globs. (#16550) (Nicholas C. Zakas)
• 9432b67 fix: throw error for first unmatched pattern (#16533) (Milos Djermanovic)
• e76c382 fix: allow * 1 when followed by / in no-implicit-coercion (#16522) (Milos Djermanovic)

Documentation

• 34c05a7 docs: Language Options page intro and tweaks (#16511) (Ben Perlmutter)
• 3e66387 docs: add intro and edit ignoring files page (#16510) (Ben Perlmutter)
• 436f712 docs: fix Header UI inconsistency (#16464) (Tanuj Kanti)
• f743816 docs: switch to wrench emoji for auto-fixable rules (#16545) (Bryan Mishkin)
• bc0547e docs: improve styles for versions and languages page (#16553) (Nitin Kumar)
• 6070f58 docs: clarify esquery issue workaround (#16556) (Milos Djermanovic)
• b48e4f8 docs: Command Line Interface intro and tweaks (#16535) (Ben Perlmutter)
• b92b30f docs: Add Rules page intro and content tweaks (#16523) (Ben Perlmutter)
• 1769b42 docs: Integrations page introduction (#16548) (Ben Perlmutter)
• a8d0a57 docs: make table of contents sticky on desktop (#16506) (Sam Chen)
• a01315a docs: fix route of japanese translation site (#16542) (Tanuj Kanti)
• 0515628 docs: use emoji instead of svg for deprecated rule (#16536) (Bryan Mishkin)
• 68f1288 docs: set default layouts (#16484) (Percy Ma)
• 776827a docs: init config about specifying shared configs (#16483) (Percy Ma)
• 5c39425 docs: fix broken link to plugins (#16520) (Ádám T. Nagy)
• c97c789 docs: Add missing no-new-native-nonconstructor docs code fence (#16503) (Brandon Mills)

Chores

• e94a4a9 chore: Add tests to verify #16038 is fixed (#16538) (Nicholas C. Zakas)
• e13f194 chore: stricter validation of meta.docs.description in core rules (#16529) (Milos Djermanovic)
• 72dbfbc chore: use pkg parameter in getNpmPackageVersion (#16525) (webxmsj)

v8.27.0

Features

• f14587c feat: new no-new-native-nonconstructor rule (#16368) (Sosuke Suzuki)
• 978799b feat: add new rule no-empty-static-block (#16325) (Sosuke Suzuki)
• 69216ee feat: no-empty suggest to add comment in empty BlockStatement (#16470) (Nitin Kumar)
• 319f0a5 feat: use context.languageOptions.ecmaVersion in core rules (#16458) (Milos Djermanovic)

Bug Fixes

• c3ce521 fix: Ensure unmatched glob patterns throw an error (#16462) (Nicholas C. Zakas)
• 886a038 fix: handle files with unspecified path in getRulesMetaForResults (#16437) (Francesco Trotta)

Documentation

• ce93b42 docs: Stylelint property-no-unknown (#16497) (Nick Schonning)
• d2cecb4 docs: Stylelint declaration-block-no-shorthand-property-overrides (#16498) (Nick Schonning)
• 0a92805 docs: stylelint color-hex-case (#16496) (Nick Schonning)
• 74a5af4 docs: fix stylelint error (#16491) (Milos Djermanovic)

... (truncated)

Sourced from eslint's changelog.

v8.28.0 - November 18, 2022

• 34c05a7 docs: Language Options page intro and tweaks (#16511) (Ben Perlmutter)
• 3e66387 docs: add intro and edit ignoring files page (#16510) (Ben Perlmutter)
• 436f712 docs: fix Header UI inconsistency (#16464) (Tanuj Kanti)
• f743816 docs: switch to wrench emoji for auto-fixable rules (#16545) (Bryan Mishkin)
• bc0547e docs: improve styles for versions and languages page (#16553) (Nitin Kumar)
• 6070f58 docs: clarify esquery issue workaround (#16556) (Milos Djermanovic)
• b48e4f8 docs: Command Line Interface intro and tweaks (#16535) (Ben Perlmutter)
• b92b30f docs: Add Rules page intro and content tweaks (#16523) (Ben Perlmutter)
• 1769b42 docs: Integrations page introduction (#16548) (Ben Perlmutter)
• 63bce44 feat: add ignoreClassFieldInitialValues option to no-magic-numbers (#16539) (Milos Djermanovic)
• c50ae4f fix: Ensure that dot files are found with globs. (#16550) (Nicholas C. Zakas)
• a8d0a57 docs: make table of contents sticky on desktop (#16506) (Sam Chen)
• 9432b67 fix: throw error for first unmatched pattern (#16533) (Milos Djermanovic)
• 8385ecd feat: multiline properties in rule key-spacing with option align (#16532) (Francesco Trotta)
• a4e89db feat: no-obj-calls support Intl (#16543) (Sosuke Suzuki)
• a01315a docs: fix route of japanese translation site (#16542) (Tanuj Kanti)
• e94a4a9 chore: Add tests to verify #16038 is fixed (#16538) (Nicholas C. Zakas)
• 0515628 docs: use emoji instead of svg for deprecated rule (#16536) (Bryan Mishkin)
• e76c382 fix: allow * 1 when followed by / in no-implicit-coercion (#16522) (Milos Djermanovic)
• 68f1288 docs: set default layouts (#16484) (Percy Ma)
• e13f194 chore: stricter validation of meta.docs.description in core rules (#16529) (Milos Djermanovic)
• 776827a docs: init config about specifying shared configs (#16483) (Percy Ma)
• 72dbfbc chore: use pkg parameter in getNpmPackageVersion (#16525) (webxmsj)
• 5c39425 docs: fix broken link to plugins (#16520) (Ádám T. Nagy)
• c97c789 docs: Add missing no-new-native-nonconstructor docs code fence (#16503) (Brandon Mills)

v8.27.0 - November 6, 2022

• f14587c feat: new no-new-native-nonconstructor rule (#16368) (Sosuke Suzuki)
• 978799b feat: add new rule no-empty-static-block (#16325) (Sosuke Suzuki)
• ce93b42 docs: Stylelint property-no-unknown (#16497) (Nick Schonning)
• d2cecb4 docs: Stylelint declaration-block-no-shorthand-property-overrides (#16498) (Nick Schonning)
• 0a92805 docs: stylelint color-hex-case (#16496) (Nick Schonning)
• c3ce521 fix: Ensure unmatched glob patterns throw an error (#16462) (Nicholas C. Zakas)
• 74a5af4 docs: fix stylelint error (#16491) (Milos Djermanovic)
• 69216ee feat: no-empty suggest to add comment in empty BlockStatement (#16470) (Nitin Kumar)
• 324db1a docs: explicit stylelint color related rules (#16465) (Nick Schonning)
• 94dc4f1 docs: use Stylelint for HTML files (#16468) (Nick Schonning)
• cc6128d docs: enable stylelint declaration-block-no-duplicate-properties (#16466) (Nick Schonning)
• d03a8bf docs: Add heading to justification explanation (#16430) (Maritaria)
• 886a038 fix: handle files with unspecified path in getRulesMetaForResults (#16437) (Francesco Trotta)
• 319f0a5 feat: use context.languageOptions.ecmaVersion in core rules (#16458) (Milos Djermanovic)
• 8a15968 docs: add Stylelint configuration and cleanup (#16379) (Nick Schonning)
• 9b0a469 docs: note commit messages don't support scope (#16435) (Andy Edwards)
• 1581405 docs: improve context.getScope() docs (#16417) (Ben Perlmutter)
• b797149 docs: update formatters template (#16454) (Milos Djermanovic)
• 5ac4de9 docs: fix link to formatters on the Core Concepts page (#16455) (Vladislav)
• 33313ef docs: core-concepts: fix link to semi rule (#16453) (coderaiser)

... (truncated)

• b8769f1 8.28.0
• d2b0723 Build: changelog update for 8.28.0
• 34c05a7 docs: Language Options page intro and tweaks (#16511)
• 3e66387 docs: add intro and edit ignoring files page (#16510)
• 436f712 docs: fix Header UI inconsistency (#16464)
• f743816 docs: switch to wrench emoji for auto-fixable rules (#16545)
• bc0547e docs: improve styles for versions and languages page (#16553)
• 6070f58 docs: clarify esquery issue workaround (#16556)
• b48e4f8 docs: Command Line Interface intro and tweaks (#16535)
• b92b30f docs: Add Rules page intro and content tweaks (#16523)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.14

• Fix parsing of TypeScript infer inside a conditional extends (#2675)

  Unlike JavaScript, parsing TypeScript sometimes requires backtracking. The infer A type operator can take an optional constraint of the form infer A extends B. However, this syntax conflicts with the similar conditional type operator A extends B ? C : D in cases where the syntax is combined, such as infer A extends B ? C : D. This is supposed to be parsed as (infer A) extends B ? C : D. Previously esbuild incorrectly parsed this as (infer A extends B) ? C : D instead, which is a parse error since the ?: conditional operator requires the extends keyword as part of the conditional type. TypeScript disambiguates by speculatively parsing the extends after the infer, but backtracking if a ? token is encountered afterward. With this release, esbuild should now do the same thing, so esbuild should now correctly parse these types. Here's a real-world example of such a type:

  type Normalized<T> = T extends Array<infer A extends object ? infer A : never>
    ? Dictionary<Normalized<A>>
    : {
        [P in keyof T]: T[P] extends Array<infer A extends object ? infer A : never>
          ? Dictionary<Normalized<A>>
          : Normalized<T[P]>
      }
  

• Avoid unnecessary watch mode rebuilds when debug logging is enabled (#2661)

  When debug-level logs are enabled (such as with --log-level=debug), esbuild's path resolution subsystem generates debug log messages that say something like "Read 20 entries for directory /home/user" to help you debug what esbuild's path resolution is doing. This caused esbuild's watch mode subsystem to add a dependency on the full list of entries in that directory since if that changes, the generated log message would also have to be updated. However, meant that on systems where a parent directory undergoes constant directory entry churn, esbuild's watch mode would continue to rebuild if --log-level=debug was passed.

  With this release, these debug log messages are now generated by "peeking" at the file system state while bypassing esbuild's watch mode dependency tracking. So now watch mode doesn't consider the count of directory entries in these debug log messages to be a part of the build that needs to be kept up to date when the file system state changes.

v0.15.13

• Add support for the TypeScript 4.9 satisfies operator (#2509)

  TypeScript 4.9 introduces a new operator called satisfies that lets you check that a given value satisfies a less specific type without casting it to that less specific type and without generating any additional code at run-time. It looks like this:

  const value = { foo: 1, bar: false } satisfies Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript knows that "foo" is a number here
  

  Before this existed, you could use a cast with as to check that a value satisfies a less specific type, but that removes any additional knowledge that TypeScript has about that specific value:

  const value = { foo: 1, bar: false } as Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript no longer knows that "foo" is a number
  

  You can read more about this feature in TypeScript's blog post for 4.9 as well as the associated TypeScript issue for this feature.

  This feature was implemented in esbuild by @​magic-akari.

• Fix watch mode constantly rebuilding if the parent directory is inaccessible (#2640)

  Android is unusual in that it has an inaccessible directory in the path to the root, which esbuild was not originally built to handle. To handle cases like this, the path resolution layer in esbuild has a hack where it treats inaccessible directories as empty. However, esbuild's watch implementation currently triggers a rebuild if a directory previously encountered an error but the directory now exists. The assumption is that the previous error was caused by the directory not existing. Although that's usually the case, it's not the case for this particular parent directory on Android. Instead the error is that the directory previously existed but was inaccessible.

  This discrepancy between esbuild's path resolution layer and its watch mode was causing watch mode to rebuild continuously on Android. With this release, esbuild's watch mode instead checks for an error status change in the readdir file system call, so watch mode should no longer rebuild continuously on Android.

• Apply a fix for a rare deadlock with the JavaScript API (#1842, #2485)

... (truncated)

Sourced from esbuild's changelog.

0.15.14

• Fix parsing of TypeScript infer inside a conditional extends (#2675)

  Unlike JavaScript, parsing TypeScript sometimes requires backtracking. The infer A type operator can take an optional constraint of the form infer A extends B. However, this syntax conflicts with the similar conditional type operator A extends B ? C : D in cases where the syntax is combined, such as infer A extends B ? C : D. This is supposed to be parsed as (infer A) extends B ? C : D. Previously esbuild incorrectly parsed this as (infer A extends B) ? C : D instead, which is a parse error since the ?: conditional operator requires the extends keyword as part of the conditional type. TypeScript disambiguates by speculatively parsing the extends after the infer, but backtracking if a ? token is encountered afterward. With this release, esbuild should now do the same thing, so esbuild should now correctly parse these types. Here's a real-world example of such a type:

  type Normalized<T> = T extends Array<infer A extends object ? infer A : never>
    ? Dictionary<Normalized<A>>
    : {
        [P in keyof T]: T[P] extends Array<infer A extends object ? infer A : never>
          ? Dictionary<Normalized<A>>
          : Normalized<T[P]>
      }
  

• Avoid unnecessary watch mode rebuilds when debug logging is enabled (#2661)

  When debug-level logs are enabled (such as with --log-level=debug), esbuild's path resolution subsystem generates debug log messages that say something like "Read 20 entries for directory /home/user" to help you debug what esbuild's path resolution is doing. This caused esbuild's watch mode subsystem to add a dependency on the full list of entries in that directory since if that changes, the generated log message would also have to be updated. However, meant that on systems where a parent directory undergoes constant directory entry churn, esbuild's watch mode would continue to rebuild if --log-level=debug was passed.

  With this release, these debug log messages are now generated by "peeking" at the file system state while bypassing esbuild's watch mode dependency tracking. So now watch mode doesn't consider the count of directory entries in these debug log messages to be a part of the build that needs to be kept up to date when the file system state changes.

0.15.13

• Add support for the TypeScript 4.9 satisfies operator (#2509)

  TypeScript 4.9 introduces a new operator called satisfies that lets you check that a given value satisfies a less specific type without casting it to that less specific type and without generating any additional code at run-time. It looks like this:

  const value = { foo: 1, bar: false } satisfies Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript knows that "foo" is a number here
  

  Before this existed, you could use a cast with as to check that a value satisfies a less specific type, but that removes any additional knowledge that TypeScript has about that specific value:

  const value = { foo: 1, bar: false } as Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript no longer knows that "foo" is a number
  

  You can read more about this feature in TypeScript's blog post for 4.9 as well as the associated TypeScript issue for this feature.

  This feature was implemented in esbuild by @​magic-akari.

• Fix watch mode constantly rebuilding if the parent directory is inaccessible (#2640)

  Android is unusual in that it has an inaccessible directory in the path to the root, which esbuild was not originally built to handle. To handle cases like this, the path resolution layer in esbuild has a hack where it treats inaccessible directories as empty. However, esbuild's watch implementation currently triggers a rebuild if a directory previously encountered an error but the directory now exists. The assumption is that the previous error was caused by the directory not existing. Although that's usually the case, it's not the case for this particular parent directory on Android. Instead the error is that the directory previously existed but was inaccessible.

  This discrepancy between esbuild's path resolution layer and its watch mode was causing watch mode to rebuild continuously on Android. With this release, esbuild's watch mode instead checks for an error status change in the readdir file system call, so watch mode should no longer rebuild continuously on Android.

... (truncated)

• d0f6b7f publish 0.15.14 to npm
• 5ecf746 GitHub Workflows security hardening (#2654)
• 9dee65c fix #2675: parsing of infer inside extends
• c6e880a fix #2661: avoid extra rebuilds with debug logging
• ba47710 publish 0.15.13 to npm
• 679548f small code simplification
• 78d6194 attempted fix for #2485: Add and Wait safety
• 4f9694b fix a typo
• 8d0c2b9 update go 1.19.2 => 1.19.3
• 8c2fdc2 support TypeScript satisfies (#2509)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from eslint's releases.

v8.27.0

Features

• f14587c feat: new no-new-native-nonconstructor rule (#16368) (Sosuke Suzuki)
• 978799b feat: add new rule no-empty-static-block (#16325) (Sosuke Suzuki)
• 69216ee feat: no-empty suggest to add comment in empty BlockStatement (#16470) (Nitin Kumar)
• 319f0a5 feat: use context.languageOptions.ecmaVersion in core rules (#16458) (Milos Djermanovic)

Bug Fixes

• c3ce521 fix: Ensure unmatched glob patterns throw an error (#16462) (Nicholas C. Zakas)
• 886a038 fix: handle files with unspecified path in getRulesMetaForResults (#16437) (Francesco Trotta)

Documentation

• ce93b42 docs: Stylelint property-no-unknown (#16497) (Nick Schonning)
• d2cecb4 docs: Stylelint declaration-block-no-shorthand-property-overrides (#16498) (Nick Schonning)
• 0a92805 docs: stylelint color-hex-case (#16496) (Nick Schonning)
• 74a5af4 docs: fix stylelint error (#16491) (Milos Djermanovic)
• 324db1a docs: explicit stylelint color related rules (#16465) (Nick Schonning)
• 94dc4f1 docs: use Stylelint for HTML files (#16468) (Nick Schonning)
• cc6128d docs: enable stylelint declaration-block-no-duplicate-properties (#16466) (Nick Schonning)
• d03a8bf docs: Add heading to justification explanation (#16430) (Maritaria)
• 8a15968 docs: add Stylelint configuration and cleanup (#16379) (Nick Schonning)
• 9b0a469 docs: note commit messages don't support scope (#16435) (Andy Edwards)
• 1581405 docs: improve context.getScope() docs (#16417) (Ben Perlmutter)
• b797149 docs: update formatters template (#16454) (Milos Djermanovic)
• 5ac4de9 docs: fix link to formatters on the Core Concepts page (#16455) (Vladislav)
• 33313ef docs: core-concepts: fix link to semi rule (#16453) (coderaiser)

v8.26.0

Features

• 4715787 feat: check Object.create() in getter-return (#16420) (Yuki Hirasawa)
• 28d1902 feat: no-implicit-globals supports exported block comment (#16343) (Sosuke Suzuki)
• e940be7 feat: Use ESLINT_USE_FLAT_CONFIG environment variable for flat config (#16356) (Tomer Aberbach)
• dd0c58f feat: Swap out Globby for custom globbing solution. (#16369) (Nicholas C. Zakas)

Bug Fixes

• df77409 fix: use baseConfig constructor option in FlatESLint (#16432) (Milos Djermanovic)
• 33668ee fix: Ensure that glob patterns are matched correctly. (#16449) (Nicholas C. Zakas)
• 740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409) (Francesco Trotta)
• 8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425) (Milos Djermanovic)
• 325ad37 fix: make getRulesMetaForResults return a plain object in trivial case (#16438) (Francesco Trotta)
• a2810bc fix: Ensure that directories can be unignored. (#16436) (Nicholas C. Zakas)
• 35916ad fix: Ensure unignore and reignore work correctly in flat config. (#16422) (Nicholas C. Zakas)

Documentation

• 651649b docs: Core concepts page (#16399) (Ben Perlmutter)
• 631cf72 docs: note --ignore-path not supported with flat config (#16434) (Andy Edwards)
• 1692840 docs: fix syntax in examples for new config files (#16427) (Milos Djermanovic)
• d336cfc docs: Document extending plugin with new config (#16394) (Ben Perlmutter)

Chores

... (truncated)

Sourced from eslint's changelog.

v8.27.0 - November 6, 2022

• f14587c feat: new no-new-native-nonconstructor rule (#16368) (Sosuke Suzuki)
• 978799b feat: add new rule no-empty-static-block (#16325) (Sosuke Suzuki)
• ce93b42 docs: Stylelint property-no-unknown (#16497) (Nick Schonning)
• d2cecb4 docs: Stylelint declaration-block-no-shorthand-property-overrides (#16498) (Nick Schonning)
• 0a92805 docs: stylelint color-hex-case (#16496) (Nick Schonning)
• c3ce521 fix: Ensure unmatched glob patterns throw an error (#16462) (Nicholas C. Zakas)
• 74a5af4 docs: fix stylelint error (#16491) (Milos Djermanovic)
• 69216ee feat: no-empty suggest to add comment in empty BlockStatement (#16470) (Nitin Kumar)
• 324db1a docs: explicit stylelint color related rules (#16465) (Nick Schonning)
• 94dc4f1 docs: use Stylelint for HTML files (#16468) (Nick Schonning)
• cc6128d docs: enable stylelint declaration-block-no-duplicate-properties (#16466) (Nick Schonning)
• d03a8bf docs: Add heading to justification explanation (#16430) (Maritaria)
• 886a038 fix: handle files with unspecified path in getRulesMetaForResults (#16437) (Francesco Trotta)
• 319f0a5 feat: use context.languageOptions.ecmaVersion in core rules (#16458) (Milos Djermanovic)
• 8a15968 docs: add Stylelint configuration and cleanup (#16379) (Nick Schonning)
• 9b0a469 docs: note commit messages don't support scope (#16435) (Andy Edwards)
• 1581405 docs: improve context.getScope() docs (#16417) (Ben Perlmutter)
• b797149 docs: update formatters template (#16454) (Milos Djermanovic)
• 5ac4de9 docs: fix link to formatters on the Core Concepts page (#16455) (Vladislav)
• 33313ef docs: core-concepts: fix link to semi rule (#16453) (coderaiser)

v8.26.0 - October 21, 2022

• df77409 fix: use baseConfig constructor option in FlatESLint (#16432) (Milos Djermanovic)
• 33668ee fix: Ensure that glob patterns are matched correctly. (#16449) (Nicholas C. Zakas)
• 651649b docs: Core concepts page (#16399) (Ben Perlmutter)
• 4715787 feat: check Object.create() in getter-return (#16420) (Yuki Hirasawa)
• e917a9a ci: add node v19 (#16443) (Koichi ITO)
• 740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409) (Francesco Trotta)
• 8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425) (Milos Djermanovic)
• 325ad37 fix: make getRulesMetaForResults return a plain object in trivial case (#16438) (Francesco Trotta)
• a2810bc fix: Ensure that directories can be unignored. (#16436) (Nicholas C. Zakas)
• 631cf72 docs: note --ignore-path not supported with flat config (#16434) (Andy Edwards)
• 1692840 docs: fix syntax in examples for new config files (#16427) (Milos Djermanovic)
• 28d1902 feat: no-implicit-globals supports exported block comment (#16343) (Sosuke Suzuki)
• 35916ad fix: Ensure unignore and reignore work correctly in flat config. (#16422) (Nicholas C. Zakas)
• 4b70b91 chore: Add VS Code issues link (#16423) (Nicholas C. Zakas)
• e940be7 feat: Use ESLINT_USE_FLAT_CONFIG environment variable for flat config (#16356) (Tomer Aberbach)
• d336cfc docs: Document extending plugin with new config (#16394) (Ben Perlmutter)
• dd0c58f feat: Swap out Globby for custom globbing solution. (#16369) (Nicholas C. Zakas)
• 232d291 chore: suppress a Node.js deprecation warning (#16398) (Koichi ITO)

v8.25.0 - October 7, 2022

• 1f78594 chore: upgrade @​eslint/eslintrc@​1.3.3 (#16397) (Milos Djermanovic)
• 173e820 feat: Pass --max-warnings value to formatters (#16348) (Brandon Mills)
• 8476a9b chore: Remove CODEOWNERS (#16375) (Nick Schonning)
• 720ff75 chore: use "ci" for Dependabot commit message (#16377) (Nick Schonning)

... (truncated)

• e950964 8.27.0
• 631c91f Build: changelog update for 8.27.0
• f14587c feat: new no-new-native-nonconstructor rule (#16368)
• 978799b feat: add new rule no-empty-static-block (#16325)
• ce93b42 docs: Stylelint property-no-unknown (#16497)
• d2cecb4 docs: Stylelint declaration-block-no-shorthand-property-overrides (#16498)
• 0a92805 docs: stylelint color-hex-case (#16496)
• c3ce521 fix: Ensure unmatched glob patterns throw an error (#16462)
• 74a5af4 docs: fix stylelint error (#16491)
• 69216ee feat: no-empty suggest to add comment in empty BlockStatement (#16470)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.13

• Add support for the TypeScript 4.9 satisfies operator (#2509)

  TypeScript 4.9 introduces a new operator called satisfies that lets you check that a given value satisfies a less specific type without casting it to that less specific type and without generating any additional code at run-time. It looks like this:

  const value = { foo: 1, bar: false } satisfies Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript knows that "foo" is a number here
  

  Before this existed, you could use a cast with as to check that a value satisfies a less specific type, but that removes any additional knowledge that TypeScript has about that specific value:

  const value = { foo: 1, bar: false } as Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript no longer knows that "foo" is a number
  

  You can read more about this feature in TypeScript's blog post for 4.9 as well as the associated TypeScript issue for this feature.

  This feature was implemented in esbuild by @​magic-akari.

• Fix watch mode constantly rebuilding if the parent directory is inaccessible (#2640)

  Android is unusual in that it has an inaccessible directory in the path to the root, which esbuild was not originally built to handle. To handle cases like this, the path resolution layer in esbuild has a hack where it treats inaccessible directories as empty. However, esbuild's watch implementation currently triggers a rebuild if a directory previously encountered an error but the directory now exists. The assumption is that the previous error was caused by the directory not existing. Although that's usually the case, it's not the case for this particular parent directory on Android. Instead the error is that the directory previously existed but was inaccessible.

  This discrepancy between esbuild's path resolution layer and its watch mode was causing watch mode to rebuild continuously on Android. With this release, esbuild's watch mode instead checks for an error status change in the readdir file system call, so watch mode should no longer rebuild continuously on Android.

• Apply a fix for a rare deadlock with the JavaScript API (#1842, #2485)

  There have been reports of esbuild sometimes exiting with an "all goroutines are asleep" deadlock message from the Go language runtime. This issue hasn't made much progress until recently, where a possible cause was discovered (thanks to @​jfirebaugh for the investigation). This release contains a possible fix for that possible cause, so this deadlock may have been fixed. The fix cannot be easily verified because the deadlock is non-deterministic and rare. If this was indeed the cause, then this issue only affected the JavaScript API in situations where esbuild was already in the process of exiting.

  In detail: The underlying cause is that Go's sync.WaitGroup API for waiting for a set of goroutines to finish is not fully thread-safe. Specifically it's not safe to call Add() concurrently with Wait() when the wait group counter is zero due to a data race. This situation could come up with esbuild's JavaScript API when the host JavaScript process closes the child process's stdin and the child process (with no active tasks) calls Wait() to check that there are no active tasks, at the same time as esbuild's watchdog timer calls Add() to add an active task (that pings the host to see if it's still there). The fix in this release is to avoid calling Add() once we learn that stdin has been closed but before we call Wait().

v0.15.12

• Fix minifier correctness bug with single-use substitutions (#2619)

  When minification is enabled, esbuild will attempt to eliminate variables that are only used once in certain cases. For example, esbuild minifies this code:

  function getEmailForUser(name) {
    let users = db.table('users');
    let user = users.find({ name });
    let email = user?.get('email');
    return email;
  }
  

  into this code:

... (truncated)

Sourced from esbuild's changelog.

0.15.13

• Add support for the TypeScript 4.9 satisfies operator (#2509)

  TypeScript 4.9 introduces a new operator called satisfies that lets you check that a given value satisfies a less specific type without casting it to that less specific type and without generating any additional code at run-time. It looks like this:

  const value = { foo: 1, bar: false } satisfies Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript knows that "foo" is a number here
  

  Before this existed, you could use a cast with as to check that a value satisfies a less specific type, but that removes any additional knowledge that TypeScript has about that specific value:

  const value = { foo: 1, bar: false } as Record<string, number | boolean>
  console.log(value.foo.toFixed(1)) // TypeScript no longer knows that "foo" is a number
  

  You can read more about this feature in TypeScript's blog post for 4.9 as well as the associated TypeScript issue for this feature.

  This feature was implemented in esbuild by @​magic-akari.

• Fix watch mode constantly rebuilding if the parent directory is inaccessible (#2640)

  Android is unusual in that it has an inaccessible directory in the path to the root, which esbuild was not originally built to handle. To handle cases like this, the path resolution layer in esbuild has a hack where it treats inaccessible directories as empty. However, esbuild's watch implementation currently triggers a rebuild if a directory previously encountered an error but the directory now exists. The assumption is that the previous error was caused by the directory not existing. Although that's usually the case, it's not the case for this particular parent directory on Android. Instead the error is that the directory previously existed but was inaccessible.

  This discrepancy between esbuild's path resolution layer and its watch mode was causing watch mode to rebuild continuously on Android. With this release, esbuild's watch mode instead checks for an error status change in the readdir file system call, so watch mode should no longer rebuild continuously on Android.

• Apply a fix for a rare deadlock with the JavaScript API (#1842, #2485)

  There have been reports of esbuild sometimes exiting with an "all goroutines are asleep" deadlock message from the Go language runtime. This issue hasn't made much progress until recently, where a possible cause was discovered (thanks to @​jfirebaugh for the investigation). This release contains a possible fix for that possible cause, so this deadlock may have been fixed. The fix cannot be easily verified because the deadlock is non-deterministic and rare. If this was indeed the cause, then this issue only affected the JavaScript API in situations where esbuild was already in the process of exiting.

  In detail: The underlying cause is that Go's sync.WaitGroup API for waiting for a set of goroutines to finish is not fully thread-safe. Specifically it's not safe to call Add() concurrently with Wait() when the wait group counter is zero due to a data race. This situation could come up with esbuild's JavaScript API when the host JavaScript process closes the child process's stdin and the child process (with no active tasks) calls Wait() to check that there are no active tasks, at the same time as esbuild's watchdog timer calls Add() to add an active task (that pings the host to see if it's still there). The fix in this release is to avoid calling Add() once we learn that stdin has been closed but before we call Wait().

0.15.12

• Fix minifier correctness bug with single-use substitutions (#2619)

  When minification is enabled, esbuild will attempt to eliminate variables that are only used once in certain cases. For example, esbuild minifies this code:

  function getEmailForUser(name) {
    let users = db.table('users');
    let user = users.find({ name });
    let email = user?.get('email');
    return email;
  }
  

  into this code:

... (truncated)

• ba47710 publish 0.15.13 to npm
• 679548f small code simplification
• 78d6194 attempted fix for #2485: Add and Wait safety
• 4f9694b fix a typo
• 8d0c2b9 update go 1.19.2 => 1.19.3
• 8c2fdc2 support TypeScript satisfies (#2509)
• 97d6dba fix #2640: watch mode checks readdir, not stat
• 223e6ea publish 0.15.12 to npm
• ccc8e8b fix #2619: bug with single-use substitutions
• 4608721 ci: update github actions (#2612)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from eslint's releases.

v8.26.0

Features

• 4715787 feat: check Object.create() in getter-return (#16420) (Yuki Hirasawa)
• 28d1902 feat: no-implicit-globals supports exported block comment (#16343) (Sosuke Suzuki)
• e940be7 feat: Use ESLINT_USE_FLAT_CONFIG environment variable for flat config (#16356) (Tomer Aberbach)
• dd0c58f feat: Swap out Globby for custom globbing solution. (#16369) (Nicholas C. Zakas)

Bug Fixes

• df77409 fix: use baseConfig constructor option in FlatESLint (#16432) (Milos Djermanovic)
• 33668ee fix: Ensure that glob patterns are matched correctly. (#16449) (Nicholas C. Zakas)
• 740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409) (Francesco Trotta)
• 8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425) (Milos Djermanovic)
• 325ad37 fix: make getRulesMetaForResults return a plain object in trivial case (#16438) (Francesco Trotta)
• a2810bc fix: Ensure that directories can be unignored. (#16436) (Nicholas C. Zakas)
• 35916ad fix: Ensure unignore and reignore work correctly in flat config. (#16422) (Nicholas C. Zakas)

Documentation

• 651649b docs: Core concepts page (#16399) (Ben Perlmutter)
• 631cf72 docs: note --ignore-path not supported with flat config (#16434) (Andy Edwards)
• 1692840 docs: fix syntax in examples for new config files (#16427) (Milos Djermanovic)
• d336cfc docs: Document extending plugin with new config (#16394) (Ben Perlmutter)

Chores

• e917a9a ci: add node v19 (#16443) (Koichi ITO)
• 4b70b91 chore: Add VS Code issues link (#16423) (Nicholas C. Zakas)
• 232d291 chore: suppress a Node.js deprecation warning (#16398) (Koichi ITO)

v8.25.0

Features

• 173e820 feat: Pass --max-warnings value to formatters (#16348) (Brandon Mills)
• 6964cb1 feat: remove support for ignore files in FlatESLint (#16355) (Milos Djermanovic)
• 1cc4b3a feat: id-length counts graphemes instead of code units (#16321) (Sosuke Suzuki)

Documentation

• 90c6028 docs: Conflicting fixes (#16366) (Ben Perlmutter)
• 5a3fe70 docs: Add VS to integrations page (#16381) (Maria José Solano)
• 49bd1e5 docs: remove unused link definitions (#16376) (Nick Schonning)
• 3bd380d docs: typo cleanups for docs (#16374) (Nick Schonning)
• b3a0837 docs: remove duplicate words (#16378) (Nick Schonning)
• a682562 docs: add BigInt to new-cap docs (#16362) (Sosuke Suzuki)
• f6d57fb docs: Update docs README (#16352) (Ben Perlmutter)
• 7214347 docs: fix logical-assignment-operators option typo (#16346) (Jonathan Wilsson)

Chores

• 1f78594 chore: upgrade @​eslint/eslintrc@​1.3.3 (#16397) (Milos Djermanovic)
• 8476a9b chore: Remove CODEOWNERS (#16375) (Nick Schonning)
• 720ff75 chore: use "ci" for Dependabot commit message (#16377) (Nick Schonning)
• 42f5479 chore: bump actions/stale from 5 to 6 (#16350) (dependabot[bot])
• e5e9e27 chore: remove jsdoc dev dependency (#16344) (Milos Djermanovic)

... (truncated)

Sourced from eslint's changelog.

v8.26.0 - October 21, 2022

• df77409 fix: use baseConfig constructor option in FlatESLint (#16432) (Milos Djermanovic)
• 33668ee fix: Ensure that glob patterns are matched correctly. (#16449) (Nicholas C. Zakas)
• 651649b docs: Core concepts page (#16399) (Ben Perlmutter)
• 4715787 feat: check Object.create() in getter-return (#16420) (Yuki Hirasawa)
• e917a9a ci: add node v19 (#16443) (Koichi ITO)
• 740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409) (Francesco Trotta)
• 8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425) (Milos Djermanovic)
• 325ad37 fix: make getRulesMetaForResults return a plain object in trivial case (#16438) (Francesco Trotta)
• a2810bc fix: Ensure that directories can be unignored. (#16436) (Nicholas C. Zakas)
• 631cf72 docs: note --ignore-path not supported with flat config (#16434) (Andy Edwards)
• 1692840 docs: fix syntax in examples for new config files (#16427) (Milos Djermanovic)
• 28d1902 feat: no-implicit-globals supports exported block comment (#16343) (Sosuke Suzuki)
• 35916ad fix: Ensure unignore and reignore work correctly in flat config. (#16422) (Nicholas C. Zakas)
• 4b70b91 chore: Add VS Code issues link (#16423) (Nicholas C. Zakas)
• e940be7 feat: Use ESLINT_USE_FLAT_CONFIG environment variable for flat config (#16356) (Tomer Aberbach)
• d336cfc docs: Document extending plugin with new config (#16394) (Ben Perlmutter)
• dd0c58f feat: Swap out Globby for custom globbing solution. (#16369) (Nicholas C. Zakas)
• 232d291 chore: suppress a Node.js deprecation warning (#16398) (Koichi ITO)

v8.25.0 - October 7, 2022

• 1f78594 chore: upgrade @​eslint/eslintrc@​1.3.3 (#16397) (Milos Djermanovic)
• 173e820 feat: Pass --max-warnings value to formatters (#16348) (Brandon Mills)
• 8476a9b chore: Remove CODEOWNERS (#16375) (Nick Schonning)
• 720ff75 chore: use "ci" for Dependabot commit message (#16377) (Nick Schonning)
• 90c6028 docs: Conflicting fixes (#16366) (Ben Perlmutter)
• 5a3fe70 docs: Add VS to integrations page (#16381) (Maria José Solano)
• 6964cb1 feat: remove support for ignore files in FlatESLint (#16355) (Milos Djermanovic)
• 49bd1e5 docs: remove unused link definitions (#16376) (Nick Schonning)
• 42f5479 chore: bump actions/stale from 5 to 6 (#16350) (dependabot[bot])
• 3bd380d docs: typo cleanups for docs (#16374) (Nick Schonning)
• b3a0837 docs: remove duplicate words (#16378) (Nick Schonning)
• a682562 docs: add BigInt to new-cap docs (#16362) (Sosuke Suzuki)
• 1cc4b3a feat: id-length counts graphemes instead of code units (#16321) (Sosuke Suzuki)
• f6d57fb docs: Update docs README (#16352) (Ben Perlmutter)
• e5e9e27 chore: remove jsdoc dev dependency (#16344) (Milos Djermanovic)
• 7214347 docs: fix logical-assignment-operators option typo (#16346) (Jonathan Wilsson)

v8.24.0 - September 23, 2022

• 131e646 chore: Upgrade @​humanwhocodes/config-array for perf (#16339) (Nicholas C. Zakas)
• 2c152ff docs: note false positive Object.getOwnPropertyNames in prefer-reflect (#16317) (AnnAngela)
• bf7bd88 docs: fix warn severity description for new config files (#16324) (Nitin Kumar)
• 504fe59 perf: switch from object spread to Object.assign when merging globals (#16311) (Milos Djermanovic)
• 1729f9e feat: account for sourceType: "commonjs" in the strict rule (#16308) (Milos Djermanovic)
• b0d72c9 feat: add rule logical-assignment-operators (#16102) (fnx)
• f02bcd9 feat: array-callback-return support findLast and findLastIndex (#16314) (Sosuke Suzuki)
• 8cc0bbe docs: use more clean link syntax (#16309) (Percy Ma)

... (truncated)

• 823b018 8.26.0
• dce6a71 Build: changelog update for 8.26.0
• 6c2be51 Revert "docs: update header (#16403)" (#16451)
• df77409 fix: use baseConfig constructor option in FlatESLint (#16432)
• 33668ee fix: Ensure that glob patterns are matched correctly. (#16449)
• 651649b docs: Core concepts page (#16399)
• 4715787 feat: check Object.create() in getter-return (#16420)
• e917a9a ci: add node v19 (#16443)
• 740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409)
• 8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.12

• Fix minifier correctness bug with single-use substitutions (#2619)

  When minification is enabled, esbuild will attempt to eliminate variables that are only used once in certain cases. For example, esbuild minifies this code:

  function getEmailForUser(name) {
    let users = db.table('users');
    let user = users.find({ name });
    let email = user?.get('email');
    return email;
  }
  

  into this code:

  function getEmailForUser(e){return db.table("users").find({name:e})?.get("email")}
  

  However, this transformation had a bug where esbuild did not correctly consider the "read" part of binary read-modify-write assignment operators. For example, it's incorrect to minify the following code into bar += fn() because the call to fn() might modify bar:

  const foo = fn();
  bar += foo;
  

  In addition to fixing this correctness bug, this release also improves esbuild's output in the case where all values being skipped over are primitives:

  function toneMapLuminance(r, g, b) {
    let hdr = luminance(r, g, b)
    let decay = 1 / (1 + hdr)
    return 1 - decay
  }
  

  Previous releases of esbuild didn't substitute these single-use variables here, but esbuild will now minify this to the following code starting with this release:

  function toneMapLuminance(e,n,a){return 1-1/(1+luminance(e,n,a))}
  

v0.15.11

• Fix various edge cases regarding template tags and this (#2610)

  This release fixes some bugs where the value of this wasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:

  async function test() {
  

... (truncated)

Sourced from esbuild's changelog.

0.15.12

• Fix minifier correctness bug with single-use substitutions (#2619)

  When minification is enabled, esbuild will attempt to eliminate variables that are only used once in certain cases. For example, esbuild minifies this code:

  function getEmailForUser(name) {
    let users = db.table('users');
    let user = users.find({ name });
    let email = user?.get('email');
    return email;
  }
  

  into this code:

  function getEmailForUser(e){return db.table("users").find({name:e})?.get("email")}
  

  However, this transformation had a bug where esbuild did not correctly consider the "read" part of binary read-modify-write assignment operators. For example, it's incorrect to minify the following code into bar += fn() because the call to fn() might modify bar:

  const foo = fn();
  bar += foo;
  

  In addition to fixing this correctness bug, this release also improves esbuild's output in the case where all values being skipped over are primitives:

  function toneMapLuminance(r, g, b) {
    let hdr = luminance(r, g, b)
    let decay = 1 / (1 + hdr)
    return 1 - decay
  }
  

  Previous releases of esbuild didn't substitute these single-use variables here, but esbuild will now minify this to the following code starting with this release:

  function toneMapLuminance(e,n,a){return 1-1/(1+luminance(e,n,a))}
  

0.15.11

• Fix various edge cases regarding template tags and this (#2610)

  This release fixes some bugs where the value of this wasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:

... (truncated)

• 223e6ea publish 0.15.12 to npm
• ccc8e8b fix #2619: bug with single-use substitutions
• 4608721 ci: update github actions (#2612)
• 0bb62e8 publish 0.15.11 to npm
• 9c89f14 update go 1.19.1 => 1.19.2
• 0d8ec0a fix #2610: template tag edge cases with this
• a4a45f3 fix indentation in tests
• 81fa2ca more info in yarn pnp error messages (#2585)
• fdbea94 fixes for NewStringInJSLog
• aaae34e publish 0.15.10 to npm
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.15.11

• Fix various edge cases regarding template tags and this (#2610)

  This release fixes some bugs where the value of this wasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:

  async function test() {
    class Foo { foo() { return this } }
    class Bar extends Foo {
      a = async () => super.foo``
      b = async () => super['foo']``
      c = async (foo) => super[foo]``
    }
    function foo() { return this }
    const obj = { foo }
    const bar = new Bar
    console.log(
      (await bar.a()) === bar,
      (await bar.b()) === bar,
      (await bar.c('foo')) === bar,
      { foo }.foo``.foo === foo,
      (true && obj.foo)`` !== obj,
      (false || obj.foo)`` !== obj,
      (null ?? obj.foo)`` !== obj,
    )
  }
  test()
  

  Each edge case in the code above previously incorrectly printed false when run through esbuild with --minify --target=es6 but now correctly prints true. These edge cases are unlikely to have affected real-world code.

v0.15.10

• Add support for node's "pattern trailers" syntax (#2569)

  After esbuild implemented node's exports feature in package.json, node changed the feature to also allow text after * wildcards in patterns. Previously the * was required to be at the end of the pattern. It lets you do something like this:

  {
    "exports": {
      "./features/*": "./features/*.js",
      "./features/*.js": "./features/*.js"
    }
  }
  

  With this release, esbuild now supports these types of patterns too.

• Fix subpath imports with Yarn PnP (#2545)

  Node has a little-used feature called subpath imports which are package-internal imports that start with # and that go through the imports map in package.json. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.

... (truncated)

Sourced from esbuild's changelog.

0.15.11

• Fix various edge cases regarding template tags and this (#2610)

  This release fixes some bugs where the value of this wasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:

  async function test() {
    class Foo { foo() { return this } }
    class Bar extends Foo {
      a = async () => super.foo``
      b = async () => super['foo']``
      c = async (foo) => super[foo]``
    }
    function foo() { return this }
    const obj = { foo }
    const bar = new Bar
    console.log(
      (await bar.a()) === bar,
      (await bar.b()) === bar,
      (await bar.c('foo')) === bar,
      { foo }.foo``.foo === foo,
      (true && obj.foo)`` !== obj,
      (false || obj.foo)`` !== obj,
      (null ?? obj.foo)`` !== obj,
    )
  }
  test()
  

  Each edge case in the code above previously incorrectly printed false when run through esbuild with --minify --target=es6 but now correctly prints true. These edge cases are unlikely to have affected real-world code.

0.15.10

• Add support for node's "pattern trailers" syntax (#2569)

  After esbuild implemented node's exports feature in package.json, node changed the feature to also allow text after * wildcards in patterns. Previously the * was required to be at the end of the pattern. It lets you do something like this:

  {
    "exports": {
      "./features/*": "./features/*.js",
      "./features/*.js": "./features/*.js"
    }
  }
  

  With this release, esbuild now supports these types of patterns too.

• Fix subpath imports with Yarn PnP (#2545)

... (truncated)

• 0bb62e8 publish 0.15.11 to npm
• 9c89f14 update go 1.19.1 => 1.19.2
• 0d8ec0a fix #2610: template tag edge cases with this
• a4a45f3 fix indentation in tests
• 81fa2ca more info in yarn pnp error messages (#2585)
• fdbea94 fixes for NewStringInJSLog
• aaae34e publish 0.15.10 to npm
• 4bd03f3 fix #1861, fix #2565: add cssBundle to metafile
• c55000d Fix subpath imports with Yarn PnP (#2547)
• 1bce251 fix transform tsconfigRaw type (#2568)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from esbuild's releases.

v0.16.3

• Fix a hang with the JS API in certain cases (#2727)

  A change that was made in version 0.15.13 accidentally introduced a case when using esbuild's JS API could cause the node process to fail to exit. The change broke esbuild's watchdog timer, which detects if the parent process no longer exists and then automatically exits esbuild. This hang happened when you ran node as a child process with the stderr stream set to pipe instead of inherit, in the child process you call esbuild's JS API and pass incremental: true but do not call dispose() on the returned rebuild object, and then call process.exit(). In that case the parent node process was still waiting for the esbuild process that was created by the child node process to exit. The change made in version 0.15.13 was trying to avoid using Go's sync.WaitGroup API incorrectly because the API is not thread-safe. Instead of doing this, I have now reverted that change and implemented a thread-safe version of the sync.WaitGroup API for esbuild to use instead.

v0.16.2

• Fix process.env.NODE_ENV substitution when transforming (#2718)

  Version 0.16.0 introduced an unintentional regression that caused process.env.NODE_ENV to be automatically substituted with either "development" or "production" when using esbuild's transform API. This substitution is a necessary feature of esbuild's build API because the React framework crashes when you bundle it without doing this. But the transform API is typically used as part of a larger build pipeline so the benefit of esbuild doing this automatically is not as clear, and esbuild previously didn't do this.

  However, version 0.16.0 switched the default value of the platform setting for the transform API from neutral to browser, both to align it with esbuild's documentation (which says browser is the default value) and because escaping the </script> character sequence is now tied to the browser platform (see the release notes for version 0.16.0 for details). That accidentally enabled automatic substitution of process.env.NODE_ENV because esbuild always did that for code meant for the browser. To fix this regression, esbuild will now only automatically substitute process.env.NODE_ENV when using the build API.

• Prevent define from substituting constants into assignment position (#2719)

  The define feature lets you replace certain expressions with constants. For example, you could use it to replace references to the global property reference window.DEBUG with false at compile time, which can then potentially help esbuild remove unused code from your bundle. It's similar to DefinePlugin in Webpack.

  However, if you write code such as window.DEBUG = true and then defined window.DEBUG to false, esbuild previously generated the output false = true which is a syntax error in JavaScript. This behavior is not typically a problem because it doesn't make sense to substitute window.DEBUG with a constant if its value changes at run-time (Webpack's DefinePlugin also generates false = true in this case). But it can be alarming to have esbuild generate code with a syntax error.

  So with this release, esbuild will no longer substitute define constants into assignment position to avoid generating code with a syntax error. Instead esbuild will generate a warning, which currently looks like this:

  ▲ [WARNING] Suspicious assignment to defined constant "window.DEBUG" [assign-to-define]
  example.js:1:0:
    1 │ window.DEBUG = true
      ╵ ~~~~~~~~~~~~
  
  The expression "window.DEBUG" has been configured to be replaced with a constant using the
  "define" feature. If this expression is supposed to be a compile-time constant, then it doesn't
  make sense to assign to it here. Or if this expression is supposed to change at run-time, this
  "define" substitution should be removed.
  

• Fix a regression with npm install --no-optional (#2720)

  Normally when you install esbuild with npm install, npm itself is the tool that downloads the correct binary executable for the current platform. This happens because of how esbuild's primary package uses npm's optionalDependencies feature. However, if you deliberately disable this with npm install --no-optional then esbuild's install script will attempt to repair the installation by manually downloading and extracting the binary executable from the package that was supposed to be installed.

  The change in version 0.16.0 to move esbuild's nested packages into the @esbuild/ scope unintentionally broke this logic because of how npm's URL structure is different for scoped packages vs. normal packages. It was actually already broken for a few platforms earlier because esbuild already had packages for some platforms in the @esbuild/ scope, but I didn't discover this then because esbuild's integration tests aren't run on all platforms. Anyway, this release contains some changes to the install script that should hopefully get this scenario working again.

v0.16.1

This is a hotfix for the previous release.

• Re-allow importing JSON with the copy loader using an import assertion

  The previous release made it so when assert { type: 'json' } is present on an import statement, esbuild validated that the json loader was used. This is what an import assertion is supposed to do. However, I forgot about the relatively new copy loader, which sort of behaves as if the import path was marked as external (and thus not loaded at all) except that the file is copied to the output directory and the import path is rewritten to point to the copy. In this case whatever JavaScript runtime ends up running the code is the one to evaluate the import assertion. So esbuild should really allow this case as well. With this release, esbuild now allows both the json and copy loaders when an assert { type: 'json' } import assertion is present.

v0.16.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.15.0 or ~0.15.0. See npm's documentation about semver for more information.

• Move all binary executable packages to the @esbuild/ scope

... (truncated)

Sourced from esbuild's changelog.

0.16.3

• Fix a hang with the JS API in certain cases (#2727)

  A change that was made in version 0.15.13 accidentally introduced a case when using esbuild's JS API could cause the node process to fail to exit. The change broke esbuild's watchdog timer, which detects if the parent process no longer exists and then automatically exits esbuild. This hang happened when you ran node as a child process with the stderr stream set to pipe instead of inherit, in the child process you call esbuild's JS API and pass incremental: true but do not call dispose() on the returned rebuild object, and then call process.exit(). In that case the parent node process was still waiting for the esbuild process that was created by the child node process to exit. The change made in version 0.15.13 was trying to avoid using Go's sync.WaitGroup API incorrectly because the API is not thread-safe. Instead of doing this, I have now reverted that change and implemented a thread-safe version of the sync.WaitGroup API for esbuild to use instead.

0.16.2

• Fix process.env.NODE_ENV substitution when transforming (#2718)

  Version 0.16.0 introduced an unintentional regression that caused process.env.NODE_ENV to be automatically substituted with either "development" or "production" when using esbuild's transform API. This substitution is a necessary feature of esbuild's build API because the React framework crashes when you bundle it without doing this. But the transform API is typically used as part of a larger build pipeline so the benefit of esbuild doing this automatically is not as clear, and esbuild previously didn't do this.

  However, version 0.16.0 switched the default value of the platform setting for the transform API from neutral to browser, both to align it with esbuild's documentation (which says browser is the default value) and because escaping the </script> character sequence is now tied to the browser platform (see the release notes for version 0.16.0 for details). That accidentally enabled automatic substitution of process.env.NODE_ENV because esbuild always did that for code meant for the browser. To fix this regression, esbuild will now only automatically substitute process.env.NODE_ENV when using the build API.

• Prevent define from substituting constants into assignment position (#2719)

  The define feature lets you replace certain expressions with constants. For example, you could use it to replace references to the global property reference window.DEBUG with false at compile time, which can then potentially help esbuild remove unused code from your bundle. It's similar to DefinePlugin in Webpack.

  However, if you write code such as window.DEBUG = true and then defined window.DEBUG to false, esbuild previously generated the output false = true which is a syntax error in JavaScript. This behavior is not typically a problem because it doesn't make sense to substitute window.DEBUG with a constant if its value changes at run-time (Webpack's DefinePlugin also generates false = true in this case). But it can be alarming to have esbuild generate code with a syntax error.

  So with this release, esbuild will no longer substitute define constants into assignment position to avoid generating code with a syntax error. Instead esbuild will generate a warning, which currently looks like this:

  ▲ [WARNING] Suspicious assignment to defined constant "window.DEBUG" [assign-to-define]
  example.js:1:0:
    1 │ window.DEBUG = true
      ╵ ~~~~~~~~~~~~
  
  The expression "window.DEBUG" has been configured to be replaced with a constant using the
  "define" feature. If this expression is supposed to be a compile-time constant, then it doesn't
  make sense to assign to it here. Or if this expression is supposed to change at run-time, this
  "define" substitution should be removed.
  

• Fix a regression with npm install --no-optional (#2720)

  Normally when you install esbuild with npm install, npm itself is the tool that downloads the correct binary executable for the current platform. This happens because of how esbuild's primary package uses npm's optionalDependencies feature. However, if you deliberately disable this with npm install --no-optional then esbuild's install script will attempt to repair the installation by manually downloading and extracting the binary executable from the package that was supposed to be installed.

  The change in version 0.16.0 to move esbuild's nested packages into the @esbuild/ scope unintentionally broke this logic because of how npm's URL structure is different for scoped packages vs. normal packages. It was actually already broken for a few platforms earlier because esbuild already had packages for some platforms in the @esbuild/ scope, but I didn't discover this then because esbuild's integration tests aren't run on all platforms. Anyway, this release contains some changes to the install script that should hopefully get this scenario working again.

0.16.1

This is a hotfix for the previous release.

• Re-allow importing JSON with the copy loader using an import assertion

  The previous release made it so when assert { type: 'json' } is present on an import statement, esbuild validated that the json loader was used. This is what an import assertion is supposed to do. However, I forgot about the relatively new copy loader, which sort of behaves as if the import path was marked as external (and thus not loaded at all) except that the file is copied to the output directory and the import path is rewritten to point to the copy. In this case whatever JavaScript runtime ends up running the code is the one to evaluate the import assertion. So esbuild should really allow this case as well. With this release, esbuild now allows both the json and copy loaders when an assert { type: 'json' } import assertion is present.

0.16.0

... (truncated)

• 8ef19fe publish 0.16.3 to npm
• 8648239 fix #2727: avoid sync.WaitGroup to fix hang
• 2ec1f5b add a timeout for yarn pnp tests
• 0829d74 publish 0.16.2 to npm
• 7b45a3b fix #2718: transform keeps process.env.NODE_ENV
• a4d7d97 fix #2723: skip import.meta warnings in packages
• c189b30 fix #2722: write ^0.15.0 in the release notes
• 9493e3b fix #2719: avoid define creating syntax errors
• a2a2dd0 fix #2720: adapt npm i --no-optional to scopes
• 1ae3ca6 fix #917: document my basic development workflow
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from eslint's releases.

v8.29.0

Features

• 49a07c5 feat: add allowParensAfterCommentPattern option to no-extra-parens (#16561) (Nitin Kumar)
• e6a865d feat: prefer-named-capture-group add suggestions (#16544) (Josh Goldberg)
• a91332b feat: In no-invalid-regexp validate flags also for non-literal patterns (#16583) (trosos)

Documentation

• 0311d81 docs: Configuring Plugins page intro, page tweaks, and rename (#16534) (Ben Perlmutter)
• 57089b1 docs: add a property assignment example for camelcase rule (#16605) (Milos Djermanovic)
• b6ab030 docs: add docs codeowners (#16601) (Strek)
• 6380c87 docs: fix sitemap and feed (#16592) (Milos Djermanovic)
• ade621d docs: perf debounce the search query (#16586) (Shanmughapriyan S)
• fbcf3ab docs: fix searchbar clear button (#16585) (Shanmughapriyan S)
• f894035 docs: HTTPS link to yeoman.io (#16582) (Christian Oliff)
• de12b26 docs: Update configuration file pages (#16509) (Ben Perlmutter)
• 1ae9f20 docs: update correct code examples for no-extra-parens rule (#16560) (Nitin Kumar)

Chores

• 7628403 chore: add discord channel link (#16590) (Amaresh S M)
• f5808cb chore: fix rule doc headers check (#16564) (Milos Djermanovic)

v8.28.0

Features

• 63bce44 feat: add ignoreClassFieldInitialValues option to no-magic-numbers (#16539) (Milos Djermanovic)
• 8385ecd feat: multiline properties in rule key-spacing with option align (#16532) (Francesco Trotta)
• a4e89db feat: no-obj-calls support Intl (#16543) (Sosuke Suzuki)

Bug Fixes

• c50ae4f fix: Ensure that dot files are found with globs. (#16550) (Nicholas C. Zakas)
• 9432b67 fix: throw error for first unmatched pattern (#16533) (Milos Djermanovic)
• e76c382 fix: allow * 1 when followed by / in no-implicit-coercion (#16522) (Milos Djermanovic)

Documentation

• 34c05a7 docs: Language Options page intro and tweaks (#16511) (Ben Perlmutter)
• 3e66387 docs: add intro and edit ignoring files page (#16510) (Ben Perlmutter)
• 436f712 docs: fix Header UI inconsistency (#16464) (Tanuj Kanti)
• f743816 docs: switch to wrench emoji for auto-fixable rules (#16545) (Bryan Mishkin)
• bc0547e docs: improve styles for versions and languages page (#16553) (Nitin Kumar)
• 6070f58 docs: clarify esquery issue workaround (#16556) (Milos Djermanovic)
• b48e4f8 docs: Command Line Interface intro and tweaks (#16535) (Ben Perlmutter)
• b92b30f docs: Add Rules page intro and content tweaks (#16523) (Ben Perlmutter)
• 1769b42 docs: Integrations page introduction (#16548) (Ben Perlmutter)
• a8d0a57 docs: make table of contents sticky on desktop (#16506) (Sam Chen)
• a01315a docs: fix route of japanese translation site (#16542) (Tanuj Kanti)
• 0515628 docs: use emoji instead of svg for deprecated rule (#16536) (Bryan Mishkin)
• 68f1288 docs: set default layouts (#16484) (Percy Ma)
• 776827a docs: init config about specifying shared configs (#16483) (Percy Ma)
• 5c39425 docs: fix broken link to plugins (#16520) (Ádám T. Nagy)
• c97c789 docs: Add missing no-new-native-nonconstructor docs code fence (#16503) (Brandon Mills)

... (truncated)

Sourced from eslint's changelog.

v8.29.0 - December 2, 2022

• 0311d81 docs: Configuring Plugins page intro, page tweaks, and rename (#16534) (Ben Perlmutter)
• 57089b1 docs: add a property assignment example for camelcase rule (#16605) (Milos Djermanovic)
• b6ab030 docs: add docs codeowners (#16601) (Strek)
• 7628403 chore: add discord channel link (#16590) (Amaresh S M)
• 49a07c5 feat: add allowParensAfterCommentPattern option to no-extra-parens (#16561) (Nitin Kumar)
• 6380c87 docs: fix sitemap and feed (#16592) (Milos Djermanovic)
• e6a865d feat: prefer-named-capture-group add suggestions (#16544) (Josh Goldberg)
• ade621d docs: perf debounce the search query (#16586) (Shanmughapriyan S)
• a91332b feat: In no-invalid-regexp validate flags also for non-literal patterns (#16583) (trosos)
• fbcf3ab docs: fix searchbar clear button (#16585) (Shanmughapriyan S)
• f894035 docs: HTTPS link to yeoman.io (#16582) (Christian Oliff)
• de12b26 docs: Update configuration file pages (#16509) (Ben Perlmutter)
• f5808cb chore: fix rule doc headers check (#16564) (Milos Djermanovic)
• 1ae9f20 docs: update correct code examples for no-extra-parens rule (#16560) (Nitin Kumar)

v8.28.0 - November 18, 2022

• 34c05a7 docs: Language Options page intro and tweaks (#16511) (Ben Perlmutter)
• 3e66387 docs: add intro and edit ignoring files page (#16510) (Ben Perlmutter)
• 436f712 docs: fix Header UI inconsistency (#16464) (Tanuj Kanti)
• f743816 docs: switch to wrench emoji for auto-fixable rules (#16545) (Bryan Mishkin)
• bc0547e docs: improve styles for versions and languages page (#16553) (Nitin Kumar)
• 6070f58 docs: clarify esquery issue workaround (#16556) (Milos Djermanovic)
• b48e4f8 docs: Command Line Interface intro and tweaks (#16535) (Ben Perlmutter)
• b92b30f docs: Add Rules page intro and content tweaks (#16523) (Ben Perlmutter)
• 1769b42 docs: Integrations page introduction (#16548) (Ben Perlmutter)
• 63bce44 feat: add ignoreClassFieldInitialValues option to no-magic-numbers (#16539) (Milos Djermanovic)
• c50ae4f fix: Ensure that dot files are found with globs. (#16550) (Nicholas C. Zakas)
• a8d0a57 docs: make table of contents sticky on desktop (#16506) (Sam Chen)
• 9432b67 fix: throw error for first unmatched pattern (#16533) (Milos Djermanovic)
• 8385ecd feat: multiline properties in rule key-spacing with option align (#16532) (Francesco Trotta)
• a4e89db feat: no-obj-calls support Intl (#16543) (Sosuke Suzuki)
• a01315a docs: fix route of japanese translation site (#16542) (Tanuj Kanti)
• e94a4a9 chore: Add tests to verify #16038 is fixed (#16538) (Nicholas C. Zakas)
• 0515628 docs: use emoji instead of svg for deprecated rule (#16536) (Bryan Mishkin)
• e76c382 fix: allow * 1 when followed by / in no-implicit-coercion (#16522) (Milos Djermanovic)
• 68f1288 docs: set default layouts (#16484) (Percy Ma)
• e13f194 chore: stricter validation of meta.docs.description in core rules (#16529) (Milos Djermanovic)
• 776827a docs: init config about specifying shared configs (#16483) (Percy Ma)
• 72dbfbc chore: use pkg parameter in getNpmPackageVersion (#16525) (webxmsj)
• 5c39425 docs: fix broken link to plugins (#16520) (Ádám T. Nagy)
• c97c789 docs: Add missing no-new-native-nonconstructor docs code fence (#16503) (Brandon Mills)

v8.27.0 - November 6, 2022

• f14587c feat: new no-new-native-nonconstructor rule (#16368) (Sosuke Suzuki)
• 978799b feat: add new rule no-empty-static-block (#16325) (Sosuke Suzuki)
• ce93b42 docs: Stylelint property-no-unknown (#16497) (Nick Schonning)

... (truncated)

• d3e4b59 8.29.0
• 6a5f667 Build: changelog update for 8.29.0
• 0311d81 docs: Configuring Plugins page intro, page tweaks, and rename (#16534)
• 57089b1 docs: add a property assignment example for camelcase rule (#16605)
• b6ab030 docs: add docs codeowners (#16601)
• 7628403 chore: add discord channel link (#16590)
• 49a07c5 feat: add allowParensAfterCommentPattern option to no-extra-parens (#16561)
• 6380c87 docs: fix sitemap and feed (#16592)
• e6a865d feat: prefer-named-capture-group add suggestions (#16544)
• ade621d docs: perf debounce the search query (#16586)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​open-wc/testing's releases.

@​open-wc/testing@​3.1.7

Patch Changes

• b187c0bc: Add types export for node16 module resolution
• Updated dependencies [b187c0bc]
  • @​open-wc/testing-helpers@​2.1.4

Sourced from @​open-wc/testing's changelog.

3.1.7

Patch Changes

• b187c0bc: Add types export for node16 module resolution
• Updated dependencies [b187c0bc]
  • @​open-wc/testing-helpers@​2.1.4

• 0182490 Version Packages (#2508)
• b187c0b Add types export to testing & testing-helpers (#2507)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​web/test-runner's releases.

@​web/test-runner@​0.15.0

Minor Changes

• acca5d51: Update dependency v8-to-istanbul to v9

Patch Changes

• Updated dependencies [acca5d51]
  • @​web/test-runner-chrome@​0.11.0

@​web/test-runner@​0.14.1

Patch Changes

• 04e2fa7d: Update portfinder dependency to 1.0.32
• Updated dependencies [04e2fa7d]
  • @​web/dev-server@​0.1.35

Sourced from @​web/test-runner's changelog.

0.15.0

Minor Changes

• acca5d51: Update dependency v8-to-istanbul to v9

Patch Changes

• Updated dependencies [acca5d51]
  • @​web/test-runner-chrome@​0.11.0

0.14.1

Patch Changes

• 04e2fa7d: Update portfinder dependency to 1.0.32
• Updated dependencies [04e2fa7d]
  • @​web/dev-server@​0.1.35

• ce38e9a Version Packages (#2064)
• e1b928a Version Packages (#2060)
• 04e2fa7 fix: update portfinder dependency to 1.0.32 (#2059)
• 9245c25 chore(deps): update dependency concurrently to v7 (#1861)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Sourced from @​vimeo/player's releases.

v2.18.0

Adds support for setting the current time of an embedded player through a ?vimeo_t_${CLIP_ID}=${TIME_IN_SECONDS} parameter that can be appended to the parent page URL.

• 2838bb8 v2.18.0
• e1beda4 Enable time query param in embed URL (#858)
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)