Dynamic import with top-level await about graaljs HOT 3 CLOSED

Thank you for reaching out about this, could you please share a complete code example to illustrate the issue?

from graaljs.

This seems to be a misunderstanding of Polyglot API. What do you expect to happen when you invoke entrypoint.execute()? Note that context.eval(source); executes your script already (and prints nothing like vanilla Node.js). It returns the value of the executed script. It would be the value of the last statement in non-async code, for example 42 in the following case:

if (false) {
  console.log('SKIPPED');
}
console.log('EXECUTED');
42;

and it is the promise that represents your asynchronous code in your case (because you used await - which basically turned your script into an async function). So, entrypoint.execute() attempts to execute the promise as function. This fails because promises are not executable/callable/functions.

In other words, your test-case is equivalent to

var fun = async function() { /* your code */ };  var entryPoint = fun(); entryPoint();

You can verify that this code fails with TypeError: entryPoint is not a function in both Node.js and graal-js.

from graaljs.

@iamstolis I see your point, thank you for clarifying this.

from graaljs.