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.
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.
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
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.
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).
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 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)
Bumps org.graalvm.polyglot:js-community from 23.1.2 to 24.0.2.
Release notes
Sourced from org.graalvm.polyglot:js-community's releases.
Changelog
Sourced from org.graalvm.polyglot:js-community's changelog.
... (truncated)
Commits
7c354bd
release GraalVM 24.0.200df63c
[GR-54762] Developer info is consistent with other suites.c45ace6
Developer info is consistent with other suites.d4afc25
[GR-54676] Backport to 24.0: Make the esm-eval-returns-exports option be stab...09eefba
[GR-54053] Backport to 24.0: Re-enable jdk-latest jobs on darwin-amd64 and mo...1d83c15
Make the esm-eval-returns-exports option be stable and usable in sandbox mode.d752a38
Allow newer macOS versions than BigSur, too.9f4b909
Remove workaround for missing <charconv> (GR-48310).f0372d6
Re-enable jdk-latest jobs on darwin-amd64 and move to macOS BigSur.7d4bf7c
[GR-53476] Backport to 24.0: Upgrading the underlying Node.js to version 18.2...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