Bump org.graalvm.js:js-scriptengine from 21.1.0 to 24.1.0

[dependabot]

Bumps org.graalvm.js:js-scriptengine from 21.1.0 to 24.1.0.

Release notes

Sourced from org.graalvm.js:js-scriptengine's releases.

GraalJS 24.1.0

GraalJS is an ECMAScript-compliant runtime to execute JavaScript and Node.js applications. It is fully standard compliant, execute applications with high performance, and provide all benefits from the GraalVM stack, including language interoperability and common tooling.

GraalJS version 24.1.0 is designed for use with Oracle GraalVM for JDK 23.0.0 or GraalVM Community Edition for JDK 23.0.0, and can be downloaded separately.

There are two standalone types to choose from:

• Native Standalone: This contains a Native Image compiled launcher
• JVM Standalone: This contains JavaScript in the JVM configuration

To distinguish between them, the GraalVM Community Edition version has the suffix -community in the name. A JVM standalone has a -jvm suffix in a name.

Learn more about GraalJS and how to get started on the website: https://www.graalvm.org/javascript/.

GraalJS 24.0.2

GraalJS is an ECMAScript-compliant runtime to execute JavaScript and Node.js applications. It is fully standard compliant, execute applications with high performance, and provide all benefits from the GraalVM stack, including language interoperability and common tooling.

GraalJS version 24.0.2 is designed for use with Oracle GraalVM for JDK 22.0.2 or GraalVM Community Edition for JDK 22.0.2, and can be downloaded separately.

There are two standalone types to choose from:

• Native Standalone: This contains a Native Image compiled launcher
• JVM Standalone: This contains JavaScript in the JVM configuration

To distinguish between them, the GraalVM Community Edition version has the suffix -community in the name. A JVM standalone has a -jvm suffix in a name.

Learn more about GraalJS and how to get started on the website: https://www.graalvm.org/javascript/.

GraalJS 24.0.1

GraalJS is an ECMAScript-compliant runtime to execute JavaScript and Node.js applications. It is fully standard compliant, execute applications with high performance, and provide all benefits from the GraalVM stack, including language interoperability and common tooling.

GraalJS version 24.0.1 is designed for use with Oracle GraalVM for JDK 22.0.1 or GraalVM Community Edition for JDK 22.0.1, and can be downloaded separately.

There are two standalone types to choose from:

• Native Standalone: This contains a Native Image compiled launcher
• JVM Standalone: This contains JavaScript in the JVM configuration

To distinguish between them, the GraalVM Community Edition version has the suffix -community in the name. A JVM standalone has a -jvm suffix in a name.

Learn more about GraalJS and how to get started on the website: https://www.graalvm.org/javascript/.

GraalJS 24.0.0

GraalJS is an ECMAScript-compliant runtime to execute JavaScript and Node.js applications. It is fully standard compliant, execute applications with high performance, and provide all benefits from the GraalVM stack, including language interoperability and common tooling.

GraalJS version 24.0.0 is designed for use with Oracle GraalVM for JDK 22.0.0 or GraalVM Community Edition for JDK 22.0.0, and can be downloaded separately.

There are two standalone types to choose from:

• Native Standalone: This contains a Native Image compiled launcher

... (truncated)

Changelog

Sourced from org.graalvm.js:js-scriptengine's changelog.

Version 24.1.0

• ECMAScript 2024 mode/features enabled by default.
• Implemented the Make eval-introduced global vars redeclarable proposal.
• Implemented the Float16Array proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Implemented the Array.fromAsync proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Implemented the Resizable and Growable ArrayBuffers proposal.
• Updated Node.js to version 20.13.1.
• Made option js.esm-eval-returns-exports stable and allowed in SandboxPolicy.UNTRUSTED.

Version 24.0.0

• Implemented the WebAssembly threads proposal.
• Implemented the Promise.withResolvers proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Implementation of Async Iterator Helpers proposal (that was split out from Iterator Helpers proposal) was moved behind the experimental option --js.async-iterator-helpers.
• Implemented the Well-Formed Unicode Strings proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Implemented the JSON.parse source text access proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Updated Node.js to version 18.18.2.
• WebAssembly support in Node.js has been enabled by default. It can be disabled using the experimental option --js.webassembly=false.
• --js.import-assertions option has been replaced by --js.import-attributes option because the corresponding proposal has migrated from the usage of assertions to the usage of attributes.

Version 23.1.0

• NOTE: GraalVM no longer ships with a "js" ScriptEngine. Please either use the Maven dependency or explicitly put js-scriptengine.jar on the module path. See ScriptEngine documentation for details.
• ECMAScript 2023 mode/features enabled by default.
• Updated Node.js to version 18.17.1.
• Implemented the Async Context proposal. It is available behind the experimental option --js.async-context.
• FinalizationRegistry.prototype.cleanupSome is not enabled by default any more; it has been moved to ECMAScript staging mode (--js.ecmascript-version=staging).
• Added an experimental option --js.allow-narrow-spaces-in-date-format (enabled by default). When this option is set to false then narrow spaces in date/time formats are replaced by a space (0x20).
• Made option js.console stable and allowed in SandboxPolicy.UNTRUSTED.
• Made option js.unhandled-rejections stable and allowed in SandboxPolicy.CONSTRAINED.
• Added option js.allow-eval that is stable and allowed in SandboxPolicy.UNTRUSTED.
• Deprecated option js.disable-eval, superseded by js.allow-eval.
• Implemented the String.dedent proposal. It is available in ECMAScript staging mode (--js.ecmascript-version=staging).
• Duplicate named capture groups are now supported in regular expressions, as per the duplicate named capturing groups proposal.
• Implemented the RegExp v flag proposal. It is available behind the experimental option --js.regexp-unicode-sets.
• The Maven coordinates for embedding the GraalVM JavaScript have been updated. For consuming the enterprise GraalVM JavaScript, use:

  <dependency>
    <groupId>org.graalvm.polyglot</groupId>
    <artifactId>js</artifactId>
    <version>${graalvm.version}</version>
    <type>pom</type>
  </dependency>

  For consuming the community GraalVM JavaScript, use:

  <dependency>
    <groupId>org.graalvm.polyglot</groupId>
    <artifactId>js-community</artifactId>
    <version>${graalvm.version}</version>
    <type>pom</type>

... (truncated)

Commits

• 5ed929b [GR-54375] Release GraalVM 24.1.0.
• c7170b3 [GR-57059] Batch backport from master into 24.1 release branch.
• 3a569a8 Sync CI files.
• e118c7b Adding a note about js.stack-trace-api option into change-log.
• 5d26b52 Testing js.stack-trace-api option.
• fd4b7be Adding an option that enables/disables stack-trace-related extensions.
• 5041fbf Enabling Error.stackTraceLimit in MLE mode.
• fa68370 Adding a note about the limited usage of Error.prepareStackTrace/stackTraceLi...
• 8f85f0b Do not override the deprecated isCaptureFramesForTrace(Node).
• 3fbfef5 Tests using Error.prepareStackTrace/stackTraceLimit should use v8-compat mode.
• 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 <dependency name> 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)

---

This change is