Modules being emitted in strict mode breaks global.ts

[kitsonk]

As of TypeScript 1.8, all modules are emitted with the "use strict"; prologue (see: microsoft/TypeScript#5765). This causes global.ts to return undefined at runtime, versus the global scope.

[kitsonk]

@jason0x43 mentioned the following should work in strict mode:

const global = (1,eval)('this');

[kitsonk]

Actually, I settled on const global = Function('return this')(); as it seems more clear what the intent is.

[kfranqueiro]

I was thinking something along those lines too; is there a reason to prefer that over (function () { return this; }());?

[jason0x43]

this is undefined for regular function calls in strict mode.

[kfranqueiro]

Oh, derp, that is what we were doing (I had thought we were doing something more specific). Nevermind. Though I wouldn't have expected new Function to behave differently then.

[kitsonk]

Yeah, I didn't either, but @DanielRosenwasser pointed me to a StackOverflow and it passes the tests.

[jason0x43]

Functions created with the Function constructor don't inherit strictness, so this points to the global object as it would in non-strict mode.