\r\n- \r\n
Drop support for older platforms (#3902)
\r\nThis release drops support for the following operating system:
\r\n\r\n- macOS 10.15 Catalina
\r\n
\r\nThis is because the Go programming language dropped support for this\r\noperating system version in Go 1.23, and this release updates esbuild\r\nfrom Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or\r\nlater.
\r\nNote that this only affects the binary esbuild executables that are\r\npublished to the esbuild npm package. It's still possible to compile\r\nesbuild's source code for these older operating systems. If you need to,\r\nyou can compile esbuild for yourself using an older version of the Go\r\ncompiler (before Go version 1.23). That might look something like\r\nthis:
\r\ngit clone https://github.com/evanw/esbuild.git\r\ncd esbuild\r\ngo build ./cmd/esbuild\r\n./esbuild --version\r\n
\r\n \r\n- \r\n
Fix class field decorators in TypeScript if\r\nuseDefineForClassFields is false (#3913)
\r\nSetting the useDefineForClassFields flag to\r\nfalse in tsconfig.json means class fields use\r\nthe legacy TypeScript behavior instead of the standard JavaScript\r\nbehavior. Specifically they use assign semantics instead of define\r\nsemantics (e.g. setters are triggered) and fields without an initializer\r\nare not initialized at all. However, when this legacy behavior is\r\ncombined with standard JavaScript decorators, TypeScript switches to\r\nalways initializing all fields, even those without initializers.\r\nPreviously esbuild incorrectly continued to omit field initializers for\r\nthis edge case. These field initializers in this case should now be\r\nemitted starting with this release.
\r\n \r\n- \r\n
Avoid incorrect cycle warning with tsconfig.json\r\nmultiple inheritance (#3898)
\r\nTypeScript 5.0 introduced multiple inheritance for\r\ntsconfig.json files where extends can be an\r\narray of file paths. Previously esbuild would incorrectly treat files\r\nencountered more than once when processing separate subtrees of the\r\nmultiple inheritance hierarchy as an inheritance cycle. With this\r\nrelease, tsconfig.json files containing this edge case\r\nshould work correctly without generating a warning.
\r\n \r\n- \r\n
Handle Yarn Plug'n'Play stack overflow with\r\ntsconfig.json (#3915)
\r\nPreviously a tsconfig.json file that\r\nextends another file in a package with an\r\nexports map could cause a stack overflow when Yarn's\r\nPlug'n'Play resolution was active. This edge case should work now\r\nstarting with this release.
\r\n \r\n- \r\n
Work around more issues with Deno 1.31+ (#3917)
\r\nThis version of Deno broke the stdin and\r\nstdout properties on command objects for inherited streams,\r\nwhich matters when you run esbuild's Deno module as the entry point\r\n(i.e. when import.meta.main is true).\r\nPreviously esbuild would crash in Deno 1.31+ if you ran esbuild like\r\nthat. This should be fixed starting with this release.
\r\nThis fix was contributed by @Joshix-1.
\r\n \r\n
\r\n