How to access `global` from the module body

[caridy]

From what I can remember, Reflect.global was suppose to provide a way to access the global now that this is undefined in modules, but it is not in the spec for what I can tell. Using new Function() is not an option if you're using CSP, the only option at this point is to cross your fingers and do: typeof global !== 'undefined' ? global : window;.

/cc @ericf

[ericf]

Related would be to access the global from the [[Realm]] slot via the declarative syntax. Something like:

import {Realm} from this module;

And then access the global object from the Realm. I'll have to check through the notes because I forgot if this module was deferred or not.

Also we might want to move this to https://bugs.ecmascript.org…

[caridy]

@ericf ... from this module; is up in the air, definitely not in ES6.

[matthewp]

Also need a way to access the Loader that is loading your module.

[ericf]

@caridy I wasn't suggesting this would be in ES6 since ES6 is locked; just pointing out the most recent syntax for ES7/2016 that was discussed in TC39 (likely in the notes somewhere).

[dherman]

I'm not sure we want to expose the realm or the global via the module system. I suspect MarkM will have security concerns around it. I think it's likely better to do this through Reflect. Let's discuss with Mark at the next TC39 meeting.

[caridy]

update: we need to reach out to @erights to settle this.

[caridy]

Update:

• I can't be on Reflect.
• System.global: https://github.com/tc39/proposal-global proposal has reached stage 1, and might solve this.