Build(deps): bump esbuild from 0.23.0 to 0.24.0

Bumps esbuild from 0.23.0 to 0.24.0.

Release notes

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.
Drop support for older platforms (#3902)

This release drops support for the following operating system:

macOS 10.15 Catalina

This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.
v0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)

import fs from "fs";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.
Drop support for older platforms (#3902)

This release drops support for the following operating system:

macOS 10.15 Catalina

This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.
0.23.1
Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open

... (truncated)

Commits

d34e79e publish 0.24.0 to npm
045a87f fix #3887: omit dead export warning for default
6e049b8 fix #3913: useDefineForClassFields and decorators
9c26f98 lower decorators for useDefineForClassFields #3913
46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
b500443 fix #3917: running esbuild cli with deno
b125e62 run make update-compat-table
112b9aa fix #3915: stack overflow with yarn + tsconfig
ed5a555 wasm: catch and rethrow stack overflows (#3915)
11d3196 fix #3902: update go 1.22.5 => 1.23.1
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

Package	New capabilities	Transitives	Size	Publisher
npm/@esbuild/aix-ppc64@0.24.0	None	`0`	11.2 MB	evanw
npm/@esbuild/android-arm@0.24.0	None	`0`	11.9 MB	evanw
npm/@esbuild/android-arm64@0.24.0	None	`0`	10.6 MB	evanw
npm/@esbuild/android-x64@0.24.0	None	`0`	11.9 MB	esbuild, evanw
npm/@esbuild/darwin-arm64@0.24.0	None	`0`	9.75 MB	evanw
npm/@esbuild/darwin-x64@0.24.0	None	`0`	10.4 MB	evanw
npm/@esbuild/freebsd-arm64@0.24.0	None	`0`	9.5 MB	evanw
npm/@esbuild/freebsd-x64@0.24.0	None	`0`	10.2 MB	evanw
npm/@esbuild/linux-arm@0.24.0	None	`0`	9.63 MB	evanw
npm/@esbuild/linux-arm64@0.24.0	None	`0`	9.57 MB	evanw
npm/@esbuild/linux-ia32@0.24.0	None	`0`	9.59 MB	evanw
npm/@esbuild/linux-loong64@0.24.0	None	`0`	9.77 MB	evanw
npm/@esbuild/linux-mips64el@0.24.0	None	`0`	10.9 MB	evanw
npm/@esbuild/linux-ppc64@0.24.0	None	`0`	9.83 MB	evanw
npm/@esbuild/linux-riscv64@0.24.0	None	`0`	9.44 MB	evanw
npm/@esbuild/linux-s390x@0.24.0	None	`0`	10.7 MB	evanw
npm/@esbuild/linux-x64@0.24.0	None	`0`	10.2 MB	evanw
npm/@esbuild/netbsd-x64@0.24.0	None	`0`	10.1 MB	evanw
npm/@esbuild/openbsd-arm64@0.24.0	None	`0`	9.57 MB	evanw
npm/@esbuild/openbsd-x64@0.24.0	None	`0`	10.2 MB	evanw
npm/@esbuild/sunos-x64@0.24.0	None	`0`	10.2 MB	evanw
npm/@esbuild/win32-arm64@0.24.0	None	`0`	9.57 MB	evanw
npm/@esbuild/win32-ia32@0.24.0	None	`0`	9.85 MB	evanw
npm/@esbuild/win32-x64@0.24.0	None	`0`	10.4 MB	evanw
npm/esbuild@0.24.0	environment, filesystem, network, shell	`0`	134 kB	esbuild, evanw

i18next / i18next-parser

Build(deps): bump esbuild from 0.23.0 to 0.24.0 #1072

v0.24.0

v0.23.1

0.24.0

0.23.1