Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot detect error for puppeteer problem
See original GitHub issueCurrently working with v3 (with webpack 3) and sometimes experienced error for the puppeteer renderer. The error was caught but not thrown. In such case, not all routes were rendered and webpack finished the process with 0 was returned.
May I know if this is the intended behaviour or what is expected to handle this kind of behaviour? Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
Puppeteer can't catch failing request & errors - Stack Overflow
The complete worked answer is: const puppeteer = require('puppeteer'); const run = async () => { const browser = await puppeteer.launch({ ...
Read more >Puppeteer doesn't capture some requests and JS errors #2617
Running the code will reproduce the problem. const puppeteer = require('puppeteer'); var run = async () => { const browser = await puppeteer....
Read more >Troubleshooting - Puppeteer
The most common cause is a bug in Node.js v14.0.0 which broke extract-zip , the module Puppeteer uses to extract browser downloads into...
Read more >Puppeteer Tutorial | Fixing Common Errors while installing ...
This tutorial troubleshoots common errors in Puppeteer. Using the commands and methods provided based on error scenarios, one can fix the ...
Read more >Puppeteer - npm
Puppeteer is a Node.js library which provides a high-level API to control Chrome/Chromium over the DevTools Protocol.
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
Errors should be forwarded up to the user, so yes, that is a bug. I’ll take a look. 😃
@Tribex I found you changed the last statement in
catchblock fromthrow errtoconsole.error(err)in the latest version. That should fix the issue. I will reproduce and see if it is fixed, thanks!