Puppeteer will be familiar to people using other browser testing frameworks. All examples below use async/await which is only supported in Node v7.6.0 or greater.
Starting from v3.0.0 Puppeteer starts to rely on Node 10.18.1+. Specifically on the current pageĪlternatively, for specifical pages in case that you handle multiple pages on different variables, you should be able to specify the limit on the context as an option in the configuration object of the page.goto method: await page.Prior to v1.18.1, Puppeteer required at least Node v6.4.0.
Navigate to some website e.g Our Code World Create an instance of the chrome browserĪwait tDefaultNavigationTimeout(0)
The following snippet shows how you can do it in a real example: // Require puppeteer A value of 0 means an unlimited amount of time. The setDefaultNavigationTimeout method available on a created page of Puppeteer allows you to define the timeout of the tab and expects as first argument, the value in milliseconds. For example, to remove the limit you should add: await tDefaultNavigationTimeout(0) The option that i prefer, as i browse multiple pages in the same tab, is to remove the timeout limit on the tab that i use to browse. In this article, i'll explain you briefly 2 ways to bypass this limitation. Personally, i prefer to remove the limit as i know that the pages that i work with will end up loading someday. To solve this problem, you will have 2 options, either to increase this timeout in the configuration or remove it at all. is the load time, an exception is thrown (specifically the TimeoutError) after a page takes more than 30000ms (30 seconds) to load totally. One of the most usual problems with pages that contain a lot of content, because of the ads, images etc. During the automation of multiple tasks on my job and personal projects, i decided to move on Puppeteer instead of the old school PhantomJS.
0 kommentar(er)
