Executing JavaScript IIFE causes PolyglotException: ReferenceError about graaljs HOT 7 CLOSED

Do you know date of next release that should have a fix?

There is no fix yet. So, there is no date of a release with a fix yet ;-).

And if I use org.graalvm.polyglot.Context instead GraalJSScriptEngine will I also have issue?

The mentioned context variable refers to ScriptContext used by the ScriptEngine. There is no ScriptContext/ScriptEngine when you use org.graalvm.polyglot.Context. So, there cannot be this context global variable.

I wonder if you really need/use this context variable and why. If you really need it then you can provide it on your own as a workaround (i.e. you can set the variable/binding yourself explicitly).

from graaljs.

neither in Nashorn and it didn't fail there.

ReferenceError is expected in this case and I see the same behavior in Nashorn. Namely, when I execute the following code

System.out.println(System.getProperty("java.version"));
ScriptEngineManager manager = new ScriptEngineManager();
ScriptEngine engine = manager.getEngineByName("nashorn");
System.out.println(engine);
CompiledScript script = ((Compilable) engine).compile("(function __f(arg) { return null; })(arg);");
script.eval();

I get

11.0.12
Warning: Nashorn engine is planned to be removed from a future JDK release
jdk.nashorn.api.scripting.NashornScriptEngine@52aa2946
Exception in thread "main" javax.script.ScriptException: ReferenceError: "arg" is not defined in <eval> at line number 1
	at jdk.scripting.nashorn/jdk.nashorn.api.scripting.NashornScriptEngine.throwAsScriptException(NashornScriptEngine.java:477)
	at jdk.scripting.nashorn/jdk.nashorn.api.scripting.NashornScriptEngine.evalImpl(NashornScriptEngine.java:461)
	at jdk.scripting.nashorn/jdk.nashorn.api.scripting.NashornScriptEngine$3.eval(NashornScriptEngine.java:517)
	at java.scripting/javax.script.CompiledScript.eval(CompiledScript.java:103)

from graaljs.

oops.
@iamstolis
Can you replace in your code 'arg' with "context" and repeat?

from graaljs.

Can you replace in your code 'arg' with "context" and repeat?

Yes, the usage of context throws in graaljs but does not throw in nashorn. Nashorn seems to provide a global context variable that points to the ScriptContext in use. We can provide the same variable in GraalJSScriptEngine in nashorn-compat mode.

from graaljs.

Do you know date of next release that should have a fix?

And if I use org.graalvm.polyglot.Context instead GraalJSScriptEngine will I also have issue?

from graaljs.

Thanks, for now will do the workaround manually.

from graaljs.

context (and engine) global variables has been added by 27063eb (when ScriptEngine is used).

from graaljs.