-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid eval #1403
Comments
If you can find a workaround for our use of https://github.com/caolan/async/blob/master/lib/internal/wrapAsync.js#L6-L15 |
@aearly why not to change: function isAsync(fn) {
return supportsSymbol && fn[Symbol.toStringTag] === 'AsyncFunction';
} to function isAsync(fn) {
return fn.constructor.name === 'AsyncFunction';
} |
megawac
added a commit
that referenced
this issue
Apr 17, 2017
Avoid eval in async wrappers; fixes #1403
Released in v2.4.0! |
Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
I would like to ask if you can avoid using eval. I am getting this error from Firefox browser console:
Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src moz-extension://...”). Source: call to eval() or related function blocked by CSP.
async.js:206
The text was updated successfully, but these errors were encountered: