[Snyk] Upgrade esbuild from 0.18.13 to 0.21.5 #16

fishylunar · 2024-07-01T08:04:25Z

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

![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade esbuild from 0.18.13 to 0.21.5.

ℹ️ 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 29 versions ahead of your current version.
The recommended version was released on 21 days ago.

Release notes

Package name: esbuild

0.21.5 - 2024-06-09
- Fix Symbol.metadata on classes without a class decorator (#3781)
  
  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.
- Allow unknown import attributes to be used with the copy loader (#3792)
  
  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:
```
// This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }
```
  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).
  
  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):
```
// This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }
```
- Support import attributes with glob-style imports (#3797)
  
  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:
```
async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}
```
  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
  #3782)
  
  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:
```
{
  "compilerOptions": {
    "paths": {
      "js/*": ["${configDir}/dist/js/*"]
    }
  }
}
```
  You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.
- Fix internal error with --supported:object-accessors=false (#3794)
  
  This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.
0.21.4 - 2024-05-25
- Update support for import assertions and import attributes in node (#3778)
 
 Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:
 ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with] example.mjs:1:40: 1 │ import json from "esbuild/package.json" assert { type: "json" } │ ~~~~~~ ╵ with
 Did you mean to use "with" instead of "assert"?
 Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.
- Fix for await transform when a label is present
 
 This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:
 
 // Original code
 async function test() {
 outer: for await (const x of [Promise.resolve([0, 1])]) {
 for (const y of x) if (y) break outer
 throw 'fail'
 }
 }
 
 // Old output (with --target=es6)
 function test() {
 return __async(this, null, function* () {
 outer: try {
 for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
 const x = temp.value;
 for (const y of x) if (y) break outer;
 throw "fail";
 }
 } catch (temp) {
 error = [temp];
 } finally {
 try {
 more && (temp = iter.return) && (yield temp.call(iter));
 } finally {
 if (error)
 throw error[0];
 }
 }
 });
 }
 
 // New output (with --target=es6)
 function test() {
 return __async(this, null, function* () {
 try {
 outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
 const x = temp.value;
 for (const y of x) if (y) break outer;
 throw "fail";
 }
 } catch (temp) {
 error = [temp];
 } finally {
 try {
 more && (temp = iter.return) && (yield temp.call(iter));
 } finally {
 if (error)
 throw error[0];
 }
 }
 });
 }
- Do additional constant folding after cross-module enum inlining (#3416, #3425)
 
 This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.
 
 // Original code: enum.ts
 export enum Platform {
 WINDOWS = 'windows',
 MACOS = 'macos',
 LINUX = 'linux',
 }
 
 // Original code: main.ts
 import { Platform } from './enum';
 declare const PLATFORM: string;
 export function logPlatform() {
 if (PLATFORM == Platform.WINDOWS) console.log('Windows');
 else if (PLATFORM == Platform.MACOS) console.log('macOS');
 else if (PLATFORM == Platform.LINUX) console.log('Linux');
 else console.log('Other');
 }
 
 // Old output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
 function n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n as logPlatform};
 
 // New output (with --bundle '--define:PLATFORM="macos"' --minify --format=esm)
 function n(){console.log("macOS")}export{n as logPlatform};
- Pass import attributes to on-resolve plugins (#3384, #3639, #3646)
 
 With this release, on-resolve plugins will now have access to the import attributes on the import via the with property of the arguments object. This mirrors the with property of the arguments object that's already passed to on-load plugins. In addition, you can now pass with to the resolve() API call which will then forward that value on to all relevant plugins. Here's an example of a plugin that can now be written:
 
 const examplePlugin = {
 name: 'Example plugin',
 setup(build) {
 build.onResolve({ filter: /.*/ }, args => {
 if (args.with.type === 'external')
 return { external: true }
 })
 }
 }
 
 require('esbuild').build({
 stdin: {
 contents:  import foo from "./foo" with { type: "external" } foo()  ,
 },
 bundle: true,
 format: 'esm',
 write: false,
 plugins: [examplePlugin],
 }).then(result => {
 console.log(result.outputFiles[0].text)
 })
- Formatting support for the @ position-try rule (#3773)
 
 Chrome shipped this new CSS at-rule in version 125 as part of the CSS anchor positioning API. With this release, esbuild now knows to expect a declaration list inside of the @ position-try body block and will format it appropriately.
- Always allow internal string import and export aliases (#3343)
 
 Import and export names can be string literals in ES2022+. Previously esbuild forbid any usage of these aliases when the target was below ES2022. Starting with this release, esbuild will only forbid such usage when the alias would otherwise end up in output as a string literal. String literal aliases that are only used internally in the bundle and are "compiled away" are no longer errors. This makes it possible to use string literal aliases with esbuild's inject feature even when the target is earlier than ES2022.
0.21.3 - 2024-05-15
- Implement the decorator metadata proposal (#3760)
  
  This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:
  
  // Shim the "Symbol.metadata" symbol
  Symbol.metadata ??= Symbol('Symbol.metadata')
  
  const track = (_, context) => {
  (context.metadata.names ||= []).push(context.name)
  }
  
  class Foo {
  @track foo = 1
  @track bar = 2
  }
  
  // Prints ["foo", "bar"]
  console.log(Foo[Symbol.metadata].names)
  
  ⚠️ WARNING ⚠️
  
  This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
- Fix bundled decorators in derived classes (#3768)
  
  In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:
```
class Foo extends Object {
  @(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())
```
- Fix tsconfig.json files inside symlinked directories (#3767)
  
  This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.
0.21.2 - 2024-05-12
- Correct this in field and accessor decorators (#3761)
  
  This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:
```
const dec = () => function() { this.bar = true }
class Foo { @dec static foo }
console.log(Foo.bar) // Should be "true"
```
- Allow es2023 as a target environment (#3762)
  
  TypeScript recently added es2023 as a compilation target, so esbuild now supports this too. There is no difference between a target of es2022 and es2023 as far as esbuild is concerned since the 2023 edition of JavaScript doesn't introduce any new syntax features.
0.21.1 - 2024-05-07
- Fix a regression with --keep-names (#3756)
  
  The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:
  
  // Original code
  x = { get y() {} }
  
  // Output from version 0.21.0 (with --keep-names)
  x = { get y: /* @ PURE */ __name(function() {
  }, "y") };
  
  // Output from this version (with --keep-names)
  x = { get y() {
  } };
0.21.0 - 2024-05-07
This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.
- Implement the JavaScript decorators proposal (#104)
 
 With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:
 
 const log = (fn, context) => function() {
 console.log(before ${context.name})
 const it = fn.apply(this, arguments)
 console.log(after ${context.name})
 return it
 }
 
 class Foo {
 @log static foo() {
 console.log('in foo')
 }
 }
 
 // Logs "before foo", "in foo", "after foo"
 Foo.foo()
 
 Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.
 
 Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.
 
 ⚠️ WARNING ⚠️
 
 This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.
- Optimize the generated code for private methods
 
 Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:
```
let it
class Bar {
 constructor() {
 it = this
 }
}
class Foo extends Bar {
 #x = 1
 #y = null.foo
 static check() {
 console.log(#x in it, #y in it)
 }
}
try { new Foo } catch {}
Foo.check()
```
 This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:
 
 // Original code
 class Foo {
 #x() { return this.#x() }
 #y() { return this.#y() }
 #z() { return this.#z() }
 }
 
 // Old output (--supported:class-private-method=false)
 var _x, x_fn, _y, y_fn, _z, z_fn;
 class Foo {
 constructor() {
 __privateAdd(this, _x);
 __privateAdd(this, _y);
 __privateAdd(this, _z);
 }
 }
 _x = new WeakSet();
 x_fn = function() {
 return __privateMethod(this, _x, x_fn).call(this);
 };
 _y = new WeakSet();
 y_fn = function() {
 return __privateMethod(this, _y, y_fn).call(this);
 };
 _z = new WeakSet();
 z_fn = function() {
 return __privateMethod(this, <...