chore(deps): update non-major #52

renovate · 2024-05-28T09:48:10Z

This PR contains the following updates:

Package	Change	Type	Update
esbuild	`^0.20.2` -> `^0.21.4`	devDependencies	minor
esbuild-plugin-solid	`^0.5.0` -> `^0.6.0`	devDependencies	minor
peter-evans/create-pull-request	`70a41ab` -> `6d6857d`	action	digest
prettier-plugin-packagejson	`^2.4.14` -> `^2.5.0`	devDependencies	minor
solid-js (source)	`^1.8.16` -> `^1.8.17`	devDependencies	patch
vite (source)	`^5.2.8` -> `^5.2.11`	devDependencies	patch
vitest (source)	`^1.4.0` -> `^1.6.0`	devDependencies	minor

Release Notes

evanw/esbuild (esbuild)

`v0.21.4`

Compare Source

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.

`v0.21.3`

Compare Source

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 {
  @&#8203;track foo = 1
  @&#8203;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 {
  @&#8203;(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.

`v0.21.2`

Compare Source

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 { @&#8203;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.

`v0.21.1`

Compare Source

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: /* @&#8203;__PURE__ */ __name(function() {
}, "y") };

// Output from this version (with --keep-names)
x = { get y() {
} };
```

`v0.21.0`

Compare Source

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 {
  @&#8203;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, _z, z_fn).call(this);
};

// New output (--supported:class-private-method=false)
var _Foo_instances, x_fn, y_fn, z_fn;
class Foo {
  constructor() {
    __privateAdd(this, _Foo_instances);
  }
}
_Foo_instances = new WeakSet();
x_fn = function() {
  return __privateMethod(this, _Foo_instances, x_fn).call(this);
};
y_fn = function() {
  return __privateMethod(this, _Foo_instances, y_fn).call(this);
};
z_fn = function() {
  return __privateMethod(this, _Foo_instances, z_fn).call(this);
};

Fix an obscure bug with lowering class members with computed property keys

When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():
```
class Foo {
  [a()]() {}
  [b()];
  static { c() }
}
```
Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:
```
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = b();
  }
  [a()]() {
  }
  static {
    c();
  }
}
```
However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:
```
// Original code
class Foo {
  [a()]() {}
  [await b()];
  static { c() }
}

// Old output (with --supported:class-field=false)
var _a;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  static {
    _a = await b();
  }
  [a()]() {
  }
  static {
    c();
  }
}

