The Puppeteer API suggests using a Promise.All() to prevent a race condition. In case, if you need to wait for page to be ready a button click or a form submit, use page.waitForNavigation() const = await Promise.all([ Wait for the page ready after a button click or a form submit # But you might trap in new problems, so test your code repeatedly and on many sites. You can write standard code to handle these issues if you are working with a known set of sites. Some pages can stop sending networking requests, and some not. And sometimes, you trap in infinite scrolling. You still might have pages with lazy loading images, so you need to scroll to the bottom of the page and then wait until the images are loaded. The combination of options like domcontentloaded and networkidle2, might work well in many cases, but not in all cases.
Since your script is ok, this can be caused by network issues or issues with the page. If its not there, maybe you are getting some error/timeout before the page.screenshot command runs.
I chose networkidle2 instead of networkidle0, because they constantly send requests, and page.goto() will throw an error on timeout. The screenshot.png should be on the directory that you run the node offline-login-check.js command. In order to take a screenshot when the page is fully loaded and rendered, one of the most working combination is to set waitUntil for the page.goto() function to domcontentloaded and wait a bit before taking a screenshot: const puppeteer = require('puppeteer') Ĭonst browser = await puppeteer.launch()
While waiting a fixed period of time is a bad practice, in the real world, it is hard to find a solution that works well in all cases.
PUPPETTEER SCREENSHOT PATH HOW TO
Join me in exploring how to find the ideal wait time or event of when to take the page screenshot with Puppeteer. Posted J(updated July 14, 2022) by Dmytro Krasun ‐ 7 min read
0 kommentar(er)
