Content Security Policy (CSP) issues with new Function(...)

[michael98123]

the usage of "new Function()" requires to increase the CSP to 'unsafe-eval'

code:

function tryConvertExpr(string) {
    // PENDING
    var exprRes = /^expr\((.*)\)$/.exec(string);
    if (exprRes) {
        try {
            var func = new Function('width', 'height', 'dpr', 'return ' + exprRes[1]);
            // Try run t
            func(1, 1);

            return func;
        }
        catch (e) {
            throw new Error('Invalid expression.');
        }
    }
}

Please replace the usage(s) of new Function with safer methods

[setvik]

Ditto. This is a security issue and blocker for us.

[setvik]

Update: the code is actually in a dependency of echarts-gl, claygl.

The insecure code is here:
https://github.com/pissang/claygl/blob/master/src/createCompositor.js#L294

Related issue in that repository is here:
pissang/claygl#133