// New output (with --supported:class-field=false)
var _a, _b;
class Foo {
  constructor() {
    __publicField(this, _a);
  }
  [(_b = a(), _a = await b(), _b)]() {
  }
  static {
    c();
  }
}
```
Fix some --keep-names edge cases

The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:
```
var foo = function() {}
var bar = class {}
console.log(foo.name, bar.name)
```
When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:
```
var obj = { foo: function() {} }
class Foo0 { foo = function() {} }
class Foo1 { static foo = function() {} }
class Foo2 { accessor foo = function() {} }
class Foo3 { static accessor foo = function() {} }
foo ||= function() {}
foo &&= function() {}
foo ??= function() {}
```

amoutonbrady/esbuild-plugin-solid (esbuild-plugin-solid)

`v0.6.0`

Compare Source

Changed

🔧 Clean up dependencies and integrate `unbuild` to build the package [afe349a]
🚚 Convert test file to typescript [3322fba]
🚚 Rename source file to `index.ts` [4017708]

Removed

🔥 Remove build script to use `unbuild` instead [9333e8a]

Miscellaneous

🏷️ Fix tyeping issue [de2074f]

matzkoh/prettier-plugin-packagejson (prettier-plugin-packagejson)

`v2.5.0`

Compare Source

vitejs/vite (vite)

`v5.2.11`

Compare Source

feat: improve dynamic import variable failure error message (#16519) (f8feeea), closes #16519
fix: dynamic-import-vars plugin normalize path issue (#16518) (f71ba5b), closes #16518
fix: scripts and styles were missing from built HTML on Windows (#16421) (0e93f58), closes #16421
fix(deps): update all non-major dependencies (#16488) (2d50be2), closes #16488
fix(deps): update all non-major dependencies (#16549) (2d6a13b), closes #16549
fix(dev): watch publicDir explicitly to include it outside the root (#16502) (4d83eb5), closes #16502
fix(preload): skip preload for non-static urls (#16556) (bb79c9b), closes #16556
fix(ssr): handle class declaration and expression name scoping (#16569) (c071eb3), closes #16569
fix(ssr): handle function expression name scoping (#16563) (02db947), closes #16563

`v5.2.10`

Compare Source

revert: perf: use workspace root for fs cache (#15712) (#16476) (77e7359), closes #15712 #16476
fix: add base to virtual html (#16442) (721f94d), closes #16442
fix: adjust esm syntax judgment logic (#16436) (af72eab), closes #16436
fix: don't add outDirs to watch.ignored if emptyOutDir is false (#16453) (6a127d6), closes #16453
fix(cspNonce): don't overwrite existing nonce values (#16415) (b872635), closes #16415
feat: show warning if root is in build.outDir (#16454) (11444dc), closes #16454
feat: write cspNonce to style tags (#16419) (8e54bbd), closes #16419
chore(deps): update dependency eslint-plugin-n to v17 (#16381) (6cccef7), closes #16381

`v5.2.9`

Compare Source

fix: fsp.rm removing files does not take effect (#16032) (b05c405), closes #16032
fix: fix accumulated stacks in error overlay (#16393) (102c2fd), closes #16393
fix(deps): update all non-major dependencies (#16376) (58a2938), closes #16376
chore: update region comment (#16380) (77562c3), closes #16380
perf: reduce size of injected __vite__mapDeps code (#16184) (c0ec6be), closes #16184
perf(css): only replace empty chunk if imported (#16349) (e2658ad), closes #16349

vitest-dev/vitest (vitest)

View changes on GitHub

`v1.5.3`

Compare Source

🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5608 (48fba)
Backport jest iterable equality within object - by @sukovanej in https://github.com/vitest-dev/vitest/issues/5621 (30e5d)
browser: Support benchmark - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5622 (becab)
reporter: Use default error formatter for JUnit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5629 (20060)

View changes on GitHub

`v1.5.2`

Compare Source

🐞 Bug Fixes

Check for null before storing in weakmap - by @sheremet-va (ce368)

View changes on GitHub

`v1.5.1`

Compare Source

🚀 Features

api: startVitest() to accept stdout and stdin - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5493 (780b1)
- This is listed as a feature, but it doesn't increase the minor version because startVitest API is experimental and doesn't follow semver.

🐞 Bug Fixes

Close vite servers on all resolved projects - by @surc54 in https://github.com/vitest-dev/vitest/issues/5544 (413ec)
Fix default import.meta.env.PROD: false - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5561 (9c649)
Resolve cwd correctly when initiating projects - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5582 (ec9d7)
Always run onTestFinished in reverse order - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5598 (23f29)
browser:
- Disable fileParallelism by default on browser pool - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5528 (5c69f)
- Dispose tester iframe on done - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5595 (b2135)
coverage:
- Fix bundling of v8-to-istanbul - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5549 (df6a4)
- Prevent crash when cleanOnRerun is disabled - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5540 (ea3c1)
- thresholds to compare files relative to root - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5574 (80265)
expect:
- Fix toEqual and toMatchObject with circular references - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5535 (9e641)
vitest:
- Fix false positive file filter match with leading slash - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5578 (316eb)
- Watch the output directory correctly - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5584 (e40f9)
- StubEnv casts boolean on PROD/SSR/DEV - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5590 (4da88)

View changes on GitHub

`v1.5.0`

Compare Source

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

socket-security · 2024-05-28T09:48:32Z

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/esbuild-plugin-solid@0.6.0	Transitive: environment, filesystem, shell, unsafe	`+63`	10.5 MB	amoutonbrady
npm/esbuild@0.21.4	environment, filesystem, network, shell	`0`	133 kB	evanw

View full report↗︎

socket-security · 2024-05-28T09:48:35Z

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/esbuild-plugin-solid@0.6.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

stipsan · 2024-05-28T10:46:14Z

@SocketSecurity ignore npm/esbuild-plugin-solid@0.6.0

chore(deps): update non-major

587fd05

renovate bot added 📦 deps 🤖 bot labels May 28, 2024

stipsan enabled auto-merge May 28, 2024 10:46

stipsan approved these changes May 28, 2024

View reviewed changes

stipsan added this pull request to the merge queue May 28, 2024

Merged via the queue into main with commit c1474d1 May 28, 2024
7 checks passed

stipsan deleted the renovate/non-major branch May 28, 2024 10:47

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update non-major #52

chore(deps): update non-major #52

renovate bot commented May 28, 2024

socket-security bot commented May 28, 2024 •

edited

Loading

socket-security bot commented May 28, 2024 •

edited

Loading

stipsan commented May 28, 2024

chore(deps): update non-major #52

chore(deps): update non-major #52

Conversation

renovate bot commented May 28, 2024

Release Notes

Changed

Removed

Miscellaneous

🚀 Features

🐞 Bug Fixes

🏎 Performance

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

Configuration

socket-security bot commented May 28, 2024 • edited Loading

socket-security bot commented May 28, 2024 • edited Loading

Next steps

stipsan commented May 28, 2024

socket-security bot commented May 28, 2024 •

edited

Loading

socket-security bot commented May 28, 2024 •

edited

Loading