Realm running module code to cover import

[leobalter]

does having import implies Realm code is module code?

[littledan]

I don't think so, since inside that module, you can use eval, which doesn't run module code.

[mhofman]

Currently the proposal does require that the "bootstrap" is either module code, or using realm.eval(), with the latter subject to string evaluation and CSP complications in browsers. Maybe there could be an executeScript(specifier): Promise<void>, which compatible hosts (e.g. browsers) could implement by interpreting the specifier as a path? The call would be async, and resolve to undefined, or reject.

~Update: I guess the inability to return a value would require the usage of eval or module bindings anyway, so I guess there isn't much benefit to an "executeScript".~

[mhofman]

Actually maybe there could be something like getGlobalPropertyValue(name): PrimitiveValueOrCallable? Combined with an executeScript, that should allow executing non module code without the need of eval, while avoiding exposing the realm's globalThis directly.

Edit: for completeness, here is an example:

// my-script.js
globalThis.timesTwo = (x) => x * 2;

// main.js
const r = new Realm();
await r.executeScript('./my-script.js');

const redFunction = r.getGlobalPropertyValue('timesTwo');
redFunction(21); // yields 42