Not compatible with strict CSP due to new Function(..)

[gretzkiy]

Hi,

This library relies on using new Function(...) to obtain references to the global object. However, this approach causes problems in environments with strict CSP settings that do not allow the unsafe-eval directive. Including unsafe-eval in the CSP is considered a security risk. Additionally, there are certain environments, such as browser extensions, where we are unable to relax the CSP.

Therefore, it is advisable to avoid using new Function(...) or eval(...) altogether, or to use them as a last resort only when no other means of referencing the global object is available.