[Snyk] Upgrade esbuild from 0.19.5 to 0.20.0 #1

B020239 · 2024-03-09T15:23:04Z

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade esbuild from 0.19.5 to 0.20.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 8 versions ahead of your current version.
The recommended version was released a month ago, on 2024-01-27.

Release notes

Package name: esbuild

0.20.0 - 2024-01-27
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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
- Work around API deprecations in Deno 1.40.x (#3609, #3611)
  
  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
  
  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.
- Reorder implicit file extensions within node_modules (#3341, #3608)
  
  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.
  
  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.
  
  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.
0.19.12 - 2024-01-23
- The "preserve" JSX mode now preserves JSX text verbatim (#3605)
 
 The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
 
 Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
 
 // Original code
 let el =
 <a href={'/'} title=''"'> some text
 {foo}
 more text </a>
 
 // Old output (with --loader=jsx --jsx=preserve)
 let el = <a href="/" title={'"}>
 {" some text"}
 {foo}
 {"more text "}
 </a>;
 
 // New output (with --loader=jsx --jsx=preserve)
 let el = <a href={"/"} title=''"'> some text
 {foo}
 more text </a>;
- Allow JSX elements as JSX attribute values
 
 JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:
```
let el = <div data-ab=<><a/></>/>;
```
 I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.
 
 Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.
- Fix a bug with TypeScript type parsing (#3574)
 
 This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:
```
type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never
```
0.19.11 - 2023-12-29
- Fix TypeScript-specific class transform edge case (#3559)
 
 The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:
 
 // Original code
 class Foo extends Bar {
 #private = 1;
 public: any;
 constructor() {
 super();
 }
 }
 
 // Old output (with esbuild v0.19.9)
 class Foo extends Bar {
 constructor() {
 super();
 this.#private = 1;
 }
 #private;
 }
 
 // Old output (with esbuild v0.19.10)
 class Foo extends Bar {
 constructor() {
 this.#private = 1;
 super();
 }
 #private;
 }
 
 // New output
 class Foo extends Bar {
 #private = 1;
 constructor() {
 super();
 }
 }
- Minifier: allow reording a primitive past a side-effect (#3568)
 
 The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:
 
 // Original code
 function f() {
 let x = false;
 let y = x;
 const boolean = y;
 let frag = $.template(${boolean}">hello world);
 return frag;
 }
 
 // Old output (with --minify)
 function f(){const e=!1;return $.template(${e}">hello world)}
 
 // New output (with --minify)
 function f(){return $.template('hello world')}
- Minifier: consider properties named using known Symbol instances to be side-effect free (#3561)
 
 Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as Symbol.iterator as a computed property name is not obviously side-effect free. This release adds a special case for known Symbol instances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:
```
class Foo {
 *[Symbol.iterator]() {
 }
}
```
- Provide the stop() API in node to exit esbuild's child process (#3558)
 
 You can now call stop() in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.
0.19.10 - 2023-12-19
Read more
0.19.9 - 2023-12-10
Read more
0.19.8 - 2023-11-26
Read more
0.19.7 - 2023-11-21
Read more
0.19.6 - 2023-11-19
Read more
0.19.5 - 2023-10-17
Read more