Puppeteer adapter: "Evaluation failed: TypeError: Failed to fetch"
See original GitHub issueI’m attempting to use Polly in an existing project to test a webform, however upon adding Polly with the Puppeteer adapter I’m running into this error from Puppeteer.
Evaluation failed: TypeError: Failed to fetch
This error isn’t present without Polly and the Puppeteer adapter.
I can provide more details upon request, but I’m unsure on what I need to share to diagnose this issue right now.
Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:12
Top Results From Across the Web
Puppeteer is failing to upload a file with TypeError
@blex Just tried this, but I'm still getting the Evaluation failed: TypeError: Failed to fetch error. – Sup3r D. Mar 22, 2020 at...
Read more >@pollyjs/adapter-puppeteer - npm
Record, Replay, and Stub HTTP Interactions ... The @pollyjs/adapter-puppeteer package provides a Puppeteer adapter to be used with @pollyjs/core .
Read more >failed to fetch dynamically imported module - You.com | The AI ...
Describe the bug. I am encountering some issues when deploying my project to vercel using the vercel-adapter. The project builds but then the...
Read more >consistent bad gateway using npm artifacts
When trying to restore the following package from my azure artifact, it fails with bad gateway. https://www.npmjs.com/package/jsnlog.
Read more >The Tidelift catalog of open source packages
Fetch all the members of all the specified github organizations with their complete details ... Custom error messages in JSON-Schema for Ajv validator....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
FYI this happens because of CSP errors and can be resolved with:
An easy way to reproduce it is to just open the console on github.com (this page works fine) and enter:
This shows in the console as:
It’s triggered by the following header:
I’ll look into setting up a fail test, but regardless is probably a good idea to just recommend that the user turn this on in the documentation or even in the error message for
fetch
failing. I’m not seeing an easier way to work around it (unless you want to turn it on for them).Thoughts?