Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SES - Function constructor this-value

See original GitHub issue

is it possible to safely preserve this strict-mode behavior in SES? its a common pre-globalThis pattern as long as the globalThis is the compartment globalThis, it seems fine 🤔

new Function('return this')() === globalThis

Issue Analytics

State:
Created 3 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

kumaviscommented, Mar 16, 2021

thanks 🚀

1reaction

erightscommented, Mar 16, 2021

Yes. Caller insensitivity. Like any other function, the meaning of both Function and indirect eval are not sensitive to the strictness of their caller. That would be dynamic scoping, which is one horror that I have totally succeeded at keeping out of JS!

For both Function and indirect eval, they evaluate their code sloppy unless that code begins with a "use strict"; directive. However, SES banishes sloppy mode completely, but still with no caller sensitivity. The SES Fucntion and indirect eval evaluate their code only strict, as if always preceded by a "use strict"; directive.