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
No errors are thrown on asyncawait check. #3455
Comments
Thanks for letting us know. The lines you pointed to belong to our Node6 infrastructure. They will be removed once we drop Node6 support, and thus the necessity of unsafe-eval will go away as well. As another workaround, you can build a custom version for |
Hey guys, im having this error.. npm run bundle npm ERR! A complete log of this run can be found in: |
I have same issue. It seems that puppteer is not so popular in chrome extension. too less resources. |
Same issue:
|
puppeteer has updated their ways of running and there are better alternatives. Just running the script won't get you far. Let me find another way and update my old answers. :D |
Thanks for your comment! I was talking regarding the
Previously setting a server like this:
But did not succeed due to this error:
I realize now that the answer where I got this code from in SO is also yours lol. I'll be thankful in case you have any comment to make this work :) |
Origin of problem:
puppeteer-web
on chrome extension.Source: https://github.com/GoogleChrome/puppeteer/blob/master/index.js#L21
Relevent Stackoverflow Question: https://stackoverflow.com/q/53001009/6161265
The bundled version shows anonymous function, figuring out the problem wasn't smooth.
Possible solutions:
unsafe-eval
on content_security_policy of theirmanifest.json
file.The text was updated successfully, but these errors were encountered: